Busy. Please wait.

show password
Forgot Password?

Don't have an account?  Sign up 

Username is available taken
show password


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.

Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.

Remove ads
Don't know
remaining cards
To flip the current card, click it or press the Spacebar key.  To move the current card to one of the three colored boxes, click on the box.  You may also press the UP ARROW key to move the card to the "Know" box, the DOWN ARROW key to move the card to the "Don't know" box, or the RIGHT ARROW key to move the card to the Remaining box.  You may also click on the card displayed in any of the three boxes to bring that card back to the center.

Pass complete!

"Know" box contains:
Time elapsed:
restart all cards

Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how



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
Created by: cgeaski