Static routes added to Routing Table in Windows 2000 Server upon R

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have a Windows 2000 Server which upon any reboot, two static routes are
placed back into the Routing Table and cause our VPN connections to not
reconnect. Once we remove the two routes from table, the VPN connections
resume and work correctly. The server has multiple NICs, but all are disable
in the BIOS except the Gigabit. At first, we thought it was the onboard NICs
pulling an IP, but after looking into the problem, I have no idea why these
routes are being added at the reboot. Any ideas would be appreciated.
Thanks, Marc
 
check the RRAS routing table or post the routing table here. you can use route print to display the routing table. For more and other information, go to http://howtonetworking.com.

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
I recommend Brinkster for web hosting!

We have a Windows 2000 Server which upon any reboot, two static routes are
placed back into the Routing Table and cause our VPN connections to not
reconnect. Once we remove the two routes from table, the VPN connections
resume and work correctly. The server has multiple NICs, but all are disable
in the BIOS except the Gigabit. At first, we thought it was the onboard NICs
pulling an IP, but after looking into the problem, I have no idea why these
routes are being added at the reboot. Any ideas would be appreciated.
Thanks, Marc
 
This is the normal Routing Table:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 03 47 2a d1 ad ...... Intel(R) PRO/100 VE Network Connection #2 -
Pack
et Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.4.1.1 10.4.1.28 20
10.4.1.0 255.255.255.0 10.4.1.28 10.4.1.28 20
10.4.1.28 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.4.1.28 10.4.1.28 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.4.1.28 10.4.1.28 20
255.255.255.255 255.255.255.255 10.4.1.28 10.4.1.28 1
Default Gateway: 10.4.1.1
===========================================================================
Persistent Routes:
None
 
Marc said:
This is the normal Routing Table:
Click to expand...


The "route" command and the RRAS routing MMC
are NOT fully integrated.

Routes in one (may or) may not work in the other, or
even appear there -- they may not appear but they may
have an effect.

If you use RRAS stay away from the route command
except for an occasional quick peek (no setting or deleting
there.)


===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 03 47 2a d1 ad ...... Intel(R) PRO/100 VE Network Connection #2 -
Pack
et Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.4.1.1 10.4.1.28 20
10.4.1.0 255.255.255.0 10.4.1.28 10.4.1.28 20
10.4.1.28 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.4.1.28 10.4.1.28 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.4.1.28 10.4.1.28 20
255.255.255.255 255.255.255.255 10.4.1.28 10.4.1.28 1
Default Gateway: 10.4.1.1
===========================================================================
Persistent Routes:
None
Click to expand...

If you are picking up 'persistent' routes not shown above
then they are coming from the RRAS MMC (NetSh.exe
can do this too) or from a script program that is resetting
it on each logon.
 
There is also the chance they are coming from another router via a
routing protocol like RIP.
 
Bill Grant said:
There is also the chance they are coming from another router via a
routing protocol like RIP.
Click to expand...

That's a good addition -- this would be through RRAS,
but your point is more explicit.
 
Well, we are running CISCO routers throughout our network. Do you think it
is possible that the routes are coming from the CISCO equipment?
 
Marc said:
Well, we are running CISCO routers throughout our network. Do you think it
is possible that the routes are coming from the CISCO equipment?
Click to expand...

Only if you are running RIP, OSPF in conjunction
with them.

Or perhaps if it is adding it through a "router direct"
(ICMP) message from them.

I didn't think it would add them to the table for this, but
I guess it is possible.
 
There are lots of ways routes can get added to the machine, as stated
previously a routing protocol can add them ( RIP, OSPF ), ICMP messages (
Redirect and Router Discovery ), static routes ( DHCP assigned, route add,
RRASMgmt.msc added, Interface added etc ).

The best way to track this down is look at the route table using
RRASMgmt.msc when the routes are there. They will have a tag associated
with them that will help narrow down how they were learned ( RIP, OSPF,
Network Management, etc. )
 
Back
Top