Changes to the Workstation
The changes made to the systems on the network are not always under the control of the network administrator. Often, the end user performs configuration changes and some software installations. Such changes can be particularly frustrating to troubleshoot, and many users are unaware that the changes they make can cause problems. When looking for changes to a workstation system, consider the following:
- Network settings-One of the configuration hotspots for workstation computer systems are the network settings. If a workstation cannot access the network, it is a good idea to confirm that the network settings have not been changed.
- Printer settings-Many printing problems can be isolated to changes in the printer configuration. Some client systems, such as Linux, are more adept at controlling administrative configuration screens than others; for example, Windows leaves such screens open to anyone who wants to change the configuration. When printing problems are isolated to a single system, changes in the configuration could be the cause.
- New software-Many users love to download and install nifty screensavers or perhaps the latest 3D adventure games on their work computers. The addition of extra software can cause the system to fail. Confirm with the end user that new software has not been added to the system recently.
NOTE: Duplicate IP Addresses Consider a system that could previously log on to the network but now receives an error message, stating that it cannot log on because of a duplicate IP address. A duplicate IP address means that two systems on the network are attempting to connect to the network using the same IP address. As you know, there can be only one. This often happens when a new system has been added to a network where Dynamic Host Configuration Protocol (DHCP) is not used.
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