Click Shares in the console tree.

when tracking down problems in a Windows Server 2003 system. Poke around the console tree in Computer Management and here’s what you’ll find: ⻬ Event Viewer: Refer to the section “Using the Event Viewer” earlier in this chapter for more information. ⻬ Shared Folders: Here you can manage your shared folders, current ses- sions, and open files. For more information, see Chapter 4 of this book. ⻬ Performance Logs and Alerts: Refer to Chapter 14 for more information on Performance Monitor. ⻬ Device Manager: A handy tool for diagnosing problems with hardware devices. Device Manager lists all the hardware devices currently installed on the computer. You can double-click a device to bring up a Properties dialog box that displays information about the status of the device and lets you change drivers or configuration settings. ⻬ Removable Storage: Lets you track removable storage media such as tapes and CDs, and manage tape and CD libraries. ⻬ Disk Defragmenter: Lets you optimize the way data is stored on your disks. ⻬ Disk Management: Lets you work with disk partitions, format disks, create mirror sets, and perform other disk operations. ⻬ Services and Applications: Lets you manage services and applications that you’ve installed on the computer, such as DHCP, DNS, IIS, and so on. Working with services The last troubleshooting tool I want to describe is the Services console, which you can access by choosing Start➪Administrative Tools➪Services. As Figure 19-11 shows, the Services console displays a list of all services currently running on your system. If a Windows server feature isn’t working properly, the problem is often that something has caused one of the services associated with the feature to stop. You can often correct the problem by calling up the Services console and restarting the service. To do that, just select the service, and then click the Start the Service link. Of course, this action doesn’t correct the underlying cause of the problem. If the service stopped because of a one-time error, simply restarting the service may be all that you need to do. In many cases, though, the problem that dis- rupted the service will resurface and cause the service to stop again. 272 Part IV: Network Operating Systems Always look at the Services console before rebooting your server in an effort to correct a problem. Very few problems require a reboot in Windows Server 2003. Instead, you can often correct the problem by restarting just the affected service. Figure 19-11: The Services console. 273

Chapter 19: Windows Server 2003