Network troubleshooting is--or should be--a systematic process, whether or not you are an expert.

Many times, when a user notices an issue on their computer, their first response is to suspect something bigger--the server, the network, the Internet connection, etc.

Often, however, the cause of the problem is much closer to home.

When examining a problem, it is best to "work from the inside out." This means start where you have noticed the trouble--whether that is at your workstation, the printer, the server, etc.--and follow the trail of clues until you find the cause.

The first and most important question you can ask when "working from the inside out," is whether or not anyone else is having the same or a similar problem. If so, you can probably move on from the workstations to the next level up--mostly likely the server.

Depending upon the exact nature of the issue, you may have to check your hubs or switches, your router, and possibly contact your Internet Service Provider, before you uncover the answer. The key is to proceed in a logical fashion--if the problem is bigger than one workstation, check the server. If the server also has an issue, check the hubs, switches or router. If the router has a problem, make sure the Internet is working, and so on.

In some cases, you may find that the problem is beyond your technical capabilities. In that case, you have no choice but to wait for assistance. You will have done yourself a favor, however, by narrowing the problem down as much as you can. When the computer technician arrives, he or she will have a head-start on finding a solution, based on what you have already accomplished.

Troubleshooting your network does not have to be a scary proposition. Most people have the skills needed to analyze the overall issue, simply by following an orderly process to determine the likely cause of the problem.

Next Week: Remember--There Is an Answer