WiFi Connected But No Internet? 12 Fixes That Actually Work

What "WiFi Connected But No Internet" Actually Means

The WiFi icon shows full bars, your device says "Connected" — and nothing loads. This happens because WiFi and internet are two separate connections: WiFi is the radio link between your device and the router; internet is the router's link to your ISP and beyond. "Connected, no internet" means the first link works and the second one — or the DNS layer that translates names to addresses — is broken.

Operating systems detect this by silently pinging a known test URL after connecting (Microsoft, Apple, and Google each run their own connectivity check). When the check fails, Windows shows "No internet, secured", Android shows "Connected, no internet", and iPhone shows "No Internet Connection" under the network name.

The failure is nearly always in one of three places: your device's network configuration (wrong IP, stale DNS), the router (glitched DHCP, dropped ISP session), or the ISP itself (outage, authentication issue). The 12 fixes below walk through them from fastest to most thorough.

First: Is It One Device or the Whole Network?

Thirty seconds of triage saves an hour of random fixes. Check the internet on a second device connected to the same WiFi — another phone, laptop, or TV.

You can also confirm whether name resolution is the broken layer: if you can't open any website, try visiting 1.1.1.1 directly in the browser. If that loads but normal sites don't, your connection is fine and DNS is the problem — Fix 3 will solve it.

Common Causes, Ranked

Roughly in order of how often they're the culprit:

• Router lost its ISP session — the WiFi radio keeps working while the WAN link is down. A restart renegotiates it.

• Stale or conflicting IP lease — your device holds an address the router no longer honors, or two devices collided.

• Broken DNS — the router's DNS forwarder glitched or the ISP's resolver is down; everything "connects" but nothing resolves.

• ISP outage — area-wide maintenance or failures; nothing on your side is wrong.

• Captive portal not completed — hotel/café/airport networks block everything until you accept their login page.

• VPN, proxy, or firewall interference — a dead VPN tunnel or leftover proxy setting silently blackholes traffic.

• Outdated or corrupted network drivers (Windows) — connects to WiFi but fails the internet check.

• Router misconfiguration — broken DHCP range, MAC filtering, or an ISP-pushed firmware update gone wrong.

Fix 1: Restart the Router and Modem (Properly)

It's the cliché for a reason: a power cycle forces the router to rebuild its connection table, renew its own lease from the ISP, and restart its DNS forwarder — clearing the three most common failure points in one move.

Unplug the router and the modem (if separate) from power. Wait a full 30 seconds — this lets the ISP side drop the old session. Plug the modem in first, wait until its status lights stabilize (1–2 minutes), then plug in the router and give it 2–3 minutes. Reconnect and test.

If internet returns but drops again within hours or days, don't keep rebooting forever — that's a symptom of an overheating router, failing power adapter, or an ISP line problem worth reporting.

Fix 2: Release and Renew Your IP Address

Your device leases an IP address from the router via DHCP. When that lease goes stale or conflicts with another device, you stay connected to WiFi with no working route. Renewing forces a fresh lease — and fresh DNS server assignments with it.

# Windows (Command Prompt as Administrator)
ipconfig /release
ipconfig /renew
ipconfig /flushdns

# macOS — renew DHCP lease
# System Settings → Network → Wi-Fi → Details → TCP/IP → Renew DHCP Lease
# or from Terminal:
sudo ipconfig set en0 DHCP

# Android: Settings → WiFi → your network → Forget, then reconnect
# iPhone: Settings → Wi-Fi → (i) → Renew Lease

After renewing, check what you got: an address starting with 169.254.x.x means DHCP failed completely (the device gave itself a dead-end address) — that points at the router's DHCP server, so restart the router (Fix 1) or check its DHCP settings (Fix 10).

Fix 3: Flush DNS and Switch to a Public DNS Server

This is the #1 fix when WiFi shows connected and sites won't load — especially if 1.1.1.1 opens in your browser but named sites don't. Your cached lookups may be stale, or the DNS server your router assigned (usually the ISP's) may be down entirely.

First flush the cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS. Then switch your DNS to a public resolver:

Windows: Settings → Network & Internet → Wi-Fi → your network → Edit DNS server assignment → Manual → IPv4 → 1.1.1.1 / 1.0.0.1. macOS: System Settings → Network → Wi-Fi → Details → DNS. Android: Settings → Network & Internet → Private DNS → one.one.one.one. iPhone: Settings → Wi-Fi → (i) → Configure DNS → Manual.

Not sure which resolver is fastest from your connection? Benchmark them in 30 seconds with the DNS Speed Test. And if only one specific site won't load, check whether its DNS is actually resolving worldwide with a global DNS lookup — the problem may be the site's, not yours.

Fix 4: Forget the Network and Reconnect

Your device stores the network's configuration — security type, band preferences, IP settings — and that stored profile can go stale after a router update or settings change. Forgetting the network deletes the profile and negotiates everything fresh.

Windows: Settings → Network & Internet → Wi-Fi → Manage known networks → your network → Forget. macOS: System Settings → Wi-Fi → Details → Forget This Network. Android/iPhone: tap the network → Forget. Then reconnect with the password and test.

Fix 5: Check for an ISP Outage

If no device in the house has internet and a router restart didn't help, there's a good chance nothing on your side is broken. Check your ISP's status page or app using mobile data, or look the provider up on Downdetector.

Also glance at the modem's indicator lights: a blinking or red "Internet"/"Online" light means the ISP link itself is down — no amount of device-side fixing will help. Report it and wait it out. If outages happen weekly, that history is worth citing when you call to complain (or negotiate).

Fix 6: Trigger the Captive Portal (Hotels, Cafés, Airports)

Public networks hold every connection hostage until you accept terms on their login page — and if that page never popped up, you're "connected" with zero internet. Force it to appear:

• Open http://neverssl.com in your browser — a plain HTTP site that portals can intercept (HTTPS sites often can't be redirected)

• Or visit the router's gateway IP directly — commonly 192.168.1.1 or whatever "Router" shows in your WiFi details

• Disable Private/Random MAC for this network if the portal loops — portals track your MAC address, and randomization breaks their session

• Complete the login/accept page, then test again

Fix 7: Disable VPN, Proxy, and Firewall Interference

A VPN whose tunnel died takes all your traffic down with it — the WiFi stays connected while every request disappears into a dead tunnel. Disconnect the VPN entirely and test.

Next, proxies: Windows Settings → Network & Internet → Proxy → turn off "Use a proxy server"; macOS System Settings → Network → Wi-Fi → Details → Proxies → uncheck all. A leftover proxy from an old app or network is a classic silent killer.

Finally, briefly disable third-party antivirus/firewall web protection and test — some suites intercept all traffic through a local filter that can wedge itself. Re-enable it right after testing either way.

Fix 8: Update or Reinstall Network Drivers (Windows)

If your laptop shows "No internet, secured" while phones work fine on the same WiFi, the Windows WiFi adapter driver is the prime suspect — especially after a Windows update.

Open Device Manager → Network adapters → right-click your WiFi adapter → Update driver → Search automatically. If that finds nothing, try Uninstall device (keep the driver software), then restart — Windows reinstalls the adapter cleanly on boot. For persistent cases, download the latest driver from the laptop manufacturer's site using another device.

Fix 9: Check Router Settings (DHCP, MAC Filtering, Firmware)

Log into the router's admin page (the "gateway" IP from your WiFi details — commonly 192.168.1.1 or 192.168.0.1) and check three things:

DHCP is enabled and its address pool isn't exhausted — a full pool means new devices connect to WiFi but never get a working IP. MAC filtering isn't silently blocking the affected device — some routers ship with an allowlist a family member once configured. Firmware is current — ISP-pushed updates occasionally reset WAN settings; reapplying your ISP's connection credentials (PPPoE username/password, if used) fixes it.

While you're in there: if the router's DNS is set to the ISP's servers, changing it to 1.1.1.1 / 8.8.8.8 applies fast DNS to every device on the network at once.

Fix 10: Full Network Reset (Last Resort on the Device)

When one specific device still refuses to work, reset its entire network stack — this wipes saved networks, adapters, and misconfigured settings back to defaults:

• Windows: Settings → Network & Internet → Advanced network settings → Network reset (restarts the PC)

• macOS: remove Wi-Fi from Network settings and re-add it; for deep issues delete /Library/Preferences/SystemConfiguration/ network plists and reboot

• Android: Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth

• iPhone: Settings → General → Transfer or Reset → Reset → Reset Network Settings

You'll need to re-enter WiFi passwords afterwards — but this clears virtually every device-side misconfiguration in one shot.

Still Broken? How to Prove It's Your ISP

If every fix above failed and every device is offline, build a 2-minute case before calling support — it shortens the call dramatically:

Confirm the modem's WAN/Online light is red or blinking. Note whether the outage tracker shows your area. If you have partial connectivity, run a ping test to 8.8.8.8 (tests raw connectivity, bypassing DNS) and a DNS lookup for any domain — telling support "ping to 8.8.8.8 works but DNS fails" or "100% packet loss at the first hop" gets you past the script and escalated faster.

And once you're back online, check what your connection actually reports — after outages, ISPs occasionally route you through congested backup paths with much slower DNS.