Module 3 / Unit 5 Network Troubleshooting Flashcards
On completion of this unit, you will be able to: □ Use effective troubleshooting procedures, following the CompTIA troubleshooting model. □ Troubleshoot common connectivity scenarios. □ Troubleshoot problems in networking infrastructure. □ Troubleshoot problems with network services, such as DHCP and DNS.
What are the two basic principles of identifying the cause of a problem?
Find out if anything has changed and test one thing at a time.
After asking the three basic questions of anyone reporting a problem, what should you have determined? (Choose THREE): ○ Whether to look for recent change or an oversight in configuration ○ Where to look for the problem ○ The severity of the problem ○ If the problem should be escalated
Whether to look for recent change or an oversight in configuration - TRUE
Where to look for the problem - TRUE
The severity of the problem - TRUE
If the problem should be escalated - FALSE
In what sort of circumstances should you escalate a problem?
If you cannot solve it yourself (though it won’t be good for your career if you give up too easily). You might also escalate if you do not have authorization to perform the necessary changes or if the system is under some sort of warranty.
If you detect a significant increase in noise affecting a cable link, how would you go about determining the cause?
Ask what has changed - it is likely that some equipment or power cabling has been installed near the data cable link.
When troubleshooting a cable link, which should you investigate first - the patch cord, permanent link, or network adapter?
Patch cord - or possibly network adapter.
You have connected a new computer to a network port and cannot get a link. You have tested the adapter and cable and can confirm that there are no problems. No other users are experiencing problems. The old computer also experienced no problems. What cause would you suspect?
Speed mismatch - check the autonegotiate settings on the adapter and port.
Users on a floor served by a single switch cannot get a network connection. What is the best first step?
Reset the switch - if that works also investigate possible underlying causes, such as a malicious attack on the switch or poorly seated plug-in module.
You have pinged the router for the local subnet and confirmed that there is a valid link. The local host cannot access remote hosts however. No other users are experiencing problems. What do you think is the cause?
The router is not configured as the default gateway (you can ping it but the host is not using it for routing).
Following maintenance on network switches, users in one department cannot access the company’s internal web and email servers. You can demonstrate basic connectivity between the hosts and the servers by IP address. What might the problem be?
It is likely that there is a problem with name resolution. Perhaps the network maintenance left the hosts unable to access a DNS server, possibly due to some VLAN assignment issue.
Users on a particular network segment have been experiencing poor performance. The cause has been identified as a “broadcast storm”. What is often the cause of broadcast storms?
Defective network card or switch, misconfiguration of STP, or the unauthorized or unplanned attachment of bridging devices that create a loop.
You are planning to reconfigure static and DHCP-assigned IP addresses across the network during scheduled downtime. What preliminary step should you take to minimize connectivity issues when the network is reopened?
Ensure that clients obtain a new DHCP lease, either by shortening the lease period in advance or by using a script to force clients to renew the lease at startup.
