Changes to the Server
Part of a network administrator's job involves some tinkering with the server. Although this might be unavoidable, it can sometimes lead to several unintentional problems. Even the most mundane of all server tasks can have a negative impact on the network. The following are some common server-related tasks that can cause problems:
- Changes to user accounts-For the most part, changes to accounts do not cause any problems, but sometimes they do. If after making changes to user accounts, a user or several users cannot log on to the network or access a database, the problem is likely related to the changes made to the accounts.
- Changes to permissions-Data is protected by permissions that dictate who can and cannot access the data on the drives. Permissions are an important part of system security, but changes to permissions can inadvertently prevent users from accessing specific files.
- Patches and updates-Part of the work involved in administering networks is to monitor new patches and updates for the network operating system and install them as needed. It is not uncommon for an upgrade or a fix to an operating system to cause problems on the network.
- New applications-From time to time, new applications and programs-such as productivity software, firewall software, or even virus software-have to be installed on the server. When any kind of new software is added to the server, it might cause problems on the network. Knowing what has recently been installed can help you isolate a problem.
- Hardware changes-Either because of failure or expansion, hardware on the server might have to be changed. Changes to the hardware configuration on the server can cause connectivity problems.
In this tutorial:
- Troubleshooting Procedures
- The Art of Troubleshooting
- Troubleshooting Servers and Workstations
- General Troubleshooting Considerations
- Troubleshooting Methods and Procedures
- Step 1: Information Gathering-Identify Symptoms and Problems
- Information from the Computer
- Information from the User
- Step 2: Identify the Affected Areas of the Network
- Step 3: Determine if Anything Has Changed
- Changes to the Network
- Changes to the Server
- Changes to the Workstation
- Step 4: Establish the Most Probable Cause
- Step 5: Determine if Escalation Is Necessary
- Step 6: Create an Action Plan and Solution Identifying Potential Effects
- Step 7: Implement and Test the Solution
- Step 8: Identify the Results and Effects of the Solution
- Step 9: Document the Solution and the Entire Process
- Troubleshooting the Network
- Where the Cable Is Used
- Crosstalk
- Open Impedance Mismatch (Echo)
- Managing Collisions
- Troubleshooting Infrastructure Hardware
- Configuring and Troubleshooting Client Connectivity
- Troubleshooting Incorrect VLANs
- Identifying Issues That Might Need Escalation
- Troubleshooting Wireless Issues
- Troubleshooting Wireless Signals
- Troubleshooting Wireless Configurations