Lesson 9: Troubleshooting Method and Network Troubleshooting
CompTIA A+ Core 1 (220-1201) · Objectives 220-1201 5.0, 220-1201 5.5 · Download .docx
Objectives
- Apply the CompTIA troubleshooting methodology in the right order, from identifying the problem to documenting findings.
- Troubleshoot wired and wireless network problems.
Key terms
- Intermittent wireless connectivity
- Wi-Fi connection that repeatedly drops and reconnects, often from weak signal, interference, roaming problems or overlapping channels.
- Slow network speeds
- Symptom where data transfers take much longer than expected, caused by congestion, bad cables, duplex mismatch, interference or ISP limits.
- Limited connectivity
- Symptom where a device connects to the local network but cannot reach the internet, often due to APIPA addressing or gateway problems.
- Jitter
- Variation in the delay of packets arriving over a network, which makes real-time voice and video choppy.
- VoIP
- Voice over Internet Protocol: technology that carries phone calls as data packets over IP networks instead of traditional phone lines.
- Poor VoIP quality
- Choppy, echoing, delayed or dropped calls on internet phone systems, caused by jitter, latency, packet loss or lack of traffic prioritization.
- Port flapping
- Switch port rapidly and repeatedly going up and down, usually from bad cables, faulty NICs, duplex mismatch or loops.
- High latency
- Long delay for data to travel from source to destination and back, measured in milliseconds, causing lag in games and calls.
- External interference
- Electrical or radio noise from sources like motors, microwaves, cordless phones or neighboring networks that disrupts signals.
- Authentication failures
- Inability to join a network or service because of wrong credentials, expired passwords, certificate problems or mismatched security settings.
- Intermittent internet connectivity
- Internet access that drops in and out while the local network stays up, often from modem, ISP line or router problems.
The concept
220-1201 5.0 — Apply the CompTIA troubleshooting methodology in the right order, from identifying the problem to documenting findings. Troubleshooting methodology order: The CompTIA sequence is: identify the problem; establish a theory of probable cause (question the obvious); test the theory; establish a plan of action and implement the solution; verify full system functionality; document findings. Researching a knowledge base or the internet is part of forming the theory. Theory not confirmed: When testing does not confirm a theory, the technician returns to the theory step and proposes a new probable cause, or escalates if the issue is beyond their skill or authority. The known-good cable test was still useful because it ruled out one cause. Identify the problem: Identifying the problem means gathering information: interviewing the user, asking about recent changes to the system or environment, reviewing logs, and duplicating the problem if possible. Good information here narrows the list of probable causes. Verify and prevent: Running the system under load confirms full system functionality, and scheduling filter cleaning is a preventive measure; both belong to Step 5 in the exhibit (verify full system functionality and, if applicable, implement preventive measures). Verification proves the fix worked for the whole system, not just the replaced part. Documentation step: The final step of the methodology is to document findings and lessons learned, actions, and outcomes. Good documentation builds a knowledge base so the next technician can fix the same issue faster, and it supports tracking trends across many devices. Plan of action: Once a theory is confirmed, the technician establishes a plan of action to resolve the problem and then implements it. A good plan considers the impact on users, organizational change policies, maintenance windows, and data protection (verified backups) before work begins.
220-1201 5.5 — Troubleshoot wired and wireless network problems. APIPA limited connectivity: An address in 169.254.0.0/16 with no default gateway is an Automatic Private IP Addressing (APIPA) link-local address. Windows assigns it when it asks for an address and no DHCP server answers. Ping results analysis: Replies from 192.168.1.1 show the local network and default gateway work. Timeouts to a public IP address show traffic is not getting past the router to the internet, and the name lookup failure follows because DNS queries cannot reach an internet DNS server either. Microwave interference: Microwave ovens leak energy around 2.45 GHz, which overlaps the 2.4 GHz Wi-Fi band and disrupts connections when the oven runs, here at lunchtime. Moving clients to 5 GHz avoids that interference. 2.4 GHz channel overlap: Each 2.4 GHz channel is about 20-22 MHz wide, but channel centers are only 5 MHz apart, so channel 3 overlaps both channel 1 and channel 6. Overlapping channels cause interference and retransmissions, which feel like slow, intermittent connectivity. Slow wired link speed: Gigabit Ethernet uses all four wire pairs, while 100 Mbps Ethernet needs only two. If one pair in the cable or jack is damaged, the NIC and switch fall back to 100 Mbps. Jitter definition: Jitter is the variation in latency from packet to packet. Real-time traffic such as voice and video needs packets to arrive at a steady pace; high jitter makes audio choppy or robotic even when average latency is acceptable.
Common mistakes
- Troubleshooting methodology order: choosing “Test the theory to determine the cause” is a common mistake. Testing comes after a theory exists; you cannot test a cause you have not yet proposed.
- High latency satellite: choosing “Fiber to the premises” is a common mistake. Fiber has very low latency, typically a few milliseconds to the ISP.
- Troubleshooting methodology order: choosing “Verify full system functionality” is a common mistake. Verification is done after a solution has been implemented, near the end of the process.
- Verify and prevent: choosing “Step 6” is a common mistake. Step 6 in the exhibit is documenting findings, actions, and outcomes; nothing was recorded in a ticket or knowledge base in this scenario.
- 2.4 GHz channel overlap: choosing “Channel 3 is only legal for outdoor use” is a common mistake. Channel 3 is a standard indoor channel in most regions.
- APIPA limited connectivity: choosing “IPv6 is disabled on the network adapter” is a common mistake. The output shows IPv6 is enabled; it has a link-local IPv6 address.
Self-check
Try each one before you look. A miss here costs nothing and tells you exactly what to reread.
Canvas is the official record. This companion enhances the PGCC curriculum; it does not replace it. Last name and class year only. Students with a 504 plan or IEP: your accommodations apply.