How to Fix WiFi Connected but No Internet
When your phone or laptop says 'Connected to Wi-Fi, No Internet' (or displays a globe icon with an exclamation mark), it simply means the local 802.11 wireless radio link between your device and the access point succeeded, but a check to an external internet server failed. Running a 60-second 3-Ping Isolation Test tells you immediately whether the break is in your LAN IP, your ISP modem, or your DNS resolver.
- Run the 3-Ping Test in order:
ping <gateway-ip>(LAN),ping 1.1.1.1(WAN routing), andping google.com(DNS). - If only one device has no internet, check for a
169.254.x.xAPIPA address, a stuck VPN kill switch, or a bad static IP/DNS entry. - If every device has no internet, inspect the ISP cable modem or fiber ONT optical lights and power-cycle the modem for 60 seconds.
- When replacing a router on cable/fiber internet, always reboot the ISP modem so it releases the old router's cached MAC address.
The 60-Second 3-Ping Isolation Test (LAN vs. WAN vs. DNS)
Instead of randomly rebooting devices and changing WiFi settings, open a terminal or Command Prompt on a connected computer and run three sequential ping commands. Where the pings stop succeeding reveals the exact layer that failed:
- Test 1 — Ping Your Router Gateway (e.g.,
ping 192.168.1.1): Tests Layer 2 WiFi and Layer 3 LAN IP addressing. If this fails, your device has a bad IP (169.254.x.x), an IP conflict, or WiFi client isolation. - Test 2 — Ping an External IP Directly (
ping 1.1.1.1): Tests whether packets can route out your router's WAN port through the ISP modem to the internet without needing DNS. If Test 1 works but Test 2 fails, your ISP connection or modem-to-router WAN link is down. - Test 3 — Ping a Domain Name (
ping google.com): Ifping 1.1.1.1replies in 12ms butping google.comsays Could not find host, your internet line is fine—only your DNS server is down!
Scenario A: Single Device Affected (APIPA 169.254.x.x, VPN or Date/Time)
If your TV and phone are streaming fine while a single laptop says "No Internet," do not touch the router or modem—the fault is local to that one endpoint:
- APIPA (
169.254.x.x) DHCP Failure: Runipconfig/ifconfig. If your IP starts with169.254, your device failed to get a DHCP lease from the router (either because you typed a slightly wrong WiFi password on a router without WPA3 SAE feedback, or the router's DHCP pool is full). Forget the network and rejoin, or runipconfig /release && ipconfig /renew. - Stuck VPN Kill Switch or Proxy: A crashed VPN background service blocks all traffic outside the tunnel. Open your VPN app, connect and disconnect cleanly, or disable its network adapter.
- Wrong System Clock: If a laptop's CMOS battery died and its date is set to 2021, every HTTPS connectivity check (
captive.apple.com,msftconnecttest.com) fails TLS certificate validation.
Scenario B: All Devices Offline (Modem Lights, Coax/ONT & MAC Lock)
When every device in the home or office shows "WiFi Connected, No Internet" and ping 1.1.1.1 times out, walk over to your physical ISP Cable Modem or Fiber ONT and inspect its status LEDs:
- Cable Modem (DOCSIS 3.1): The Power, Downstream (DS), Upstream (US), and Online lights must all be solid. If DS/US is blinking continuously, check for a loose coax barrel connector or damaged outdoor drop.
- Fiber ONT: Verify the PON / Optical light is solid green. A red LOS (Loss of Signal) light means the fiber glass strand is unplugged or cut upstream.
- Modem MAC Lock After Swapping Routers: Cable modems bind to the MAC address of the very first device plugged into their Ethernet port after boot. If you plugged in a brand-new router without power-cycling the cable modem for 60 seconds (including removing any backup battery), the modem will refuse to hand a WAN IP to the new router!
Scenario C: Ping 1.1.1.1 Works, But Websites Fail (DNS Fix)
ISP default DNS resolvers frequently crash during peak evening hours, leaving your router's WAN link completely healthy while every browser displays DNS_PROBE_FINISHED_NXDOMAIN and mobile OS status bars report "No Internet Connection."
When ping 1.1.1.1 succeeds while ping google.com fails, log into your router's web GUI (192.168.1.1 or 192.168.0.1), navigate to WAN / Internet Settings > DNS Server (and/or LAN > DHCP Server DNS), switch from "Obtain DNS Automatically from ISP" to Manual DNS, and enter Cloudflare (1.1.1.1 and 1.0.0.1) or Google Public DNS (8.8.8.8 and 8.8.4.4). Flush your local cache (ipconfig /flushdns) and websites will load immediately.
Configuring a primary and secondary public DNS provider from two independent networks (such as 1.1.1.1 and 8.8.8.8) ensures that a single resolver outage never interrupts web browsing across your LAN.
3-Ping Isolation Diagnostic Matrix for 'WiFi Connected, No Internet'
| Ping Gateway (192.168.1.1) | Ping External IP (1.1.1.1) | Ping Domain (google.com) | Exact Root Cause & Immediate Fix |
|---|---|---|---|
| FAIL (169.254.x.x IP) | FAIL | FAIL | LAN DHCP Failure: Forget/rejoin WiFi, check DHCP pool or AP backhaul |
| PASS (<5 ms) | FAIL (Request timed out) | FAIL | WAN / ISP Outage: Reboot ISP modem 60s, check WAN cable & ONT/Coax LEDs |
| PASS (<5 ms) | PASS (10–30 ms) | FAIL (Unknown host) | DNS Outage: Change router DNS to 1.1.1.1 & 8.8.8.8; run ipconfig /flushdns |
| PASS (<5 ms) | PASS (10–30 ms) | PASS (Yet browser blocked) | Local Software Block: Disable VPN Kill Switch, proxy, or fix system clock |
| FAIL (Destination unreachable) | FAIL | FAIL | Bad Static IP / Subnet Mask: Switch client network adapter back to Automatic DHCP |
'WiFi Connected, No Internet' Recovery Checklist
- Check whether the issue affects only a single device or every device connected to the router.
- Run ping
, ping 1.1.1.1, and ping google.com to isolate LAN vs WAN vs DNS failure. - Verify the affected device's IPv4 address is in your router's subnet (e.g., 192.168.1.x) and not 169.254.x.x (APIPA).
- Inspect the ISP fiber ONT (check for red LOS light) or cable modem (check for blinking DS/US lights).
- Perform a sequential power-cycle: unplug both modem and router, plug the modem in first, wait 2 minutes for solid Online LED, then power on the router.
- Configure reliable public DNS servers (1.1.1.1 and 8.8.8.8) on your router's WAN/DHCP settings so ISP DNS outages never knock you offline.
Frequently Asked Questions
Why does Windows or Android say 'Connected, no internet' when websites actually load fine?
Operating systems determine internet status by fetching a tiny plaintext file from a hardcoded probe URL (http://www.msftconnecttest.com/connecttest.txt on Windows, connectivitycheck.gstatic.com on Android, captive.apple.com on Apple). If a Pi-hole ad blocker, firewall rule, or DNS glitch blocks that specific probe domain, the OS shows a false 'No Internet' warning.
Why do I have to unplug the ISP modem before plugging in the router during a reboot?
If your router finishes booting in 45 seconds while your cable modem is still syncing DOCSIS channels for 90 seconds, the router's WAN DHCP client may time out or cache an internal modem diagnostic IP (192.168.100.x) instead of your public ISP IP. Waiting until the modem's Online light is solid guarantees a clean WAN lease.
Why does a WiFi range extender or mesh satellite show 'Connected, No Internet'?
Your phone is connected strongly to the extender's radio, but the extender itself has lost its wireless or wired backhaul connection to the main router—so the extender cannot forward your DHCP request or internet packets upstream. Reboot the extender and move it closer to the primary router.
Related Router Troubleshooting & Engineering Guides
- Router System Logs Beginner Guide: What to Look For — Decode your router system logs (syslog): separate harmless WAN port-scan background noise from genuine ISP PPPoE/DHCP drops, WiFi deauths, and IP conflicts.
- Static IP vs DHCP: When to Use Each on Your LAN — Learn when to use DHCP vs static IP addresses or DHCP MAC reservations on your LAN, how the DORA lease cycle works, and how to prevent IP address conflicts.
- DNS Settings on a Router — Configure router DNS settings using Cloudflare 1.1.1.1, Quad9 9.9.9.9, or Google 8.8.8.8. Understand WAN vs DHCP LAN DNS, DoH/DoT encryption, and DNS leaks.
- TP-Link Router Setup Guide (Archer, Deco & Omada) — Configure TP-Link Archer routers, Deco mesh nodes, and Omada SDN gateways via 192.168.0.1 or tplinkwifi.net with optimal WiFi, VLAN, and security settings.