Seeing full Wi-Fi signal bars accompanied by the dreaded 'Connected, no internet' or 'No Internet Connection' warning is one of the most universal headaches in modern computing. Because the Wi-Fi icon only measures the local radio link between your device and the router in your living room, systematically fixing this error requires isolating which layer of the network stack has broken.
Why Full Wi-Fi Signal Bars Do Not Mean You Have Internet
To fix "Wi-Fi Connected, No Internet" without randomly rebooting hardware for an hour, it helps to visualize your connection as two completely separate links:
- Link A — The Local Wireless LAN (Your Device ↔ Your Wi-Fi Router): Represented by the Wi-Fi signal bars on your screen. If this link is connected, your laptop or phone has authenticated with your router's WPA2/WPA3 radio.
- Link B — The Wide Area Network (Your Router/Modem ↔ Your ISP & the Global Internet): The fiber optic cable, coax line, or 5G gateway leaving your home.
When your device says "Connected, no internet", Link A is active, but packets are failing at one of three checkpoints: Local DHCP IP Assignment, ISP Upstream WAN Connectivity, or DNS Name Resolution.
Step 1: The 10-Second Multi-Device Check (Single Device vs. Whole House)
Before touching any settings on your computer, grab a second device (such as your smartphone) connected to the same Wi-Fi network:
- Case A — Every device on the Wi-Fi has no internet: The problem is inside your router, modem, or ISP line (skip to Steps 3 and 4).
- Case B — Other devices work fine, and only ONE laptop or phone has no internet: The problem is a local IP conflict, stuck DHCP lease, VPN kill-switch, or corrupted DNS setting on that specific device (proceed to Step 2).
Step 2: Run the 3-Command Ping Triage (Isolate Router vs. ISP vs. DNS)
Open Terminal (macOS/Linux) or Command Prompt (Windows) on the affected computer and run these three rapid tests in order:
# Test 1: Ping your local router gateway (usually 192.168.1.1 or 192.168.0.1)
ping -c 4 192.168.1.1
# Test 2: Ping a raw public IP address (Cloudflare Anycast IP — bypasses DNS entirely)
ping -c 4 1.1.1.1
# Test 3: Ping a human-readable domain name (tests DNS resolution)
ping -c 4 wrldu.com
Figure 2: The three-command ping triage (gateway IP -> public IP -> domain name) isolates in under 15 seconds whether a 'No Internet' error is caused by DHCP, your ISP fiber/cable line, or DNS.
How to Read Your 3-Ping Results:
Test 1 (Router 192.168.1.1) | Test 2 (Public IP 1.1.1.1) | Test 3 (Domain wrldu.com) | Exact Root Cause & Fix |
|---|
| FAILS (Timeout / Unreachable) | FAILS | FAILS | Local DHCP / IP Conflict (169.254.x.x) -> Renew DHCP lease (Step 3) |
| SUCCEEDS | FAILS | FAILS | Modem / ISP WAN Outage -> Power-cycle ONT/Modem & Router in sequence (Step 4) |
| SUCCEEDS | SUCCEEDS | FAILS (Unknown host) | Your Internet Works, Only DNS Is Dead! -> Switch DNS to 1.1.1.1 / 8.8.8.8 (Step 5) |
| SUCCEEDS | SUCCEEDS | SUCCEEDS | False OS Probe Warning or Captive Portal -> Check VPN Kill Switch or open http://neverssl.com (Step 6) |
Step 3: Fix Self-Assigned 169.254.x.x IP & Renew Your DHCP Lease
If your device failed to receive a valid 192.168.x.x address from the router, it assigns itself an Automatic Private IP Address (169.254.x.x), which cannot reach the internet:
On Windows 11, open an elevated Command Prompt and renew your adapter's DHCP lease:
ipconfig /release
ipconfig /renew
netsh winsock reset
- macOS: Open System Settings > Wi-Fi > Details > TCP/IP and click Renew DHCP Lease.
- iPhone / Android: Tap the info icon (
i or gear) next to the Wi-Fi network, tap Forget This Network, and reconnect—or ensure Configure IP is set to Automatic (DHCP) rather than a stale Static IP.
Step 4: Power-Cycle Your Modem/ONT and Router in the Correct Order
If Test 1 succeeded but Test 2 (ping 1.1.1.1) failed across all devices, your router's WAN interface has lost its upstream DHCP lease with your ISP's fiber Optical Network Terminal (ONT) or cable modem:
- Unplug the power cables from both your ISP Modem/ONT and your Wi-Fi Router.
- Wait a full 60 seconds (this allows capacitor charge to drain and clears the ISP's stale MAC/ARP session table).
- Plug in ONLY the Modem/ONT first and wait 2 full minutes until its
PON / Online / Internet LED turns solid green or white. - Plug in your Wi-Fi Router and wait 90 seconds for it to negotiate a fresh public WAN IP.
Step 5: Fix Dead ISP DNS Servers (ping 1.1.1.1 Works, Websites Fail)
When ping 1.1.1.1 replies in 15 ms but browsers refuse to load any website, your internet line is 100% functional—your ISP's default DNS server has simply crashed.
- Change your device or router DNS server to Cloudflare (
1.1.1.1 / 1.0.0.1) or Google (8.8.8.8 / 8.8.4.4). - Once websites load again, open WRLDU DNS Speed Test (
https://wrldu.com/dns-test) to benchmark which DNS provider is fastest in your city.
Step 6: Check VPN Kill Switches, Date/Time Drift, and Captive Portals
- VPN Kill Switch: If you use NordVPN, ExpressVPN, Mullvad, or ProtonVPN and the app crashed or your subscription expired, its Kill Switch firewall rule intentionally blocks all internet traffic. Open the VPN app and disconnect cleanly.
- Hotel / Airport Captive Portals: On public Wi-Fi, open a browser tab and visit
http://neverssl.com or http://captive.apple.com to trigger the login splash screen. - Verify Full Recovery: Once reconnected, run a 15-second baseline test at WRLDU Speed Test (
https://wrldu.com/) to confirm your download, upload, ping, and jitter are back to normal.