Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On our windows 2003 domain, with XP clients, we have started seeing routes appearing in the routing tables on both the servers and the clients. The route is a /32 for another computer on the domain. The route gets added when one windows computer connects to another computer and needs to authenticate.

For example, if computer A with ip browses the c: drive of computer B with ip, a static route will get added on computer B like so:

dest     netmask         gateway  interface 

This also happens on windows authenticated SQL server connections. It does not happen when computers A and B are on the same subnet.

None of the servers have RIP or any other routing protocols enabled, and there are no batch files etc setting routes automatically.

There is another windows domain that we manage with a near identical configuration that is not exhibiting this behaviour. The only difference with this domain is that it is not up to date with its patches.

Is this meant to be happening? Has anyone else seen this? Why is it needed when I have perfectly good default gateways set on all the computers on the domain?!

share|improve this question

Is your default router routing all the traffic? or is there another router for the second network? In the latter case, your default router will send the route back to the client(your system) via a ICMP redirect or similar

share|improve this answer
Good thought. But each subnet has only one gateway. We wiresharked the traffic on the "B" computer just now to make sure and it did not show any icmp traffic other than echo. – simon Mar 22 '12 at 11:47

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.