5 replies
by ebob
I am a big fan of PING and TRACEROUTE (TRACERT in Windoze), assuming that you're working with a TCP/IP network. Try pinging and tracing to/from a variety of stations on and off the segment, which I find often helps me to narrow down the list of suspects. When the list is small enough, I can start looking at individual suspects. Possible common causes of problems include: bad NICs, bad patch cords, very busy user/workstation, and bad config on workstation.
Bad NICs and cables usually cause ots of collisions and will show up on some NICs, or the hubs/switches into which they're plugged as excess collisions.
Which brings up another free tool for diagnosing the network: the console of the hubs/switches on the segment. Many current boxes have neat little web-based GUIs which show ports reporting excessive collisions, and other problems to help narrow down your search.
by not_a_geek
by jwpluto
by not_a_geek
by not_a_geek
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending