Network Static Route Issues
Crossposted using Lemmit.
Original post from /r/sysadmin by /u/International_Dare81 on 2023-07-07 12:45:28+00:00.
Im completely confused.
C:\Windows\system32>tracert 172.16.1.10
Tracing route to copdc1.portlandmaine.local [172.16.1.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms copdc1.portlandmaine.local [172.16.1.10]
Trace complete.
C:\Windows\system32>tracert 172.16.1.11
Tracing route to copdc2.portlandmaine.local [172.16.1.11]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.199.1
2 <1 ms <1 ms <1 ms 10.10.10.9
3 1 ms <1 ms <1 ms copdc2.portlandmaine.local [172.16.1.11]
Trace complete.
C:\Windows\system32>route print
Interface List
15...00 50 56 a1 3f 81 ......vmxnet3 Ethernet Adapter
1...........................Software Loopback Interface 1
IPv4 Route Table
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.00.0.0.0192.168.199.1 192.168.199.20271
127.0.0.0255.0.0.0On-link 127.0.0.1331
127.0.0.1 255.255.255.255On-link 127.0.0.1331
127.255.255.255 255.255.255.255On-link 127.0.0.1331
192.168.199.0255.255.255.0On-link 192.168.199.20271
192.168.199.20 255.255.255.255On-link 192.168.199.20271
192.168.199.255 255.255.255.255On-link 192.168.199.20271
203.0.113.129 255.255.255.255 192.168.199.20 192.168.199.2016
224.0.0.0240.0.0.0On-link 127.0.0.1331
224.0.0.0240.0.0.0On-link 192.168.199.20271
255.255.255.255 255.255.255.255On-link 127.0.0.1331
255.255.255.255 255.255.255.255On-link 192.168.199.20271
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.00.0.0.0192.168.199.1 Default
IPv6 Route Table
Active Routes:
If Metric Network Destination Gateway
1 331 ::1/128 On-link
1 331 ff00::/8 On-link
Persistent Routes:
None
I cannot understand why 172.16.1.10 is taking some arbitrary route directly to that IP but 172.16.1.11 is taking the proper path based on the routing table. Its like there's a static route somewhere for 1.10 specifically. ALL other IPs route correctly.
Is there somewhere else to look for that static route??? I have put another server in the same subnet and done a traceroute which routes correctly so i think its a server issue not a network issue.