Click Finish. Windows Server 2003

⻬ You can remove a permission by selecting the permission and then click- ing Remove. ⻬ If you’d rather not fuss with the File Server Manager, you can set the per- missions from My Computer. Right-click the shared folder, and choose Sharing and Security; then click Permissions. You can then follow the preceding procedure, picking up at Step 3. ⻬ The permissions assigned in this procedure apply only to the share itself. The underlying folder can also have permissions assigned to it. If that’s the case, whichever of the restrictions is more restrictive will always apply. For example, if the Share Permissions grant a user Full Control per- mission, but the folder permission grants the user only Read permission, the user will be given Read permission for the folder. Troubleshooting Windows Server 2003 is extremely reliable. Get it configured right in the first place, and it’ll chug along without incident. That is, at least until something goes wrong. Which is inevitable. The following sections present a couple of Windows tools you can use to help pin down and fix trouble when it shows up. Using the Event Viewer Windows has a built-in event-tracking feature that automatically logs a variety of interesting system events. Usually, when something goes wrong with your server, you can find at least one and maybe dozens — or even hundreds — of events in one of the logs. All you have to do is open the Event Viewer, and check the logs for suspicious-looking entries. To display the event logs, choose Start➪Administrative Tools➪Event Viewer. This brings up the Event Viewer, as shown in Figure 19-10. The tree on the left side of the Event Viewer lists the five categories of events that are tracked: ⻬ Application: Lists events that were generated by application programs. In most cases, these are events that the application’s developers pur- posely wrote to the event log, to inform you of error conditions or devel- oping trouble. ⻬ Security: Lists security-related events, such as unsuccessful logon attempts, changes to security policy, and so on. For information about how to change the events that are written to the security log, see Chapter 4 of this book. ⻬ System: This is where you find events related to hardware or operating- system failures. For example, if you’re having trouble with a hard drive, you should check here for events related to the hard drive. 270 Part IV: Network Operating Systems ⻬ Directory Service: Active Directory events are recorded here. ⻬ DNS Server: If you’re having trouble with your DNS service, look at this log to find the details. ⻬ File Replication Service: Here is where you find events logged by File Replication Service. Select one of these options to see the log you want to view. In Figure 19-10, I clicked the System Events log and scrolled down the list a little to find some messages related to a DHCP problem. Notice the cute little icons next to each item in the log. They indicate whether the message is merely informative or is trying to alert you to a warning or error condition. To see the details for a particular event, double-click the event. This brings up a dialog box that displays the details about the event. In some cases, you may be able to diagnose a problem just by reading the error message dis- played in this dialog box. In other cases, this information just points you in the right direction — it tells you what went wrong, but you still have to figure out why. Using the Computer Management Console The Start➪Administrative Tools➪Computer Management command leads you to the Computer Management Console, which is a tool that’s often useful Figure 19-10: The Event Viewer lets you examine events. 271

Chapter 19: Windows Server 2003