XP - ping changes routing table?
Posted
by
Corelgott
on Server Fault
See other posts from Server Fault
or by Corelgott
Published on 2010-07-12T23:40:43Z
Indexed on
2011/01/03
4:55 UTC
Read the original article
Hit count: 243
Hey Folks,
I have got a real strange behaviour with one of my XP-Sp3 machines.
Setup: A Server in the lan (192.168.5.0) proviedes access to all roadwarriors in 10.8.0.0 The DCHP has a static route for all clients pronouncing 192.168.5.235 as gateway for 10.8.0.0
All Clients can ping & access the vpn-machines; everything works like a charm
But one Xp-Sp3 is not willing to connect to them. It gets all the same routes as any other sytem in the lan and I trippel-checked - there are no static routes on this machine
When I ping any 10.8.0.0 device from this machine, the first two packaged work like a charm; but the next two (and any package after them) fail and get lost.
When I look back into the routing table: There is a new route; a special one just for the device I pinged, which points to the right gateway - but which wasn't there earlier...
As Long as this route exists the machine can't ping anything on 10.8.0.0. But if I remove the route by hand: The next to ping packages work fine...
Has anybody got an idea about that? Anybody every seen such a behaviour? Any hint / help / tip is greatly appreachiated!
thx in advance
Corelgott
Ps: I attach an image of the cmd to clarify things - its in german, but reading a routing table shouldn't be that hard...
© Server Fault or respective owner