When you click a link and get a timeout error, or the Wi-Fi icon shows an exclamation mark, where do you even start fixing it? Troubleshooting network connectivity is the systematic process of isolating why a device can't communicate across a network, and it is the single most practical skill you will use as a CompTIA A+ technician. For the 220-1201 exam, you must know the exact order of steps to diagnose a broken connection, from checking the physical cable to verifying DNS resolution.
Jump to a section
A simple way to picture Troubleshooting Network Connectivity
A local café with a single Wi-Fi access point. You are at a small café that has one Wi-Fi router for the whole shop. You sit down, pull out your phone, and try to connect to the café Wi-Fi.
First, you check that the Wi-Fi is actually broadcasting — you should see the café's network name (SSID) in your list, just like you check that the café is open before walking in. If you see it, you try to connect. If your phone fails to join, you think about what changed: maybe the password was updated and you're typing the old one, or maybe you're too far from the counter. That's a physical layer check — are you close enough to the router, and is the signal strong?
Next, if you join the network but can't load your email, you check if the connection actually works: can you reach the café's login page? That's the network layer — your device got an IP address (like a home address for your phone on the network), but maybe the router isn't forwarding traffic to the internet. The café owner might have to restart the modem (the box that brings internet into the café) or check if the internet bill was paid.
Finally, if everything works for other customers but not you, you check your own device: is your phone in aeroplane mode? Did your email app stop working because of a settings change? That's your application layer — the problem is inside your own phone, not the café's network. The process is always the same: start at the big problem (no signal), then move step by step inward until you find the single broken link.
Network connectivity troubleshooting is the process of figuring out why two devices cannot exchange data. It is like being a detective: you have a crime scene (the broken connection) and you need to find the single piece of evidence that explains the failure.
The most important framework to understand is the OSI model (Open Systems Interconnection model). For A+, you especially care about Layers 1, 2, 3, and 7. Layer 1 is the Physical layer — the actual cables, connectors, and wireless signals. If the cable is unplugged or the Wi-Fi antenna is broken, nothing higher up matters. Layer 2 is the Data Link layer, which handles how data frames travel between directly connected devices using MAC addresses (Media Access Control addresses — a unique hardware ID burned into every network card). Layer 3 is the Network layer, where IP (Internet Protocol) addresses live and routing happens. Layer 7 is the Application layer, where your web browser, email client, and other programs actually send and receive data.
The standard troubleshooting methodology taught for 220-1201 is: identify the problem, establish a theory of probable cause, test the theory, establish a plan of action, implement the fix, verify full system functionality, and document everything. But for network issues specifically, you usually follow a more practical checklist.
Start by checking the physical connection. Is the Ethernet cable firmly plugged into both the computer and the wall port or switch? If the cable is damaged, the link lights on the network interface card (NIC — the hardware port on the computer) will be off or blinking amber instead of steady green. For wireless, check that Wi-Fi is enabled on the device and that aeroplane mode is off.
Next, check that your device has an IP address. If your network interface shows an Automatic Private IP Addressing (APIPA) address (starting with 169.254.x.x), that is a huge clue. It means your computer tried to get an IP from a DHCP server (Dynamic Host Configuration Protocol — a server that automatically assigns IP addresses) but no server responded. That usually means the router or DHCP server is down, or the cable between your device and the router is broken.
Then, verify connectivity to the local gateway. The default gateway is the router's IP address that connects your local network to the internet. Use the ping command (a tool that sends a small data packet to a target and waits for a reply) to ping the gateway. If that works but you cannot reach an internet site like 8.8.8.8 (Google's public DNS server), the problem is likely beyond your router — maybe your internet service provider (ISP) is down.
If you can ping by IP address (like 8.8.8.8) but not by a domain name (like google.com), the issue is DNS resolution. DNS (Domain Name System) translates human-readable names like www.google.com into the numeric IP addresses computers use. Your computer might have a bad DNS server setting, or the DNS server itself could be unavailable. You can try flushing the DNS cache (a temporary storage of recent name resolutions) using the command "ipconfig /flushdns" on Windows.
Other common issues include incorrect subnet masks (a number that tells your device which part of an IP address is the network part and which is the host part), duplicate IP addresses (two devices accidentally assigned the same IP), or a firewall blocking traffic. A firewall is software or hardware that filters incoming and outgoing network traffic based on rules. Sometimes, Windows Firewall or a third-party security suite will block normal traffic.
For wireless networks specifically, interference from other devices (microwaves, cordless phones, other Wi-Fi networks) can cause intermittent connectivity. The channel width (how much of the radio spectrum the Wi-Fi uses) and signal strength are key factors. Tools like Wi-Fi analysers can show you which channels are crowded.
Finally, always consider the users. Did they change a setting? Did they install new software that messed with the network stack? Did they accidentally turn off the network adapter? The human factor is often the real culprit.
Identify the Problem
Gather information from the user: what exactly is not working? Is it one website, all websites, email, or everything? When did it start? Did anything change recently (new software, moved equipment, storm)? This step sets the direction for all following steps.
Establish a Theory of Probable Cause
Based on the symptoms, list the most likely causes. For example, if only one computer cannot connect, suspect a local issue (cable, NIC, settings). If many computers are affected, suspect a shared resource (router, switch, ISP). Prioritise common causes first.
Test the Theory
Use tools like ping, ipconfig, and nslookup to confirm or eliminate the suspected cause. Check link lights. Try swapping a cable. Ping the default gateway. If the theory is confirmed, move to the next step. If not, go back to step 2 with a new theory.
Establish a Plan of Action and Implement the Fix
Decide on the specific fix based on your findings. For example, if you found a faulty cable, plan to replace it. If you found a DNS misconfiguration, plan to correct the DNS server addresses. Implement the fix carefully, one change at a time.
Verify Full System Functionality and Implement Preventative Measures
After the fix, test that the original problem is resolved. Also test related functions — can the user access email, printers, and file shares? If possible, implement a preventative measure, like labelling cables or updating documentation.
Document Findings, Actions, and Outcomes
Write down what the problem was, what you checked, what you changed, and the final result. This helps with future troubleshooting, creates a knowledge base for other technicians, and is required for certification exam methodology.
You are the sole IT support person for a small accounting firm with 20 employees. At 9:30 AM, the receptionist calls: 'The internet is down. Nobody can access email or our cloud accounting software.' You walk over to the reception desk. Here is your real-world process:
First, you ask a simple question: 'Is it just this one computer, or is it everyone?' The receptionist says everyone is complaining. That narrows the problem to a shared resource — likely the router, the internet connection, or a major piece of network infrastructure.
You go to the server room. You check the main switch (the device that connects all the computers in the office). The power light is on, but the link light for the uplink port (the port connecting the switch to the router) is off. That suggests the cable between the switch and the router is dead, or the router has lost power. You check the router — it has power, but the 'Internet' light is red. That means the router cannot reach the ISP.
You pick up your phone and call the ISP support number. While waiting, you reboot the router and modem (a device that converts signals from the ISP into a signal your network can use). When they come back online, the 'Internet' light turns green. You check a workstation — the internet works. You document the fix: 'Router and modem required reboot after unknown ISP outage. Full connectivity restored at 9:45 AM.'
But later that afternoon, the same receptionist calls again. This time, only her computer cannot access the internet. Everyone else is fine. Now you are troubleshooting a single-device issue.
You stand at her desk. You check the physical cable — it is plugged into the wall port and her computer. The link light on her computer's network port is off. You wiggle the cable — nothing. You replace the cable with a known-good spare from your drawer. The link light turns on, and her internet works. The old cable had an internal break, likely from being stepped on.
Other common real-world scenarios include:
A user cannot connect to the company VPN (Virtual Private Network, a secure tunnel to the office network) from home. You check their internet connection first, then verify that the VPN client software is up to date and that their login credentials are correct.
A conference room has no Wi-Fi signal. You use a smartphone app to check signal strength near the access point (a device that broadcasts Wi-Fi). You find the access point is unplugged — a cleaner likely bumped the power cord.
A printer cannot be found on the network. You ping the printer's IP address — no reply. You check the printer's network settings menu and discover it has an APIPA address (169.254.x.x), which means it could not reach the DHCP server. You reboot the printer, and it picks up a correct IP address.
The 220-1201 exam will test your ability to think through network troubleshooting steps in a logical order. You will see scenario-based questions that describe a symptom (e.g., 'A user can browse the internet but cannot receive email') and ask you to identify the most likely cause or the best next step.
The exam loves to test these specific concepts:
- The meaning of an APIPA address (169.254.x.x). If a question describes a computer with an IP starting with 169.254, the correct answer is almost always 'The DHCP server is unavailable' or 'The computer cannot reach the DHCP server'. - The difference between being able to ping by IP address and not being able to ping by domain name. This points directly to a DNS failure. - The order of the OSI layers, especially Physical vs. Network vs. Application. If a cable is unplugged, that is Layer 1. If a web server is down, that is Layer 7. - The use of specific command-line tools: - ping (basic connectivity check) - ipconfig /all (shows IP address, subnet mask, default gateway, DNS servers) - nslookup (queries DNS servers directly) - tracert (traces the path packets take to a destination) - netstat (shows active connections and listening ports)
Common wireless issues: SSID not broadcasting (the network name is hidden), wrong security type (WPA2 vs. WEP), interference from Bluetooth or microwaves, incorrect passphrase, and channel congestion.
Traps the exam sets:
They might describe a problem that sounds like DNS but is actually a physical issue. Read the clues carefully: if the user says 'the internet is completely dead' and no websites load by IP or name, it is not DNS.
They might present multiple possible causes and ask for the 'most likely' based on the symptom. Remember the 80/20 rule: loose cables, bad power supplies, and simple misconfigurations are far more common than failed hardware.
They might include a distractor like 'update the firmware' or 'replace the NIC' when the real fix is to check if the cable is plugged in. Always start with the simplest, cheapest check.
They might test your understanding of 'link lights' — if the link light is off, the physical connection is bad. If it is blinking rapidly, there is data activity. If it is solid, the connection is established but idle.
They love to ask about 'loopback address' (127.0.0.1). Pinging 127.0.0.1 tests whether the TCP/IP stack on your own computer is working correctly. If it fails, your networking software is corrupt.
Key definitions to memorise for the exam:
DHCP: assigns IP addresses automatically
DNS: resolves domain names to IP addresses
APIPA: self-assigned IP when DHCP is unreachable
Default gateway: the router that connects your LAN to other networks
Subnet mask: determines which part of an IP is the network and which is the host
Loopback address: 127.0.0.1, used to test the local network stack
Always start troubleshooting at Layer 1 (Physical) — check cables, link lights, and power before blaming software.
A 169.254.x.x IP address (APIPA) always means the device could not reach a DHCP server.
If you can ping by IP address but not by domain name, the problem is DNS resolution.
Pinging 127.0.0.1 (loopback) tests that your own computer's TCP/IP stack is working correctly.
The default gateway is the router that connects your local network to other networks, including the internet.
Wireless issues can be caused by interference from microwaves, cordless phones, or neighbouring Wi-Fi networks, not just the router itself.
Document every step of your troubleshooting process — it helps with complex issues and is required for CompTIA's methodology.
When diagnosing a single-user issue, check that user's physical connection first before touching shared infrastructure.
These come up on the exam all the time. Here's how to tell them apart.
APIPA Address (169.254.x.x)
Indicates DHCP server was unreachable
Only valid for local link communication, no internet access
Self-assigned by the device automatically
DHCP-Assigned Address
Provided by a DHCP server (usually the router)
Allows full internet and network access
Manually or automatically configured within a valid subnet
Ping by IP Address
Tests Layer 3 connectivity to a specific host
Does not require DNS to work
Fails if the remote host is down or a firewall blocks ICMP
Ping by Domain Name
Tests both DNS resolution and Layer 3 connectivity
Will fail if DNS is not working, even if the host is reachable
Requires a correctly configured DNS server
Wired (Ethernet) Connection
More stable and faster with less interference
Troubleshooting focuses on cables, ports, and link lights
Physical security: must be physically connected to the network
Wireless (Wi-Fi) Connection
Prone to interference from other devices and walls
Troubleshooting includes signal strength, channel congestion, and security keys
Convenient for mobility but less secure without encryption
ipconfig /all
Displays detailed network configuration information
Useful for verifying IP, subnet mask, gateway, and DNS settings
Does not test connectivity to other devices
ping 127.0.0.1
Tests the local TCP/IP stack on your own computer
Confirms your network software is installed and working
If it fails, the network stack is corrupted and needs repair
Modem
Connects your home/office to the internet service provider
Converts the ISP signal (cable, fibre, DSL) into a network signal
Usually has only one network port for a single device
Router
Routes traffic between multiple devices on your local network
Assigns IP addresses via DHCP and provides firewall functions
Has multiple LAN ports and often includes Wi-Fi access
Mistake
If I can ping a website by IP address, my internet connection is fully working.
Correct
Pinging by IP only proves Layer 3 connectivity to that specific host. DNS, firewall rules, or the application itself could still be broken.
Beginners often equate basic IP connectivity with full end-to-end functionality, forgetting that DNS translation and application-level protocols are separate layers.
Mistake
A slow internet connection means I need to replace the router or upgrade my internet plan.
Correct
Slow connectivity can be caused by many things: Wi-Fi interference, a congested channel, too many devices using bandwidth, a bad Ethernet cable, or even a failing hard drive on one computer.
Marketing and 'common sense' suggest that slow = old hardware, but network troubleshooting requires first ruling out interference and configuration issues before spending money.
Mistake
Restarting the computer always fixes network issues because it resets the network settings.
Correct
Restarting the computer often helps because it re-initialises the network adapter and clears transient states, but it does not fix hardware failures, bad cables, or DHCP server outages.
People have been trained that 'turn it off and on again' is a universal fix, but it only addresses software-related transient problems, not persistent infrastructure issues.
Mistake
If my Wi-Fi signal shows full bars, the internet should be fast and reliable.
Correct
Signal strength (bars) only indicates the strength of the radio signal, not the speed or reliability of the connection. High interference or a congested channel can give full bars but terrible performance.
Wi-Fi bars are a visual simplification. Users naturally assume more bars = better internet, but troubleshooting must differentiate between signal strength and actual data throughput.
Mistake
A 169.254.x.x address means my network card is broken.
Correct
A 169.254.x.x address means the computer could not reach a DHCP server. The network card is likely fine, but the DHCP server (often the router) is down, unreachable, or misconfigured.
When users see 'limited connectivity' and a strange IP, they panic and blame the computer hardware. In reality, the computer is working exactly as designed — it gave itself a fallback address.
Mistake
If one computer on the network cannot connect to the internet, the problem must be with the router or internet service.
Correct
If only one computer is affected, the problem is almost certainly local to that device — a bad cable, a disabled network adapter, incorrect IP settings, or software blocking the connection.
Beginners think of the internet as a single binary resource (on/off). They don't consider that each device has its own path to the router and its own settings.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
It means your computer has a network connection to the local router but cannot reach the internet. This could be because the router itself cannot connect to the internet, your DNS settings are wrong, or your IP configuration is incorrect.
Ping tests if a remote host is reachable and measures the round-trip time. Tracert (or traceroute) shows the path your data takes hop-by-hop from your computer to the destination, revealing where delays or failures occur along the route.
Open Command Prompt and type 'ipconfig'. Look for the line that says 'IPv4 Address' under your active network adapter (Wi-Fi or Ethernet). This is your computer's current IP address on the local network.
First, try pinging the website's IP address (e.g., 8.8.8.8). If that works, the problem is likely DNS — try flushing your DNS cache with 'ipconfig /flushdns'. If pinging the IP also fails, check your firewall settings or try a different browser.
A DHCP server automatically assigns IP addresses, subnet masks, default gateways, and DNS server addresses to devices on a network. Without it, you would have to manually configure every device, which is impractical for all but the smallest networks.
The problem is likely with the laptop's Wi-Fi adapter, its driver, or its configuration. Try forgetting the network and reconnecting, updating the wireless driver, or checking that aeroplane mode is off. If other devices work fine, the issue is local to the laptop.
You've just covered Troubleshooting Network Connectivity — now see how well it sticks with free 220-1201 practice questions. Full explanations included, no account needed.
Done with this chapter?