Your purpose is to narrow your search to one or two general categories. Pp Troubleshooting Basics 14.1 Troubleshooting Steps Step 2: Isolating the Cause The next step is to isolate the problem’s cause. The only tools required for this phase are a pad of paper, a pen (or pencil), and good listening skills. Without a complete understanding of the entire problem, you can spend a great deal of time working on the symptoms, without getting to the cause. Pp Troubleshooting Basics 14.1 Troubleshooting Steps Step 1: Defining the Problem The first phase is the most critical, yet most often ignored. Specific troubleshooting models share common steps, such as the five steps shown here. Pp Troubleshooting Basics 14.1 Troubleshooting Steps Troubleshooting is perhaps the most difficult task that network professionals face. Key Terms README system lockup Event Viewer Follow the plan and only troubleshoot one thing at a time. Pp Troubleshooting Basics 14.1 Guide to Reading Main Ideas Troubleshooting requires a planned, methodical approach. 1 Section 14.1 Section 14.2 Identify troubleshooting stepsĭiagnose software, hardware, and network problems Section 14.2 Use Windows Troubleshooters Create a first response plan Demonstrate how to resolve common computer problemsĢ Section 14.3 Name the principal hardware tools used to troubleshoot network problems Identify software-based monitoring tools Identify the components that each monitor tool checks Describe the methods for monitoring a network Describe network troubleshooting tools
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |