Question | Answer |
best defense against problems | prevention |
successful troubleshooters proceed | logically and methodically |
troubleshooting steps | identify the problem |
troubleshooting steps | establish a theory of probable cause |
troubleshooting steps | test the theory to determine the cause |
troubleshooting steps | establish a plan of action to resolve the problem and identify potential effects |
troubleshooting steps | implement the solution or escalate |
troubleshooting steps | verify system functionality |
troubleshooting steps | document findings |
one danger in troubleshooting technical problems | jumping to conclusions |
take time to pay attention to | the users,system and network behaviors, and any error messages |
narrowing down the area affected by a problem | can eliminate some causes and point to others |
troubleshooting steps | discover the time or frequency with which a problem occurs |
narrowing the scope | helps limit the number of possible problems |
watch the user | best way to verify that a user is doing things correctly |
you can react in two ways if you suspect that a network change has generated a problem | attempt to correct the problem that resulted from a change |
you can react in two ways if you suspect that a network change has generated a problem | attempt to restore it to its previous state |
theory of probable cause | what might be the problem based on what you see |
symptoms of physical layer problems | noise |
symptoms of physical layer problems | segment,network length exceeds standards |
symptoms of physical layer problems | improper terminations,faulty loose cables |
symptoms of physical layer problems | faulty nics |