WiFi Connected but No Internet: 3 Proven Fixes

1. DNS and IP Conflict: The Most Common Sneaky Culprit

This one tripped me up the first time too. You're connected to the network—bars are full, the icon says “Internet access” or “Connected, secured”—but nothing loads. Not Chrome, not Edge, not even a ping in CMD.

Most of the time, it’s a DNS or IP conflict. Your router handed your device an IP address, but something got crossed. Maybe your phone’s IP is clashing with another device, or your DNS settings are pointing to a dead server.

The quickest fix? Release and renew your IP, then flush the DNS cache. Here’s exactly what you do on Windows 10 or 11:

1. Press Windows Key + X and select Windows Terminal (Admin) or Command Prompt (Admin).
2. Type this and hit Enter after each line:

ipconfig /release
ipconfig /renew
ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Wait for each command to finish. The /release and /renew may take a few seconds—that’s normal. Once done, restart your computer.

I’ve seen this fix work on HP laptops with Realtek WiFi cards and Dell machines with Intel adapters. If you’re on a Mac, go to System Settings > Network > WiFi > Details > Renew DHCP Lease. Same idea, cleaner UI.

Why does this happen? Often after a power outage, a router reboot, or moving your laptop between two networks (like from office WiFi to home WiFi). The DHCP lease expires or gets confused. Forcing a fresh lease clears that up.

If this didn't work—don’t panic. The next cause is just as common.

2. Router or Modem Glitch: The Power Cycle That Actually Matters

I know it sounds basic, but hear me out. Most people unplug their router, plug it back in after ten seconds, and wonder why it didn't help. That’s because you’re not giving the modem time to fully discharge, and you’re skipping a key step.

The real fix: power cycle both the modem and router, in order, for at least 60 seconds.

1. Unplug both the modem and the router from power.
2. Wait 60 seconds—yes, set a timer. Caps in the hardware hold charge for a while.
3. Plug in the modem first. Wait until all the lights stop flashing and show a steady connection (usually 2-3 minutes).
4. Plug in the router. Wait another 2 minutes until its lights stabilize.
5. Reconnect your device and test.

This isn't a superstition. The modem needs to re-establish a handshake with your ISP before the router can assign IPs. If you power both on at the same time, they fight for attention and one side—usually the router—gives up and keeps an old, broken configuration.

I’ve seen this cause “No Internet, Secured” on TP-Link Archer A7 routers, Netgear Nighthawks, and even the AT&T gateway that comes with fiber. The fix is the same across all of them.

Still no luck? Let’s go deeper.

3. Corrupted TCP/IP Stack or Winsock: When Windows Itself Is the Problem

If the first two fixes didn’t work, Windows has likely corrupted its own networking stack. Viruses, failed updates, or even a bad VPN install can mess up the TCP/IP settings or Winsock catalog.

You’ll know this is the case if you open Command Prompt and see ping 8.8.8.8 returning “General failure” or “Transmit failed. Error code 1231.”

Here’s how to reset it cleanly:

1. Open Command Prompt as Admin again (same as before).
2. Run these commands in order:

netsh winsock reset catalog
netsh int ip reset reset.log
netsh int ipv4 reset
netsh int ipv6 reset

Then restart your PC. After reboot, run netsh winsock show catalog in CMD to confirm it says “Reset complete” and the catalog is clean.

I’ve had this happen on a Lenovo ThinkPad after a botched Windows 11 22H2 update. The fix above restored internet access in under two minutes.

If none of these work, check if your antivirus or firewall is blocking traffic—try disabling it temporarily. Also, update your WiFi driver from the manufacturer’s site (not Windows Update). Intel and Realtek both have driver utilities that scan for the latest version.

Quick-Reference Summary Table

One last thing: if you’re on a corporate or school network that uses 802.1X authentication (like eduroam or a company VPN), none of these will help. That’s a different beast—usually a certificate or authentication issue. But for home WiFi? These three fixes cover 90% of cases.