I have been struggling with this for a couple days now, maybe I just need some people with a fresh perspective to figure out what the issue is.
Basically I have a bunch of computers that are being routed through a specific gateway in order to access a web page that is hosted internally on a separate subnet. I set up static routes on all of the computers, and they all work... except one.
Here's what a route print -4 looks like for a working computer (Windows 7):
===========================================================================
Interface List
14...xx xx xx xx xx xx ......Broadcom 802.11n Network Adapter
11...xx xx xx xx xx xx ......Realtek PCIe GBE Family Controller
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
17...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.xxx.xxx.230 10.xxx.xxx.94 20
10.zzz.zzz.0 255.255.255.0 10.xxx.xxx.147 10.xxx.xxx.94 21
10.xxx.xxx.0 255.255.255.0 On-link 10.xxx.xxx.94 276
10.xxx.xxx.94 255.255.255.255 On-link 10.xxx.xxx.94 276
10.xxx.xxx.255 255.255.255.255 On-link 10.xxx.xxx.94 276
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 10.xxx.xxx.94 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 10.xxx.xxx.94 276
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
10.zzz.zzz.0 255.255.255.0 10.xxx.xxx.147 1
===========================================================================
And here's a route print -4 from the station that doesn't work (also Windows 7):
===========================================================================
Interface List
10...xx xx xx xx xx xx ......Realtek PCIe GBE Family Controller
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.xxx.xxx.230 10.xxx.xxx.132 276
10.zzz.zzz.0 255.255.255.0 10.xxx.xxx.147 10.xxx.xxx.132 21
10.xxx.xxx.0 255.255.255.0 On-link 10.xxx.xxx.132 276
10.xxx.xxx.132 255.255.255.255 On-link 10.xxx.xxx.132 276
10.xxx.xxx.255 255.255.255.255 On-link 10.xxx.xxx.132 276
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 10.xxx.xxx.132 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 10.xxx.xxx.132 276
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
10.zzz.zzz.0 255.255.255.0 10.xxx.xxx.147 1
===========================================================================
Both of these stations are running Windows 7.
So essentially what I am trying to do here is route all traffic to the 10.zzz.zzz.0 subnet through the 10.xxx.xxx.147 gateway. Everything else should go through the 10.xxx.xxx.230 gateway. This is the intended behavior, and again it is working everywhere but that one station. I noticed that the Active Route metric costs differ between the two stations, but I am new to the routing table and I am not sure how that is impacting the behavior.
I hope I have been able to explain the situation clearly. Any help would be much appreciated. I can provide any additional information if needed!
EDIT:
Here is a pathping from a working machine to a destination on the 10.zzz.zzz.0 subnet:
Tracing route to 10.zzz.zzz.2 over a maximum of 30 hops
0 WorkingPC.company.local [10.xxx.xxx.185]
1 * 10.xxx.xxx.147
2 206.nnn.nnn.54
3 10.zzz.zzz.2
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 WorkingPC.company.local [10.xxx.xxx.185]
0/ 100 = 0% |
1 1ms 1/ 100 = 1% 1/ 100 = 1% 10.xxx.xxx.147
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 206.nnn.nnn.54
0/ 100 = 0% |
3 1ms 0/ 100 = 0% 0/ 100 = 0% 10.zzz.zzz.2
Trace complete.
And here's the same pathping from the non-working machine:
Tracing route to 10.zzz.zzz.2 over a maximum of 30 hops
0 BrokenPC.company.local [10.xxx.xxx.132]
1 10.xxx.xxx.147
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 BrokenPC.company.local [10.xxx.xxx.132]
2/ 100 = 2% |
1 1ms 2/ 100 = 2% 0/ 100 = 0% 10.xxx.xxx.147
Trace complete.
Here's a tracert from a working PC:
Tracing route to 10.zzz.zzz.2 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 10.xxx.xxx.147
2 2 ms 2 ms 2 ms 206.nnn.nnn.54
3 1 ms 1 ms 1 ms 10.zzz.zzz.2
Trace complete.
And here's an abridged tracert from the non-working station:
Tracing route to 10.zzz.zzz.2 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 10.xxx.xxx.147
2 * * * Request timed out.
3 * * * Request timed out.
.
.
.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Clearly some strange things are afoot on this network. I have been with this particular company for less than two weeks now, and this is the first I have seen of a 206.nnn.nnn.0 address.
As a side note, I tried running the non-working computer through the same network port that a working station was using, but still had no luck. At least that rules out a wiring issue, I guess? The above printouts were done while the computer was still plugged in to its original network port.
Again, any help or insight you guys can provide is extremely welcomed! Thank you!
FINAL EDIT:
Thank you to everyone who provided feedback on this issue; it is now resolved. I gave the non-working station a different IP and it was able to connect to the 10.zzz.zzz.0 subnet without any issues. Once I get settled into my position here at the company a bit more, I'll take a closer look at the ACL on the 10.xxx.xxx.147 device, as several of you suggested. Until then, everything that needs to talk to each other is talking to each other. Thanks again!
arp -avshow the same gateway MAC addresses on 10.xxx.xxx.132 and 10.xxx.xxx.94? – Ansgar Wiechers Sep 19 '12 at 20:29