Troubleshooting common Wi-Fi connection problems at home: what I check before I touch the router
The message that lands in my inbox most often is some version of this: "My Wi-Fi is broken." Then, two minutes later, the person mentions that their partner is streaming Netflix in the next room without a single hiccup. That detail changes everything. It means the network isn't broken. Something between that one device and the router is.
Most home Wi-Fi troubleshooting fails because people skip the first, unglamorous step: isolating what's actually broken. Router? Internet line? One device? One band? The fix depends entirely on which of those four answers is true, and restarting your router for the fifth time in an hour won't tell you.
What follows is the order I actually work through when a connection drops, plus the quick fixes most guides repeat without explaining why they work.
Key Takeaways
- Test one device against another before you change anything — if only your phone fails, the router is probably fine.
- Restart order matters: modem first, then router, then devices. Doing it backwards undoes the fix.
- Wired vs wireless is the fastest split-test you have. Plug in a laptop and see what happens.
- 2.4 GHz travels farther and through more walls; 5 GHz is faster but fragile. Wrong band is a common culprit.
- Drivers, IP conflicts, and power-saving settings cause "connected but no internet" more often than hardware failure.
- If a full restart fixes nothing and only one device is affected, look at that device's network adapter before blaming the router.
What are the most common Wi-Fi problems?
After enough house calls — friends, family, the neighbour who caught me carrying a network cable to my car — a clear pattern emerges. The symptoms repeat, and so do the causes behind them.
The recurring symptoms
- Slow speeds at certain times of day, usually evening when everyone in the building is online.
- Signal dropping in one specific room, while the rest of the house is fine.
- A device showing "connected" with no actual internet access.
- Connection failing entirely, often right after a power cut or a firmware update.
- Intermittent disconnects that last a few seconds, then resolve themselves.
The causes are less varied than the symptoms. Physical distance and building materials explain most dead zones — concrete and metal mesh in walls absorb the signal far more than drywall does. Channel congestion explains the evening slowdowns: your neighbours' routers compete for the same frequencies. And outdated firmware or drivers explain a surprising share of everything else. I once watched a friend's connection stabilise simply by moving the router off the floor and out from behind a metal shelf unit. No new hardware, no settings touched.
Why restarting actually works
The classic advice — unplug, wait, plug back in — isn't folklore. A router holds temporary state: routing tables, DHCP leases, cached DNS entries. Over days or weeks, that state gets stale or corrupted, and the router keeps making decisions based on outdated information. A power cycle clears it.
The catch is the order. Unplug the modem, then the router, then wait a full 60 seconds. Power the modem back on first and give it a minute to reconnect to your provider before switching the router on. I made this mistake for years — restarting both at once, which meant the router tried to reach an internet connection that didn't exist yet. That's the origin of a lot of "I restarted it and it still doesn't work."
What are the 10 common network problems?
Not every problem is a Wi-Fi problem, and confusing the two wastes time. Here's the list I mentally run through, roughly in order of how often I encounter each one.
| Problem | Typical symptom | First thing to check |
|---|---|---|
| Router needs a restart | Everything slow or offline at once | Power cycle, modem first |
| Distance or obstacles | Weak signal in one area | Router placement, walls, furniture |
| Channel congestion | Slow evenings, fine mornings | Nearby networks on the same channel |
| Band mismatch | Device connects to slow network | 2.4 vs 5 GHz availability |
| Outdated firmware | Random disconnects, security gaps | Router admin panel |
| Stale network driver | One device fails, others fine | Device's network adapter settings |
| IP address conflict | "Connected, no internet" | DHCP settings, static IPs |
| DNS failure | Pages won't load, apps still work | Try a public DNS server |
| ISP outage | Nothing works, wired included | Your provider's status page |
| Power-saving mode | Wi-Fi drops when idle | Device's battery/power settings |
That last one gets overlooked constantly. Laptops and phones aggressively cut power to their Wi-Fi chip when idle, and some chipsets handle that badly — you get a dropout every few minutes that looks like a router fault. Digging into the adapter's power management settings and disabling the "allow the computer to turn off this device to save power" option has fixed this for me more than once.
The wired-vs-wireless test
Plug a laptop directly into the router with an Ethernet cable. If the connection is solid, your internet line is fine and the problem lives in the wireless side — placement, band, interference. If it's still broken with a cable, no amount of Wi-Fi tinkering will help. The issue is upstream: modem, cabling, or your provider. This single test saves more time than any other step, and it takes ninety seconds.
Why is my Wi-Fi not working but it is for everyone else?
This is the scenario that confuses people most, and it's the one where you should stop touching the router entirely. If every other device in the house connects normally, the network is working. The failure is local to one device, and that narrows the list of suspects dramatically.
The device-side checklist
- Toggle airplane mode on and off. It forces the radio to re-scan and reconnect. Sounds trivial. Works more often than it should.
- Forget the network and rejoin. A corrupted saved profile — wrong password stored, stale security settings — produces exactly the "connected but useless" behaviour.
- Check the band. Older devices and some cheaper chipsets only see 2.4 GHz. If you recently split your network names or disabled the 2.4 GHz band to force everyone onto 5 GHz, that device drops off.
- Update the network driver. This is the number-one cause I find on Windows laptops. A driver that worked with an older access point can misbehave against a new one, especially after a router firmware update.
- Look for conflicting software. VPN clients, virtual machine adapters, and some security suites install their own network layers that hijack traffic.
I'll admit I once spent an entire evening convinced my router had died, only to discover my phone had a VPN profile left active from a work trip. Everything else on the network was fine, because that VPN only intercepted traffic on my phone. The router was innocent.
How do I run diagnostics on my Wi-Fi?
You don't need professional tools for most home problems. What you need is to measure the right things: signal strength where you actually use the connection, speed at the router versus at the far end of the house, and which channels your neighbours are occupying.
A diagnostic sequence that works
- Measure signal where the problem is. Walk with your phone and watch the signal indicator. A sharp drop behind one wall points to an obstacle, not a router fault.
- Run a speed test twice — once standing next to the router, once in the room that misbehaves. The gap between those two numbers tells you whether you have a coverage problem or an overall capacity problem.
- Generate a wireless network report. On Windows, the built-in report shows every disconnect event, the reason code, and the signal strength at the moment of failure. On macOS, hold Option while clicking the Wi-Fi menu to reveal the detailed metrics.
- Scan the surrounding channels. Most router admin panels include a channel scanner. If your network sits on the same channel as four of your neighbours', move it.
- Interpret the numbers. A download speed far below your plan's rating while standing next to the router points upstream. Full speed there but a fraction of it across the house points to coverage.
The "connected, no internet" message deserves its own line. It means the device reached the router, but the router couldn't reach the wider internet. That's usually DNS or DHCP, not Wi-Fi. Switching to a public DNS server resolves a large share of these cases, and it takes about a minute.
When to stop diagnosing and call someone
If a wired connection to the router also fails, if the modem shows no sync light, or if the problem appeared right after a storm, the fault is outside your house. Call your provider. No router reset will bring back a line that's physically down.
For everything else, work through it in order — device, then band, then placement, then router, then line — and you'll almost always land on the answer before you've finished your coffee. The router is usually not the villain. It just takes the blame because it's the box with the blinking lights.
