Could also be a rogue DHCP server. When a machine experiences a problem, check it's IP address against what it should be. If the IP isn't what you expect it to be (i.e. if you're expecting 10.10.10.x and you see 192.168.0.x), it may be because a device with a DHCP server enabled was connected to your network. Any new servers or network devices would be suspect.
Main Topics
Browse All Topics





by: pseudocyberPosted on 2005-04-28 at 08:11:11ID: 13886564
Could be an intermittent routing issue. Could be a spanning tree problem.
We really need a better understanding of your network. Are they all on the same IP network? Are all the subnet masks and default gateways correct?
When they don't work, try this in order and tell us where it fails:
Can you ping 127.1.0.1?
Can you ping the IP of the device? Ping itself?
Can you ping the default gateway?
Do a traceroute to the destination.