Troubleshooting Servers and Workstations

One often overlooked but important distinction in troubleshooting networks is the difference between troubleshooting a server computer and troubleshooting a workstation system. Although the fundamental troubleshooting principles of isolation and problem determination are often the same in different networks, the steps taken for problem resolution are often different from one network to another. Make no mistake: When you troubleshoot a server system, the stakes are much higher than with workstation troubleshooting, and therefore it's considerably more stressful. Let's take a look at a few of the most important distinctions between workstation and server troubleshooting:

• Pressure-It is difficult to capture in words the pressure you feel when troubleshooting a downed server. Troubleshooting a single workstation with one anxious user is stressful enough, and when tens, hundreds, or even thousands of users are waiting for you to solve the problem, the pressure can be enough to unhinge even the most seasoned administrator.
• Planning-Troubleshooting a single workstation often requires little planning. If work needs to be done on a workstation, it can often be done during a lunch break, after work, or even during the day. If work needs to be done on a server, particularly one that is heavily accessed, you might need to wait days, weeks, or even months before you have a good time to take down the server so that you can work on it and fix the problem.
• Time-For many organizations, every minute a server is unavailable is measured as much in dollars as it is in time. Servers are often relied on to provide 24-hour network service, and anything less is often considered unacceptable. Although it might be necessary to take a server down at some point for troubleshooting, you will be expected to account for every minute that it is down.
• Problem determination-Many people who have had to troubleshoot workstation systems know that finding the problem often involves a little trial and error. (Swap out the RAM; if that doesn't work, replace the power supply, and so on.) Effective server troubleshooting involves little trial and error-if any at all. Before the server is powered down, the administrator is expected to have a good idea of the problem.
• Expertise-Today, many people feel comfortable taking the case off their personal computers to add memory, replace a fan, or just have a quick peek. Although it is based on the same technologies as PC hardware, server hardware is more complex, and those who manage and maintain servers are expected to have an advanced level of hardware and software knowledge, often reinforced by training and certifications.

These are just a few of the differences in the troubleshooting practices and considerations between servers and workstations. As this tutorial discusses troubleshooting, the focus is mainly on the server side of troubleshooting. This helps explain why some of the troubleshooting procedures might seem rigid and unnecessary on a workstation level.

TIP: Workstations and Servers The Network does not require you to identify any specific differences between workstation and server troubleshooting, but it does require background knowledge of general troubleshooting procedures and the factors that influence how to approach a network problem.