- Wi-Fi connected but no internet means your device reached the router but cannot get past it to the web.
- Isolate it first. Check whether other devices work, and whether a wired Ethernet connection works.
- If only one device fails, fix that device: forget the network, renew the IP, update the Wi-Fi driver.
- If every device fails, power-cycle the modem and router. Wait 30 seconds before powering them back on.
- Load your router page at
192.168.1.1. If it opens but the web does not, the fault is upstream. - If pages load by IP but not by name, the problem is DNS. Switch to
8.8.8.8or1.1.1.1.
Your laptop shows full Wi-Fi bars, yet nothing loads. The status reads Wi-Fi connected but no internet, and every page times out. It is one of the most common home network faults, and most of it you can fix yourself.
The message sounds contradictory, but it is precise. Your device reached the router. It just cannot get past the router to the wider internet. That gap is where the real problem lives.
This guide works from the inside out. First you isolate where the fault sits, in under a minute. Then you fix it at the right layer: the device, the router, your DNS, or the line itself.
What “connected but no internet” actually means
Wi-Fi connected but no internet means your device joined the local network but cannot reach the wider web through it. The radio link to your router works. The path past the router is broken. The fault is in the device, the router, your DNS, or your provider.
Joining Wi-Fi and reaching the internet are two separate steps. Your device first associates with the router’s radio. That is the “connected” part, and it can succeed on its own.
The second step is getting a working route out to the internet. That needs a valid IP address, a working gateway, and DNS to translate names into addresses. When any of those fails, you stay connected with no internet.
So the signal bars are not the issue. They only show the radio link is healthy. The break is one layer up, between your router and the rest of the world.
Is it one device or the whole network?
Before changing settings, find where the fault lives. Two quick checks do it: see whether other devices on the same Wi-Fi work, then test a wired Ethernet connection. The results point you straight at the device, the router, or your internet provider.
This step is the one most people skip, and it is the one that saves the most time. A minute of testing tells you which fix list to use.
The 60-second isolation test
Try a second device on the same Wi-Fi. If your phone works but your laptop does not, the fault is on that one machine. Skip to the device fixes.
Plug in an Ethernet cable if you can. If wired works but Wi-Fi does not, the issue is the router’s wireless side, not the line.
Check every device. If nothing can reach the internet on this network, the cause is shared. That points at the router or your provider.
| What you see | Likely cause | Where to go next |
|---|---|---|
| Other devices work, one does not | That device’s network settings | Fix one offline device |
| No device works on Wi-Fi | Router or internet provider | Fix the whole network |
| Ethernet works, Wi-Fi does not | Router’s wireless radio or band | The router admin check |
| Pages load by IP but not by name | DNS | When it is DNS, not the connection |
Fix one offline device
If only one device fails, repair it instead of the router. Forget and rejoin the network, renew its IP address, restart the Wi-Fi service, and update the driver. These steps clear the stale settings that strand a single machine while everything else stays online.
Forget the network and rejoin
A corrupted saved profile is a frequent cause. On Windows, open Settings → Network & internet → Wi-Fi → Manage known networks. Forget the network, then reconnect and re-enter the password.
Renew the IP address
An address that starts with 169.254 means the device never got a valid IP from the router. That is an APIPA address, and it blocks all internet access. Renew the lease with these commands in an admin Command Prompt.
ipconfig /flushdns
ipconfig /release
ipconfig /renewYou can confirm the result with our My IP Address tool. A normal home address looks like 192.168.x.x, which our guide on public versus private IP addresses explains in full.
Restart the Wi-Fi service and driver
The WLAN AutoConfig service manages wireless connections. Press Win + R, type services.msc, find WLAN AutoConfig, and restart it. If the trouble began after an update, roll the Wi-Fi driver back in Device Manager.
Fix the whole network
If no device can reach the internet, the cause is shared, so fix the network, not one machine. Power-cycle the modem and router, watch the internet light, and test with a wired cable. Most whole-network outages clear with a clean restart of both boxes.
Power-cycle the modem and router
This is the single most effective fix for a whole-network outage. Unplug both the modem and the router from power. Wait 30 seconds, then plug the modem in first and let it fully boot before powering the router.
Read the internet light
Your modem has a light labeled internet, online, or WAN. A solid light means the link to your provider is up. A blinking or red light means the fault is the connection itself, not your devices.
Test with an Ethernet cable
Connect a computer straight to the router with a cable. If the wired connection reaches the internet, the problem is the router’s Wi-Fi side. If wired also fails, the fault is the router or the line.
The router admin check
Your router’s admin page is the cleanest way to split a router problem from a provider problem. If the page loads but the internet does not, the router is healthy and the break is upstream. If the page will not load, the router itself needs attention.
Open a browser and enter your router’s address. The most common ones are below. The exact address is usually printed on a sticker on the router.
192.168.1.1192.168.0.1192.168.1.254
If the admin page loads, your device-to-router link is fine. Look at the router’s status or WAN page. A missing WAN IP there confirms the fault sits between the router and your provider.
If the page will not open at all, your device cannot reach the router properly. Re-run the device fixes above, or reboot the router and try again.
When it is DNS, not the connection
Sometimes the connection is fine and DNS is the real culprit. The clue is that pages load by IP address but not by name. Switching to a public DNS server like Google or Cloudflare often fixes it. You can then confirm name resolution with a lookup tool.
DNS turns names like example.com into IP addresses. Our guide on how DNS works covers that process. When DNS fails, the connection looks alive but no site opens.
Set your DNS to a reliable public resolver. Google uses 8.8.8.8 and 8.8.4.4. Cloudflare uses 1.1.1.1 and 1.0.0.1. Set it on the router to cover every device at once.
Confirm the fix with our DNS lookup tool, which shows whether a domain now resolves to an IP. If your browser shows a DNS-specific error, our guide to DNS_PROBE_FINISHED_NO_INTERNET walks the exact fixes.
Other common causes: VPN, proxy, and drivers
A few quieter culprits cause this error even when the basics check out. A dropped VPN, a leftover proxy, an aggressive firewall, or an outdated driver can each cause this. Wi-Fi still shows connected while they block your access. Rule them out one at a time.
- VPN: A dropped VPN tunnel can block all traffic. Disconnect it fully and reload the page.
- Proxy: Malware sometimes sets a proxy. On Windows, open Settings → Network & internet → Proxy and turn off any manual proxy.
- Firewall or antivirus: A third-party suite can block the connection. Test by disabling it briefly, then re-enable it.
- Network driver: An outdated or buggy Wi-Fi driver causes drops. Update it through Device Manager, or roll it back if trouble started after an update.
If none of these help and every device still fails, the cause is almost certainly your provider. Our network connectivity troubleshooting guide covers confirming an outage past your modem.
Related Tools & Resources
NetworkCheckr hosts the free tools these checks rely on, so you can confirm a fix instead of guessing. Use the tools below to verify your IP and DNS. The guides explain the layers behind a connected-but-offline Wi-Fi connection.
Frequently Asked Questions
Short answers to the questions people ask most about a Wi-Fi connection that shows connected but has no internet. Each one expands on a point from the fixes above. Together they cover what the status means and where the fault sits.
What does Wi-Fi connected but no internet mean?
It means your device joined the Wi-Fi network but cannot reach the wider internet through it. The link to your router is fine, but the path past the router is broken. The fault sits in the device’s settings, the router, your DNS, or your provider. It is not the Wi-Fi signal itself.
Why does my Wi-Fi say connected but no internet on Windows 11?
On Windows 11 the common causes are a stale IP lease or a corrupted network stack. A bad Wi-Fi driver or a leftover proxy or VPN setting can also do it. Start by forgetting and rejoining the network. Then run ipconfig /flushdns, ipconfig /release, and ipconfig /renew. If it persists, use Network reset under Advanced network settings.
Why does only one device have no internet?
If every other device works on the same Wi-Fi, the fault is on that one machine, not the network. The likely causes are a stale IP address or an APIPA address starting with 169.254. A proxy or VPN setting, or an outdated network driver, can also strand it. Fix the device rather than the router.
Does Wi-Fi connected but no internet mean my router is broken?
Not always. If no device can reach the internet, the cause is usually the router or your provider. A power cycle fixes most of these cases. Unplug the modem and router, wait 30 seconds, and power them back on. If the router admin page loads but the internet does not, the problem is past the router.
Why does mobile data work but Wi-Fi does not?
Mobile data uses a different connection than your home Wi-Fi, so it working only proves your phone is fine. It points the fault at your router or your internet provider, not the device. Power-cycle the router and check whether the internet light is solid. If it stays off, contact your provider.
Will a network reset fix Wi-Fi connected but no internet?
Often, yes, when the fault is on one Windows device. Network reset removes and reinstalls your network adapters and clears corrupted settings. It also forgets saved Wi-Fi networks, so you will re-enter passwords afterward. Try the lighter fixes first, then use Network reset as the last device-level step before blaming the router.
References
Primary sources for the commands, services, and settings described above. These cover the Windows network tools, the public DNS services, and the link-local address standard that explains an APIPA address. Each link points to official documentation.
- Microsoft Learn — ipconfig Command Reference
- Microsoft Support — Fix Wi-Fi Connection Issues in Windows
- Google Public DNS — Get Started With Google Public DNS
- Cloudflare — 1.1.1.1 Public DNS Resolver Docs
- IETF — RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses