Celtboy
12-24-2004, 12:19 AM
Scenario:
Machine A can ping out just fine.
Machine A CANNOT ping the proxy server (located at remote site).
Machine A CAN ping and traceroute other machines located in same vlan as proxy, and same physical site as proxy.
Traceroutes from Machine A die just before they hit the Proxy machine.
Machine B can ping proxy just fine.
Cable from machine B, plugged into Machine A = still no ping proxy.
There are no firewalls on Machine A. (XP SP1).
Seems to be sporradic. Machine A can ping for a while...then suddenly...it cannot.
DNS/Wins resolves correctly. Same regardless of pinging/tracerouting by ip or name.
Summary:
Machine can sometimes not access a remote machine, yet can access machines right beside it all the time. Does not seem to be cable or ip address dependant.
Corrupt arp caching? Evil practical joke? Any ideas?
-Celt
Machine A can ping out just fine.
Machine A CANNOT ping the proxy server (located at remote site).
Machine A CAN ping and traceroute other machines located in same vlan as proxy, and same physical site as proxy.
Traceroutes from Machine A die just before they hit the Proxy machine.
Machine B can ping proxy just fine.
Cable from machine B, plugged into Machine A = still no ping proxy.
There are no firewalls on Machine A. (XP SP1).
Seems to be sporradic. Machine A can ping for a while...then suddenly...it cannot.
DNS/Wins resolves correctly. Same regardless of pinging/tracerouting by ip or name.
Summary:
Machine can sometimes not access a remote machine, yet can access machines right beside it all the time. Does not seem to be cable or ip address dependant.
Corrupt arp caching? Evil practical joke? Any ideas?
-Celt