Static route works sometimes?

  • Thread starter Thread starter Ken Williams
  • Start date Start date
K

Ken Williams

I have an XP machine running SP2.

I added a couple static routes.
route add -p 192.168.248.0 mask 255.255.255.0 192.168.1.75 metric 2 IF 2
route add -p 192.168.252.0 mask 255.255.255.0 192.168.1.75 metric 2 IF 2

Sometimes when I bootup these routes don't work right away. Sometimes
they do.

When they do not I open a command prompt and ping one of the servers on
the other site of the route, like simply just "ping 192.168.252.2". The
first packet will fail with the typical "Request timed out". Then a
proper "Reply from 192.168.252.2: byes=32 time=90s...", etc. from then
on. Then the route works properly.

Any idea why? How can I fix this crazyness.
 
Windows will sometime eliminate routes, I don't know why but MS has some
paperwork on this that SP3 was supposed to fix... It doesn't... What I do
for cases like this is to create a batch file with the route add
instructions then run it with the task scheduler every 10 minutes. This
keeps the routes alive. I would perfer not to do this but it works...

--
Randem Systems
Your Installation Specialist
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
Disk Read Error Press Ctl+Alt+Del to Restart
http://www.randem.com/discus/messages/9402/9406.html?1236319938
 
Randem said:
Windows will sometime eliminate routes, I don't know why but MS has some
paperwork on this that SP3 was supposed to fix... It doesn't... What I do
for cases like this is to create a batch file with the route add
instructions then run it with the task scheduler every 10 minutes. This
keeps the routes alive. I would perfer not to do this but it works...
Click to expand...


If thats what it takes maybe if I just do a ping on startup (some batch
file) to somehow get it going. unless it stops routing afterwards like
your saying... I'll see what happens.
 
SPAMCOP said:
Ken,

Sounds like DNS to me. What's the primary DNS set to?
Click to expand...

I never thought of that. but the secondary should work and be fine so
this should still not happen. I need to do more testing.
 
Ken Williams said:
I have an XP machine running SP2.

I added a couple static routes.
route add -p 192.168.248.0 mask 255.255.255.0 192.168.1.75 metric 2 IF 2
route add -p 192.168.252.0 mask 255.255.255.0 192.168.1.75 metric 2 IF 2

Sometimes when I bootup these routes don't work right away. Sometimes they
do.

When they do not I open a command prompt and ping one of the servers on
the other site of the route, like simply just "ping 192.168.252.2". The
first packet will fail with the typical "Request timed out". Then a proper
"Reply from 192.168.252.2: byes=32 time=90s...", etc. from then on. Then
the route works properly.

Any idea why? How can I fix this crazyness.
Click to expand...

As sgopus suggested, this sounds like an issue with your router.

The behaviour you describe is what you would expect from an on demand VPN or
similar connection, which only opens when requested from the host.

I don't think it's an issue with your Windows Installation.

Alister
 
Back
Top