Network Troubleshooting for Non-Geeks
Well, okay, maybe not non-geeks, but non-network-geeks, at least.
As many of you well know, I am almost always pressed for time. That’s partly due to my work, which seems to include more and more front-line support and less and less networking coolness. It’s just the way things go. In any case, …
So, don’t be intimidated by this. You can diagnose most of your own network problems. Just head on over to the Linux Journal’s website, where Mike Diehl has written a pretty comprehensive article on Troubleshooting Network Problems. Oh, and don’t let the fact that it’s on a Linux website throw you, he has tips for Windows users, too.
I am not a expert, but I prefer to go the usual way…
Network troubleshooting Using Ping is effective way that I found out recently.
Ping is usually the first port of call when troubleshooting network issues. All it does is send a short message to the destination asking if it exists or is alive. Then it feeds back the results to you. If it receives a reply then it will tell you how long it took. If it doesn’t receive as reply then you know there is something wrong with the connection.
Below is a great site I found about network troubleshooting… check it out….
http://www.levoltz.com/2009/07/19/network-troubleshooting/
Thanks
Well, ping is great, for what it is. I use it as a first step quite often, but it’s only a single protocol and, frankly, is only a general indication of a good connection. Of course, I also make my living diagnosing crazy network issues, among other things, so your experience may be substantially different from mine. In any case, thanks for the suggested article!