CompTIA A+ 1201 Objective 5.5: Troubleshoot Network Issues (Port Flapping, Latency, Wi-Fi Interference, Auth Failures, Intermittent Internet)
When a user says, "Wi-Fi drops and video calls lag," the cause isn't obvious. The same complaint can come from a bad cable, a noisy wireless channel, a DNS problem, or an ISP outage. That overlap is why CompTIA A+ 1201 Objective 5.5 focuses on method, not guesswork.
This guide gives a repeatable way to troubleshoot five common network issues: port flapping, high latency, external interference, authentication failures, and intermittent internet connectivity. The goal is to prove where the failure sits, then fix the lowest-risk item first.
A step-by-step approach also saves time under pressure. In practice, you'll often have limited access, limited time, and a user who needs the network back now.
Start with a fast triage checklist so you don't chase the wrong problem
Begin by tightening the problem statement. Vague reports create wasted effort. Ask what's failing (websites, VPN, email, voice), where it fails (one room, one floor, everywhere), and when it happens (all day, mornings, during rain, after sleep). Then check scope: is it one device, one switch port, one SSID, or the whole site?
Next, verify link status. On Ethernet, check the NIC and switch link lights. On Wi-Fi, check signal bars and whether the device stays associated to the SSID. Even before tools, these clues separate local link failures from upstream issues.
After that, confirm IP settings. A device with no valid IP, wrong gateway, or wrong DNS will look "offline" even with strong Wi-Fi. On Windows, ipconfig shows IP, mask, gateway, and DNS. On Linux and macOS, ifconfig or ip a fills the same role. Don't hunt for advanced causes until addressing obvious misconfiguration.
Finally, test reachability in layers:
- Ping the default gateway (your local hop).
- Ping a public IP (tests routing without DNS).
- Ping a DNS name (tests DNS resolution plus routing).
The tools below map directly to what the exam expects. This table sets the context, then you can interpret results with less guesswork.
| Tool | What you test | What a failure suggests |
|---|---|---|
| ipconfig/ifconfig | IP, gateway, DNS, link status | DHCP issue, wrong settings, disconnected interface |
| ping | Basic reachability and delay | Local link problem, upstream routing, or latency |
| tracert/traceroute | Path and hop delays | ISP issues, routing problems, congestion points |
| nslookup/dig | DNS resolution | DNS server issue, wrong DNS, captive portal effects |
| Speed test | Throughput up and down | Saturation, ISP limit, Wi-Fi quality issues |
| Router/switch/AP logs | Link events, auth errors | Port flapping, WPA issues, 802.1X failures |
In short, each test proves one layer. If ping to the gateway fails, stay local (cable, Wi-Fi, switch, IP). If the gateway works but DNS names fail, focus on DNS. If everything works but performance stinks, investigate latency, interference, or saturation.
A good troubleshooting habit is to change one thing at a time, then re-test the same way.
Quick signs that point to the root cause
Some symptoms are like fingerprints. If Ethernet link lights drop and return, suspect a cable, jack, or switch port. If performance is slow on every device, including wired, suspect latency or an ISP problem. If only Wi-Fi struggles while Ethernet stays clean, interference or poor access point placement rises to the top.
Repeated password prompts often point to authentication failures, such as a wrong key, wrong security type, or account lockout. If the network works for hours, then drops for a minute and returns, think intermittent connectivity, such as DHCP lease trouble, overheating gear, or ISP flaps.
Treat these as starting points, not verdicts. You still confirm with tests and logs.
Port flapping: when a switch port keeps going up and down
Port flapping means a switch port rapidly changes state, up, down, then up again. For a user, it feels like the network "blinks." File transfers reset, remote sessions drop, and VoIP calls cut out. Even short drops matter because devices must re-negotiate link speed, renew DHCP at times, and rebuild sessions at higher layers.
Several common causes show up in real support work:
- A bad patch cable (kinked, crushed, or poorly terminated)
- A loose connector or damaged wall jack
- A failing NIC or a port with worn contacts
- Speed or duplex mismatch (less common on modern auto-negotiation, but still possible)
- NIC power-save settings that put the adapter to sleep
- A failing switch port or a marginal SFP on fiber links
Start with what's simple and safe. Swap the patch cable with a known-good cable. Reseat both ends until they click. If the issue persists, move the device to a different wall jack (if available), or move the switch-side connection to a different port.