I've had a route in Windows Server 2008 R2 RRAS that's been working for a long time, which is 192.168.100.0/24.
The network on the other side of that link recently added a new subnet, 192.168.101.0/24
So, naturally I thought to myself, I would just modify the existing route to the following:

But no go. Nothing on the new subnet goes anywhere.
But, if I make the following setup:

Which is effectively the same route as above, just more verbose, works perfectly.
I don't mind having the two routes, but I'd really like to know why it's nessesary. Any ideas?
route printdoes it show things correctly when you have the/23route? Does a traceroute show the traffic trying to leave the correct interface? – Zoredache Dec 12 '11 at 21:25192.168.100.0 255.255.254.0 192.168.161.106- however, I see there is a realllllly old RIP route still hanging around that's for a much smaller range on the192.168.101.0/24network which will be taking precedence. Sometimes I just have brain farts all day. – Mark Henderson♦ Dec 12 '11 at 21:51