WiFi Connected But No Internet: How to Fix It Fast

What "connected but no internet" actually means

It is one of the most confusing status messages in computing: the WiFi icon shows full bars, your laptop says it is connected, yet nothing loads. The key thing to understand is that joining a WiFi network and reaching the internet are two separate steps.

When you connect to WiFi, your device establishes a local link to the router. That part can succeed perfectly. But to actually browse, three more things have to work: your device needs a valid IP address from the router (via DHCP), it needs to resolve domain names into addresses through DNS, and the router itself needs a working route out to the internet from your ISP.

So "connected, no internet" is the system politely telling you: the first step worked, but one of the next three failed. The good news is that this narrows the problem dramatically. Instead of randomly rebooting things, you can test each layer in order and find the broken link in a few minutes.

30-second triage: is it one device or all of them?

Before changing a single setting, answer one question, because it splits the entire problem in half.

Pick up your phone and turn off its mobile data so it relies only on WiFi. Then try loading a normal website on it.

• Other devices also have no internet on the same WiFi → the problem is the router or your ISP, not your laptop. Skip ahead to the router/ISP section.
• Other devices work fine, only your laptop fails → the problem is on that one device — its DNS, IP, network adapter, VPN, or clock. Work through the quick wins and DNS/IP fixes.

This single test saves you from spending twenty minutes resetting your laptop's network stack when the real issue is a router that needs a reboot, or an ISP outage you can do nothing about. Always start here.

Fast wins that fix most cases

If it is just your device, these five moves clear the large majority of "connected but no internet" cases. Try them in order and test after each one.

1. Toggle WiFi or airplane mode. Turn airplane mode on for ten seconds, then off. This forces a clean reconnection and a fresh IP request — the single fastest fix.
2. Reboot the router. Unplug it from power, wait 30 seconds, plug it back in, and give it two full minutes to come back. Most home-router glitches die here.
3. Forget and rejoin the network. On Windows: Settings → Network & internet → WiFi → Manage known networks, forget the network, then rejoin with the password. On macOS: System Settings → Wi-Fi → Details → Forget This Network, then reconnect.
4. Check for a captive portal. On hotel, café, or airport WiFi you often connect fine but never see the login page, so nothing loads. Open a browser to a plain http:// site (not https) to trigger it. Our companion guide on hotel and café WiFi that won't connect covers this in depth.
5. Disconnect your VPN or proxy. A half-connected VPN, or one whose DNS broke, is a classic cause. Fully quit it and test. If the VPN itself is the problem, see why your VPN won't work abroad.

DNS and IP/DHCP fixes (the real culprits)

If quick wins did not do it, the issue is almost always DNS or your IP address. These are the two layers that most often break while WiFi stays "connected."

Fix DNS: switch to 1.1.1.1 / 8.8.8.8 and flush the cache

DNS translates names like example.com into numeric addresses. If your ISP's DNS server is flaky, sites won't load even though you are online. Pointing your device at Cloudflare (1.1.1.1) or Google (8.8.8.8) fixes this instantly in many cases.

Windows 11/10: Settings → Network & internet → WiFi → Hardware properties → DNS server assignment → Edit → Manual, turn on IPv4, set Preferred to 1.1.1.1 and Alternate to 8.8.8.8. Then open Command Prompt and run ipconfig /flushdns.

macOS: System Settings → Wi-Fi → Details → DNS, click +, add 1.1.1.1 and 8.8.8.8, click OK. To flush the cache, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.

Fix the IP: renew DHCP and watch for 169.254 addresses

If your device shows an address starting with 169.254.x.x, that is an APIPA address — it means the router never handed out a real IP, so you are connected to WiFi but have no usable network. Renewing the lease usually fixes it.

Windows: in Command Prompt, run ipconfig /release then ipconfig /renew. macOS: System Settings → Wi-Fi → Details → TCP/IP → Renew DHCP Lease.

The "No Internet, Secured" message on Windows

Windows users often see the exact phrase "No Internet, Secured" under the WiFi name. The "Secured" part just means the connection is encrypted (good); the "No Internet" part means Windows tested for internet access and failed. It is the same underlying problem — DNS, IP, or upstream — but Windows has a few extra levers worth pulling.

Reset the network stack

A corrupted Winsock or TCP/IP stack causes persistent "No Internet, Secured." Open Command Prompt as administrator and run these in order, then reboot:

• netsh winsock reset
• netsh int ip reset
• ipconfig /flushdns

Other Windows-specific checks

• Reset the WiFi adapter: Settings → Network & internet → Advanced network settings, disable the WiFi adapter, wait, re-enable it. Or use Network reset as a last resort (it forgets all networks).
• Update or roll back the WiFi driver: in Device Manager, under Network adapters, update the driver — or if the problem started right after an update, roll it back.
• Check date and time: a wrong clock breaks the TLS certificate checks behind HTTPS, so secure sites fail to load. Set time to update automatically with the correct time zone — a common gotcha after traveling across time zones.
• MTU mismatch: rare, but on some hotel or captive networks an oversized MTU drops packets. If pages half-load, lowering the adapter MTU (e.g. to 1400) can help; this is an advanced step we usually handle on a remote call.

When it's the router or the ISP, not your laptop

If your triage test showed that every device is offline, stop touching your laptop — the problem is upstream and no amount of DNS editing will help.

• Reboot the router and modem together. Power both off, wait a full minute, power the modem on first and let it fully sync, then the router. This re-establishes the link to your ISP.
• Check the modem lights. A blinking or red "internet"/"online" light usually means the ISP signal is down, not your equipment.
• Confirm an ISP outage. Use your phone on mobile data to check your provider's status page or outage map. If it is a regional outage, the only fix is to wait — or switch to a phone hotspot to keep working.
• Hotspot as a bridge. If you must stay online, tether your laptop to your phone's hotspot. This is also exactly how we get a remote session going to fix the underlying machine even when its main connection is dead.

If rebooting the router does not restore other devices and there is no outage reported, the router hardware or its ISP configuration may be the issue — that is when a guided remote look-through saves a frustrating call with the provider.

Symptom → cause → fix table

Use this to jump straight to the likely cause based on exactly what you see.

Symptom	Likely cause	Fix
Only one device offline, others fine	Device-side DNS, IP, or adapter	Renew IP, set DNS 1.1.1.1/8.8.8.8, flush DNS
All devices offline	Router or ISP outage	Reboot modem + router; check ISP status
IP starts with 169.254.x.x	No DHCP lease (APIPA)	ipconfig /release then /renew; reboot router
"No Internet, Secured" (Windows)	Corrupt network stack / DNS	netsh winsock reset, netsh int ip reset, reboot
Connects but login page never appears	Captive portal (hotel/café)	Open an http:// site to trigger the portal
Online but HTTPS sites fail, others vary	Wrong date/time or broken DNS	Fix clock auto-sync; switch DNS servers
Works without VPN, fails with it	VPN/proxy broke DNS or routing	Quit VPN; reconnect or switch VPN protocol
Pages half-load or stall on some networks	MTU mismatch	Lower adapter MTU (e.g. 1400)

Still stuck after working down the list? Some cases — driver corruption, MTU, layered VPN and DNS conflicts, or a router you can't physically reach — are faster to fix live. We do this every day for remote workers and travelers in 130+ cities, and we'll tell you in the first few minutes whether it's your machine or the network.