Windows XP Pro routing issue

We have two computers on our LAN that pick up an additional routing rule on boot. Their routing table looks as follows:

U:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 1a 6b 5f 13 ea ...... Intel(R) 82566DM-2 Gigabit Network Connection - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   192.168.10.250  192.168.10.110       20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      169.254.0.0      255.255.0.0   192.168.10.110  192.168.10.110       30
     192.168.10.0    255.255.255.0   192.168.10.110  192.168.10.110       20
   192.168.10.110  255.255.255.255        127.0.0.1       127.0.0.1       20
   192.168.10.255  255.255.255.255   192.168.10.110  192.168.10.110       20
        224.0.0.0        240.0.0.0   192.168.10.110  192.168.10.110       20
  255.255.255.255  255.255.255.255   192.168.10.110  192.168.10.110       1
Default Gateway:    192.168.10.250
===========================================================================
Persistent Routes:
  None


The problem route is the 169.254.0.0 route.

If I delete the route using the route delete command, it is there again when the computer is rebooted. Other computers on the same LAN are not picking up this routing rule. Our users do not have access to delete routes themselves. How do I prevent it from being picked up on future reboots? How can I find where it is getting it from and why only these two computers have the route?


Thanks,
RabidZomAsked:
Who is Participating?
 
BlazCommented:
169.254.0.0 network is a network where Windows Automatic IP Addressing (APIPA) assigns addresses. If the computer is not able to connect to a DHCP server on boot it gets an address from this range.

There is no problem with this address and route and you can just let it be. If you would configure static IP address you would probably not get this route after boot.
0
 
RabidZomAuthor Commented:
Thanks for that. Our problem is that we have some servers which have IP addresses in the 169.254.x.y range (our LAN is 192.168.10.x) and when a user has this route it appears to prevent them from accessing servers in the 169.254.x.y range (the connection times out in the browser)

 

Both users that have this issue have DHCP enabled and still get this route on boot. All our other DHCP users dont get this route. Giving them a static IP address does not prevent the route from appearing.

 

Giving persistant routes specific to the IP addresses of the individual servers (e.g. a route to 169.254.1.2) seems to resolve the issue.

0
 
BlazCommented:
No servers should have address in this range. This is not a valid public IP neither allowed privat IP and should not be used on any network.

http://www.faqs.org/rfcs/rfc3330.html:
169.254.0.0/16 - This is the "link local" block.  It is allocated for
   communication between hosts on a single link.  Hosts obtain these
   addresses by auto-configuration, such as when a DHCP server may not
   be found.
0
 
tallen03Commented:
I found the solution to be to remove the Bonjour program.  It is an Apple program that messes with the route tables.  
0
 
RabidZomAuthor Commented:
Tallen - your absolutely correct - Bonjour was installed on the affected computers!

Many Thanks for answering after the question was closed

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.