WiFi Connected But No Internet: Real Fixes That Work
Your WiFi says connected but you can't browse? Here's why it happens and how to fix it in minutes. Real steps, no fluff.
You see the WiFi icon showing full bars. Your phone or laptop says "Connected." But when you open a browser, nothing loads. Or you get that dreaded "No Internet Access" message under the network name. I've seen this hundreds of times. Here's what's actually going on and how to fix it.
I'm going to walk through the three most common causes in order of likelihood. Each has a clear fix you can try right now. No jargon. Just steps that work.
1. IP Address or DNS Conflict (Most Common)
Your device grabs an IP address and DNS server info from your router via DHCP. But sometimes that info gets stale or corrupt. Your device thinks it's on the network, but it can't actually talk to anything outside your local router. This happens after a power outage, a router reboot, or when you move between two WiFi networks.
Real-world trigger: You just came home from the coffee shop, your laptop still has the old DNS settings cached from the cafe's public WiFi.
Fix: Release, Renew, Flush DNS
Open Command Prompt as administrator:
- Press Windows Key + X, then choose Command Prompt (Admin) or Windows PowerShell (Admin).
- Type these commands one at a time, pressing Enter after each:
ipconfig /release ipconfig /renew ipconfig /flushdns - Wait for each command to finish.
ipconfig /renewcan take 10–15 seconds. You should see your IP address update. If it hangs, try again after a minute. - Close the window and test your internet.
After ipconfig /renew, check that the IP address starts with 192.168. or 10. or 172.16–31.. If you see 169.254.x.x, that means your device couldn't get an IP from the router at all—skip to cause #2.
If the flush worked, you'll see a message: "Successfully flushed the DNS Resolver Cache." If you see an error like "The requested operation requires elevation," you didn't run Command Prompt as admin. Go back and do that.
Still no internet? Try setting Google's public DNS manually:
- Open Network & Internet Settings (right-click the network icon in the taskbar).
- Click Change adapter options.
- Right-click your WiFi adapter, choose Properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Choose Use the following DNS server addresses and put in:
Preferred DNS: 8.8.8.8 Alternate DNS: 8.8.4.4 - Click OK twice. Now test your browser.
If this fixes it, your ISP's DNS was the culprit. You can keep Google's or switch later—it's stable and fast.
2. Router or Modem Glitch (Second Most Common)
Your router is a small computer running firmware. Sometimes it gets confused. A full power cycle—not just a reboot via the web interface—clears its ARP cache, renews the WAN lease, and fixes most connection issues.
Real-world trigger: You had a brief power flicker last night. The router came back up, but the modem didn't fully renegotiate with your ISP.
Fix: Full Power Cycle
- Unplug the power cord from both your modem and your router (if they're separate boxes).
- Wait a full 60 seconds. I count to 60 out loud.
- Plug the modem back in first. Wait until all the lights stabilize—usually 2–3 minutes. The "online" or "internet" light should be solid green or white, not blinking.
- Plug the router back in. Wait another 2 minutes for it to boot and reconnect to the modem.
- On your device, forget the WiFi network and reconnect, or just reconnect if prompted.
After this, check if you can load a simple page like google.com. If you still can't, try connecting a device directly to the modem via Ethernet cable. If Ethernet works, the problem is your router. If Ethernet also fails, it's your ISP or modem. Call your ISP.
3. IPv6 vs IPv4 Conflict (Less Common, But Tricky)
Some newer routers and ISPs push IPv6 alongside IPv4. Older devices or misconfigured networks can get confused. Your device tries to use IPv6, but the DNS or gateway only responds to IPv4. Result: connected but no internet.
Real-world trigger: You just updated your router's firmware and the update enabled IPv6 by default.
Fix: Disable IPv6 Temporarily
- Open Network & Internet Settings > Change adapter options.
- Right-click your WiFi adapter, choose Properties.
- Find Internet Protocol Version 6 (TCP/IPv6) in the list.
- Uncheck the box next to it.
- Click OK.
- Restart your browser and test.
If this fixes it, you've got an IPv6 issue. You can leave IPv6 disabled—most home networks don't need it. If you want IPv6 back later, re-enable it and update your router's firmware instead.
Note: Some cable ISPs (like Xfinity or Spectrum) force IPv6 on in their newer modems. If disabling IPv6 doesn't help, log into your router and check the WAN settings. Sometimes you need to change the connection type from "IPv6" to "IPv4 only" or "Auto detect."
Quick-Reference Summary Table
| Symptom | Likely Cause | Fix |
|---|---|---|
| WiFi connected, no pages load, other devices work fine | Corrupt DNS cache or stale IP lease on your device | ipconfig /release, /renew, /flushdns in admin Command Prompt |
| No internet on any device after power outage | Modem/router glitch in WAN negotiation | Full 60-second power cycle of modem and router |
| Some sites load, some don't, or intermittent drops | IPv6/IPv4 conflict after router firmware update | Disable IPv6 in adapter properties |
| All fixes tried, still no internet | ISP outage, bad Ethernet cable, or hardware failure | Test with Ethernet directly to modem; call ISP |
That's it. The first two fixes solve about 90% of "WiFi connected but no internet" cases I've seen over the years. The third covers most of the rest. You don't need to buy anything or call support—just work through these in order.
Was this solution helpful?