Discussion Locked

Finding network problems

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I would like to know if there are any good, free tools or documentation out there to help us to determine the cause of a slowdown in one of our network segments.

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 jwpluto

While Ping and traceroute are good tools, there is a large assortment of protocol analyzers on the net that can help you. Maybe not all are free, but some are, some aren't. At "downloads.cnet.com", search for "protocol analyzer". There are several tools to choose from. I recently learned how to use NetXRay and find that I should have been using it long ago to help with problems like yours. Good luck...

This discussion is closed to new replies.