Wi-Fi Connected But No Internet: The Complete Diagnostic Path
Now read the results against this table — your first failure is your diagnosis:
| Result | Diagnosis | Go to |
|---|---|---|
ipconfig shows an address starting 169.254.x.x | DHCP failed — router never gave you an address | Section 03 |
| Can't ping the gateway | Local link problem (adapter, driver, signal) | Section 04 |
| Gateway pings, 8.8.8.8 doesn't | Router-to-ISP problem — not your PC at all | Section 05 |
| 8.8.8.8 pings, nslookup fails | DNS problem — the classic "connected, no internet" | Section 06 |
| Everything passes but browsing fails | Captive portal, proxy, or firewall software | Section 07 |
03 — Fixing DHCP Failures (169.254.x.x)
An address beginning 169.254 means Windows asked the router for an IP and got silence, so it invented a useless placeholder. Ask again:
ipconfig /release
ipconfig /renewIf you still get 169.254: reboot the router (its DHCP service can wedge while Wi-Fi keeps beaconing — this is the case where "turn it off and on" is genuinely the correct engineering answer). Still failing after that? Check whether the router's DHCP pool is exhausted (lots of devices, small pool — visible in the router admin page) or whether a static IP was set on the adapter long ago and forgotten: Settings → Network & internet → Wi-Fi → your network → IP assignment should say Automatic (DHCP).
04 — Fixing Local Link Problems
Can't reach the gateway at all? In rough order of likelihood:
- Signal/interference: does it work next to the router? If yes, it's coverage, not configuration.
- Power management: the quiet classic. Device Manager → your Wi-Fi adapter → Properties → Power Management → untick "Allow the computer to turn off this device to save power." This single checkbox explains a remarkable share of "Wi-Fi drops after sleep" complaints.
- Driver: Device Manager → adapter → Update driver; better, fetch the current driver from the laptop/adapter maker rather than relying on Windows' generic one. If trouble started right after a driver update, Roll Back instead.
- Forget and rejoin the network — clears a corrupted saved profile and stale credentials.
- Full stack reset, the last local resort (re-pairs everything, removes VPN adapters):
netsh winsock reset
netsh int ip reset
# Then reboot. Or use Settings → Network & internet → Advanced → Network reset.05 — When the Router Can't Reach the Internet
Gateway responds, 8.8.8.8 doesn't: every device in the house is affected (verify with your phone on Wi-Fi — quickest confirmation there is). Your PC is innocent. Now:
- Check the router's WAN/Internet status light and admin page — does it show an IP from the ISP, or "disconnected"?
- Power-cycle the modem first, then the router, waiting for the modem's sync light before powering the router.
- Check your ISP's outage page or app — from your phone on mobile data.
- If the router gets no WAN address even after a power cycle, it's an ISP or line issue. That's a support call, and "your modem has no sync" gets you past the first tier of script-reading much faster.
06 — When It's DNS (It's Often DNS)
Raw addresses ping but names don't resolve — the textbook "connected but no internet," because browsers live on names. Quick fixes:
# Flush the local cache
ipconfig /flushdns
# Test against a known-good public server directly
nslookup google.com 1.1.1.1If the direct test against 1.1.1.1 works while plain nslookup fails, your configured DNS server (usually the router or ISP resolver) is the broken piece. Point the adapter at a public resolver — Settings → Network & internet → Wi-Fi → Hardware properties → DNS server assignment → Edit → Manual → IPv4 → 1.1.1.1 and 1.0.0.1 (Cloudflare) or 9.9.9.9 (Quad9). DNS deserves its own article — failure modes, choosing resolvers, DNS-over-HTTPS — and it's next on my list.
07 — Everything Passes But Browsing Still Fails
- Captive portal (hotels, cafés, airports): you must open a login page first. If it doesn't appear, browse to
http://neverssl.com— a deliberately unencrypted site that lets the portal hijack you to its login. - Leftover proxy or VPN: Settings → Network & internet → Proxy → everything off unless you set it deliberately; check the system tray for half-dead VPN clients.
- Third-party firewall/security suite mid-update or misconfigured — temporarily disable to test, and if that's the answer, reinstall or remove it.
- Date and time wrong on the PC breaks HTTPS certificate validation everywhere — looks exactly like "no internet" but with certificate warnings.
[Personal note placeholder: add a short real example — e.g., a case where the power-management checkbox or a dead ISP line turned out to be the cause.]
🔒 Bottom line: three pings and an nslookup turn "the internet is broken" into a named, located fault in under a minute. Test the chain in order, stop at the first break, fix that link only — and save the reboot ritual for the one case (a wedged router) where it's actually the textbook answer.