RabidZom
asked on
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,
U:\>route print
==========================
Interface List
0x1 ..........................
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,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I found the solution to be to remove the Bonjour program. It is an Apple program that messes with the route tables.
ASKER
Tallen - your absolutely correct - Bonjour was installed on the affected computers!
Many Thanks for answering after the question was closed
Many Thanks for answering after the question was closed
ASKER
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.