Few tech messages are as maddening as “Connected, no internet.” Your phone or laptop shows full Wi-Fi bars, the router is humming away, and yet nothing loads. According to Wikipedia’s overview of the Domain Name System, DNS acts as the internet’s phone book, and it’s the single most common reason a device shows a healthy Wi-Fi connection while the web stays unreachable.
The good news: this problem follows predictable patterns, and most cases can be fixed in under ten minutes without calling your provider. This guide walks through what actually works, in the order that saves the most time, plus the mistakes that keep people stuck in circles.
What “Connected, No Internet” Really Means
Before touching anything, it helps to understand the message. When your device joins a Wi-Fi network, it typically completes two separate jobs:
- Joining the local network. The router hands out an IP address via DHCP, and the device authenticates with the Wi-Fi password.
- Reaching the internet. Traffic must pass through the router, out to the modem, and on to your ISP.
“Connected, no internet” means step one succeeded and step two failed. Your device has a local address but can’t reach the outside world. That distinction narrows the suspects dramatically: DNS, the router’s upstream link, the modem, the ISP, or something on the device itself blocking traffic.
Start With the Two-Minute Checks
Before diving into settings, rule out the obvious. These quick checks solve a surprising share of cases.
- Try a second device. If your phone also shows no internet, the problem is the network or ISP. If only the laptop fails, the problem is the device.
- Check for a captive portal. Hotels, airports, cafés, and even some home guest networks require you to accept terms on a login page. Open a browser and try to load any site; if a sign-in page appears, that’s your answer.
- Look at the modem lights. A solid or blinking “online” or “internet” light is good. A red or dark light usually points to a provider-side fault.
- Ask your ISP’s status page. Outages are more common than people assume, and a quick check can save an hour of pointless tinkering.
If those don’t resolve it, move to the fixes below in order. Each one targets a specific layer of the failure.
Fix 1: Power-Cycle the Router and Modem in the Right Order
This is the oldest advice in networking, and it still works because it clears stale leases, hung processes, and half-open connections. But the order and timing matter, and most people rush it.
- Unplug the modem’s power. Leave the router plugged in for now.
- Wait a full 30 seconds. This lets capacitors drain and the ISP’s session time out cleanly.
- Plug the modem back in and wait for its online light to go solid. This can take two to three minutes.
- Now unplug the router, wait 30 seconds, and plug it back in.
- Give devices a minute to reconnect, then test.
Power-cycling the router alone often isn’t enough, because the modem may still be holding a bad session with the provider. Doing it in sequence, with patience, is what actually clears the fault.
Fix 2: Test and Change Your DNS
If the router is fine but pages won’t load, DNS is the prime suspect. A quick test: open a browser and try to load a site by its raw IP address rather than its name. If the IP loads but the name doesn’t, DNS is broken.
The fix is to point your device or router at a public DNS resolver. Two widely documented options are Google Public DNS (8.8.8.8 and 8.8.4.4) and Cloudflare’s 1.1.1.1. You can set these in your router’s admin panel (usually under WAN or Internet settings) so every device benefits, or per-device in your network settings.
On Windows, you can also flush the local DNS cache from an elevated command prompt. On macOS, the command differs by version, so check your specific release rather than copying a command blindly. After changing DNS, flush the cache and reconnect. (Wi-Fi)
One caveat: switching DNS is sometimes a workaround rather than a root-cause fix. If your ISP’s DNS keeps failing, a public resolver masks the problem but doesn’t repair it. That’s fine for most households, but worth knowing.
Fix 3: Rule Out IP Conflicts and Stale Leases
Every device on your network needs a unique IP address. If two devices claim the same one, or your device is holding an expired lease, you get exactly this symptom: connected, no internet.
The standard fix is to release and renew the lease, or simply reboot the device. On Windows, this is done through the network adapter settings or command line. On phones, toggling Wi-Fi off and on, or forgetting and rejoining the network, usually does the trick.
If the problem keeps returning, check your router’s DHCP pool. A pool that’s too small for the number of devices in the house causes repeated conflicts. Widening the range, or assigning a static IP to a stubborn device, resolves it. Note that a static IP is a workaround, not a repair; if you’re constantly fighting conflicts, the router’s DHCP configuration deserves a proper look.
Fix 4: Handle VPNs, Proxies, and Security Software
A VPN that’s connected but not routing properly will leave you with a perfect Wi-Fi signal and zero internet. The same goes for a misconfigured proxy or overly aggressive firewall rules.
- Disconnect the VPN entirely and test. If the internet returns, the VPN is the culprit; reconnect or switch servers.
- Check proxy settings. On Windows, look under Settings > Network & Internet > Proxy. On macOS, check System Settings > Network > Proxies. A leftover proxy from a work profile or old software is a common trap.
- Temporarily disable third-party firewalls or antivirus network shields to see if they’re blocking traffic. If they are, add an exception rather than leaving protection off.
This is also a good moment to think about your broader setup. A reliable security suite configured correctly prevents both intrusions and self-inflicted outages, and it’s worth comparing options if yours is causing friction. Guides on the best internet security and the best internet security australia options can help you choose one that doesn’t fight your network.
Fix 5: Update Network Drivers and Reset the Adapter
On Windows laptops especially, an outdated or corrupted Wi-Fi driver can produce the connected-but-no-internet state even when the network is perfectly healthy. The telltale sign: every other device in the house works fine.
- Open Device Manager and find your network adapter.
- Right-click and update the driver, or download the latest version from the manufacturer’s site.
- If updating doesn’t help, try disabling and re-enabling the adapter.
- As a last resort, use the network reset option in Windows settings, which wipes and reinstalls all network components. You’ll need to re-enter Wi-Fi passwords afterward.
On phones, “forget this network” followed by a fresh join achieves a similar reset. It sounds trivial, but it clears saved configuration errors that survive ordinary reboots.
Fix 6: Check Date, Time, and Browser-Level Issues
Here’s one almost nobody suspects: an incorrect system clock. If your device’s date and time are badly off, secure connections fail, and browsers may report that the internet is unreachable even though packets are flowing fine. Set the clock to update automatically and retry.
Similarly, a browser with a broken extension, corrupted cache, or strict security setting can mimic a dead connection. Test in a different browser or a private window. If the second browser works, the problem is local to the first one, and clearing its cache or disabling extensions fixes it.
Fix 7: When the Problem Is Outside Your House
If you’ve worked through everything above and other devices also fail, the fault is likely upstream: a provider outage, a damaged line, or an account issue. Check the modem’s indicator lights against your ISP’s documentation, and contact support with specifics. “My Wi-Fi says connected but there’s no internet, and the modem’s online light is red” gets you much faster help than “the internet is broken.”
For households that depend on a stable link, it’s worth understanding what a good connection actually looks like. If gaming or video calls matter, resources on the best internet for gaming explain the latency and stability factors that generic speed tests miss. And if you’re setting up a new network or renaming an old one, a guide to the best name wifi helps you avoid confusing SSIDs that make troubleshooting harder later. (Broadband Speed Guide)
Common Mistakes That Keep People Stuck
After years of watching people troubleshoot this exact problem, certain patterns repeat:
| Mistake | Why it backfires | Better approach |
|---|---|---|
| Rebooting the router repeatedly without touching the modem | The modem keeps the bad session alive | Power-cycle modem first, then router |
| Changing ten settings at once | You can’t tell what fixed or broke it | Change one thing, test, then move on |
| Disabling IPv6 permanently as a “fix” | It’s a workaround that can cause other issues | Use it only to diagnose, then revert |
| Assuming the ISP is down before checking locally | Wastes hours waiting for a fix you could do yourself | Test a second device first |
| Ignoring the device clock | Breaks TLS and mimics no internet | Enable automatic time sync |
The single most useful habit is isolating the layer: is the failure on the device, the local network, or the provider? Every fix above flows from answering that question correctly.
A Quick Diagnostic Order That Saves Time
When the message appears again, work top to bottom:
- Second device test (device vs. network).
- Captive portal check (open a browser).
- Modem and router power cycle, in order.
- DNS test and swap to a public resolver.
- Release/renew IP or rejoin the network.
- VPN and proxy check.
- Driver update or network reset.
- Clock and browser check.
- ISP status and support call.
Most people never reach step five. The ones who do usually find the answer by step six.
Conclusion
“Connected, no internet” feels like a contradiction, but it’s actually precise information: your device reached the router and stopped there. That narrows the problem to DNS, the modem’s upstream link, the provider, or something on the device blocking traffic. Work through the layers in order, change one variable at a time, and resist the urge to toggle a dozen settings at once. In practice, a patient power cycle, a DNS swap, or a driver update resolves the vast majority of cases. When it doesn’t, the fault is usually outside your walls, and a specific, well-described call to your provider gets it fixed fastest.
Frequently Asked Questions
Why does my Wi-Fi say connected but there’s no internet?
It means your device joined the local network successfully but couldn’t reach the internet beyond the router. The usual causes are a DNS failure, a stale IP lease, a modem that lost its upstream connection, an ISP outage, or a VPN or proxy blocking traffic.
How do I know if the problem is my device or my provider?
Test a second device on the same Wi-Fi. If both fail, the issue is the network or provider. If only one fails, the problem is local to that device, such as a driver, DNS setting, or proxy configuration.
Can changing DNS really fix a “no internet” error?
Yes, often. If your device can reach websites by IP address but not by name, DNS is the culprit. Switching to a public resolver like Google Public DNS or Cloudflare’s 1.1.1.1 usually restores browsing immediately.
Why does my Wi-Fi drop to “no internet” only on my laptop?
Laptop-specific causes include outdated Wi-Fi drivers, a corrupted adapter state, aggressive power-saving settings that disable the adapter, or a leftover proxy or VPN profile. Updating the driver or performing a network reset typically resolves it.
Does restarting the router actually help, or is it a myth?
It genuinely helps, but order matters. Unplug the modem first, wait about 30 seconds, let it reconnect fully, then power-cycle the router. Restarting only the router often leaves a bad modem session intact.
What should I do if nothing works and my provider says there’s no outage?
Ask the provider to check the line and your account status, and describe your modem’s indicator lights precisely. If the line tests clean, request a technician visit; persistent upstream faults often require physical inspection of cabling or equipment.
