| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
IX Troubleshooting (Page 3 of 5) Identify the Affected Area Once youve identified the symptoms, isolate the problem to the area affected. Questions you might ask are: Are all workstations on this segment affected the same way? Are all workstations on this subnet affected the same way? Are all workstations on subnets connected to a specific router affected? Are all workstations connected to a specific server affected? Are all workstations at this site affected? Can any dial-up users get access to the system? Can this user log in successfully using a PC other than their own? Isolating the problem to a specific area helps tell you what and what is not, a potential source of the problem. For example, if no dial-up users can get access to a RAS server, its unlikely that the problem source is the computer of the user who called you first. Its more likely that the problem is in the RAS server or its attached modem bank. If youve just replaced a router, and suddenly all of the users connected to that router have no, or partial, network connectivity, and you use DHCP for assigning the TCP/IP parameters to workstations, perhaps the router is not bootp-compliant.
Home - Table Of Contents - Contact Us CertiGuide for Network+ (http://www.CertiGuide.com/netplus/) on CertiGuide.com Version 1.0 - Version Date: November 7, 2004 Adapted with permission from a work created by Tcat Houser and Helen O’Boyle. CertiGuide.com Version © Copyright 2004 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||