WiFi Connected But No Internet? Here's the Real Fix

The 30-Second Fix: Turn Off Your Phone’s WiFi

Sounds stupid, right? But hear me out. Half the time when a client calls me saying “the WiFi’s down,” I ask them to check their phone. If their phone also has no internet while connected to the same network, the problem’s the router or modem. If the phone works fine, it’s a device-specific glitch.

So first thing: grab your phone, connect it to the same WiFi network. Open any website. If it loads, you’ve narrowed it down to your laptop or desktop. If it doesn’t, skip to the 5-minute fix below.

For the phone test — if your phone works, the problem’s almost always a stuck DNS cache or a corrupted IP lease on the device that’s broken. I’ve seen this a hundred times: a coworker last week couldn’t access Slack on her work laptop but could browse on her iPhone. Fixed it in 90 seconds with the next step.

The 5-Minute Fix: Flush DNS & Reset IP

This fixes maybe 70% of “WiFi connected no internet” cases. You don’t need admin access for the DNS flush, but you’ll need it for the IP reset. Here’s the exact sequence that works on Windows 10 and 11:

1. Open Command Prompt as Administrator (right-click Start, choose “Command Prompt (Admin)” or “Windows Terminal (Admin)”).
2. Type ipconfig /release and hit Enter. Wait 5 seconds.
3. Type ipconfig /renew and hit Enter. This can take 30 seconds or so — be patient.
4. Type ipconfig /flushdns and hit Enter.
5. Type netsh winsock reset and hit Enter.
6. Type nbtstat -R and hit Enter.
7. Restart your computer.

After the reboot, try loading a website. If it works, you’re done. If not, move to the next step.

Why does this work? When your laptop gets a DHCP lease from the router, it’s good for a set amount of time — usually 24 hours. But if the router resets or the lease expires weirdly, your laptop holds onto a dead IP address. The release/renew forces it to ask for a fresh one. The DNS flush clears out any cached domain lookups that might be pointing to nothing. Winsock reset just fixes the network stack itself — I’ve seen that alone fix weird SSL errors and “can’t reach this page” stuff.

The 15+ Minute Fix: TCP/IP Stack Reset & Driver Update

If the 5-minute fix didn’t work, the problem’s deeper. Either your network adapter driver is fried, or the TCP/IP stack is corrupt beyond what winsock reset can fix. Let’s go step by step.

Step 1: Reset the TCP/IP Stack Completely

Same Command Prompt as admin. Run these commands in order:

netsh int ip reset C:\resetlog.txt
netsh int tcp reset
netsh winsock reset

The first command resets the entire TCP/IP configuration to default. The resetlog.txt file is just a log — you can delete it later. After you run those, restart your PC.

If that still doesn’t work, you’ve got a hardware or driver issue. Let’s check that.

Step 2: Reinstall the WiFi Adapter Driver

1. Open Device Manager (right-click Start > Device Manager).
2. Expand “Network adapters”.
3. Find your WiFi card — usually says “Wireless” or “Wi-Fi” and the vendor name (Intel, Realtek, Qualcomm, Broadcom).
4. Right-click it and select “Uninstall device”. Check the box that says “Delete the driver software for this device” if it’s there.
5. Restart your PC. Windows will automatically reinstall the generic driver on boot.

This fixes a surprisingly large number of “no internet” cases. I had a client last month whose WiFi showed full bars but couldn’t load anything after a Windows update. The update had corrupted the Intel driver. Uninstalling and letting Windows reinstall the original driver fixed it instantly.

Step 3: Check for IP Conflicts

If you’re on a network with static IPs (like some office networks), another device might be using the same IP. Run this in Command Prompt:

arp -a

Look at the list. If you see two devices with the same IP, that’s your problem. Switch your device to “Obtain an IP automatically” in the adapter settings. On Windows: Settings > Network & Internet > Wi-Fi > Hardware properties > IP assignment > Edit > Automatic (DHCP).

Step 4: Disable IPv6 (Temporary Test)

Some ISPs or routers have iffy IPv6 support. Disabling it can force your device to use IPv4, which is rock-solid. Here’s how:

1. Go to Network Connections (run ncpa.cpl from the Run dialog).
2. Right-click your WiFi adapter, choose Properties.
3. Uncheck “Internet Protocol Version 6 (TCP/IPv6)”.
4. Click OK, then restart your PC.

If this fixes it, you can leave IPv6 off. Honestly, very few services actually need it today. I’ve had it disabled on my own laptop for two years without a single issue.

One Last Thing: Check the Router Itself

If none of this worked, the problem’s almost certainly the router or modem. Do a full power cycle: unplug the modem and the router. Wait 60 seconds. Plug the modem in first, wait for all the lights to stabilize (usually 2–3 minutes). Then plug the router in, wait another 2 minutes. Then reconnect your device.

If that doesn’t work, you might need to call your ISP. But honestly, in my 10 years of IT consulting, the 5-minute fix above solves this 9 times out of 10. Save the deeper stuff for when you’re really stuck.