WiFi Connected But No Internet: Fix It Now

Cause 1: Corrupted DNS Cache (Most Common)

This is the fix I've used hundreds of times and it works about 60% of the time. Your computer has a local cache of DNS lookups—mapping website names to IP addresses. When that cache gets corrupted, the computer thinks it can't reach any website even though the WiFi signal is strong.

What you'll see: You're connected to your home network with full bars, but browsers show "DNS_PROBE_FINISHED_NXDOMAIN" or just "No Internet." This usually happens after a power outage, a VPN session disconnect, or switching between different WiFi networks.

1. Press Windows key + R on your keyboard. This opens the Run dialog box.
2. Type cmd and press Ctrl + Shift + Enter. This opens Command Prompt as an administrator. You'll see a User Account Control prompt—click Yes.
3. In the black Command Prompt window, type exactly (or copy-paste): ipconfig /flushdns and press Enter.
4. After you press Enter: You should see a message: "Successfully flushed the DNS Resolver Cache." If you don't see that, you likely didn't run as administrator. Close and repeat step 2.
5. Type ipconfig /registerdns and press Enter. This re-registers your computer with the network. You'll see "Registration of the DNS records has been initiated."
6. Close Command Prompt. Restart your browser and try loading a website. Most times, it works immediately.

If this didn't fix it, don't worry—the next cause covers another 20% of cases.

Cause 2: Stale IP Address (Needs Release and Renew)

Your computer gets an IP address from your router using DHCP. Sometimes that lease expires or conflicts with another device. You're still "connected" to the WiFi, but with a broken IP, your computer can't talk to the router properly.

When this happens: After bringing a laptop back from standby or sleep mode, after connecting to a public hotspot then coming home, or when two devices accidentally get the same IP (more common than you'd think on older routers).

1. Open Command Prompt as administrator again (same way: Windows + R, type cmd, then Ctrl + Shift + Enter).
2. Type ipconfig /release and press Enter. Your screen will show all network adapters losing their IP addresses—they'll say "Media disconnected" or show 0.0.0.0. Your internet will cut off completely. That's expected.
3. Wait 10 seconds. This pause is important. The router needs a moment to clear the old lease.
4. Type ipconfig /renew and press Enter. This sends a request to your router for a new IP. It can take up to 20 seconds. You'll see a new IP address appear (something like 192.168.x.x or 10.0.x.x).
5. Type ipconfig /flushdns again (it doesn't hurt to do it again).
6. Close Command Prompt. Try browsing again.

If the renew step hangs: You waited 30 seconds and nothing happened? That means your router isn't responding. Skip to Cause 3.

Cause 3: Router Needs a Full Power Cycle (Hard Reset)

I saved this one for third because it's the nuclear option—but it fixes the remaining cases when DNS and IP tricks fail. Routers run a lightweight Linux-based system. After weeks or months of uptime, they accumulate memory leaks, dropped connections, and corrupted routing tables. A simple reboot often doesn't clear these—you need a full power cycle.

Real scenario: You've got a TP-Link Archer AX50 or a Netgear Nighthawk that hasn't been restarted since you set it up 6 months ago. It's been working fine, but today you can't reach any website. Other devices (like your phone) also have problems.

1. Don't just hit the reset button on the router. That factory resets it and you'll lose all settings. Instead, unplug the power cable from the back of the router.
2. Unplug your modem too (if you have a separate modem).
3. Wait a full 60 seconds. I know it feels like forever, but capacitors inside can hold charge for 30 seconds. A full minute ensures everything is discharged.
4. Plug the modem back in first (if separate). Wait until all the lights settle—usually 1-2 minutes. The "Online" or "Internet" light should be solid.
5. Plug the router back in. Wait for it to fully boot—the WiFi lights should stop blinking and stay solid. This takes 2-3 minutes on most routers.
6. On your computer, reconnect to your WiFi network (you may need to re-enter the password if the router's DHCP lease cleared).
7. Test browsing again.

Important: If this doesn't work, you might have a bigger problem—ISP outage or bad hardware. But 95% of the time, one of these three steps solves the "WiFi connected but no internet" issue. I've seen it work on Windows 10, Windows 11, and even some Macs.

Quick-Reference Summary Table