Study Wired, Wireless and Internet Connectivity Issues for A+ Core 1 (220-1201)
Diagnose DHCP, DNS, APIPA, gateway, Wi-Fi, cabling, and SOHO internet failures with the applied logic A+ Core 1 expects.
On this page
This is one of the most important troubleshooting lessons on Core 1 because networking clues often decide the answer faster than hardware clues do. A+ wants you to know whether the failure is link, addressing, Wi-Fi quality, gateway, or name resolution.
APIPA: Automatic private address in the
169.254.0.0/16range that often appears when DHCP-based configuration fails.
What CompTIA is really testing
The exam usually wants you to:
- classify the fault domain quickly
- use simple evidence before changing settings blindly
- distinguish wired, wireless, and service-layer failures
Symptom-first map
| Symptom | Strong first direction |
|---|---|
169.254.x.x address |
DHCP path problem |
| hostname fails but direct IP works | DNS problem |
| no link light | cable, port, or NIC path problem |
| weak or unstable Wi-Fi | RF interference, channel use, distance, or AP placement |
| one device works but others do not | client-specific settings or hardware, not total internet failure |
A better way to classify the failure
| If the clue is… | Think first about… |
|---|---|
| no link light or damaged connector | physical path |
169.254.x.x |
DHCP path |
| valid IP but no outside access | gateway, router, or upstream path |
| IP works but names fail | DNS |
| only wireless clients struggle | RF, SSID, security, band, or placement |
Minimal evidence workflow
1ipconfig /all
2ping 127.0.0.1
3ping 192.168.1.1
4nslookup comptia.org
What to notice:
- local stack checks differ from gateway reachability
- gateway tests differ from name-resolution tests
- you can narrow the problem without touching five settings first
Wireless-specific evidence still matters
1Check SSID and security mode
2-> check signal quality and channel crowding
3-> compare one-device versus all-device behavior
4-> only then escalate toward router or ISP blame
Harder scenario question
A user’s laptop shows a good Wi-Fi icon, but only this device cannot browse websites. Other devices on the same SSID work. The laptop has a self-assigned 169.254.x.x address.
The strongest answer usually:
- treats this as a client-side DHCP or settings issue first
- avoids blaming the ISP or replacing the router immediately
- uses the address clue to narrow the path before making changes
What strong answers usually do
- keep link, addressing, and naming issues separate
- choose the least disruptive test first
- remember that Wi-Fi quality problems are often RF or placement issues, not always ISP failure
- use one working device as a comparison clue instead of ignoring it
Quiz
Loading quiz…