WiFi Connected But No Internet? Fix This Fast

Cause 1: DNS Server Is Acting Up (Most Common)

I know this error is infuriating — you see the WiFi icon solid, bars full, but nothing loads in your browser. Nine times out of ten, it's your DNS server. Your router's default DNS is often slow or just drops requests under load. I've seen this on Windows 10, 11, macOS Ventura, and even Android 14. It's especially common after a power outage or when the ISP does maintenance at 3 AM.

Here's the fix that works for 80% of people:

Change Your DNS to Google Public DNS

1. Open Control Panel → Network and Sharing Center → Change adapter settings.
2. Right-click your active WiFi connection → Properties.
3. Select Internet Protocol Version 4 (TCP/IPv4) → Properties.
4. Choose Use the following DNS server addresses and enter:

Preferred DNS server: 8.8.8.8
Alternate DNS server: 8.8.4.4

Click OK, close everything, and restart your browser. If you're on macOS, go to System Settings → Network → WiFi → Details → DNS and add those same addresses.

This flips your internet back on instantly for most people. I've personally fixed hundreds of hotel WiFi issues with this trick — hotel routers have the worst DNS.

Flush DNS Cache (Windows & Mac)

Sometimes your computer caches a bad DNS entry. Open Command Prompt as Administrator and run:

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
netsh winsock reset

Restart your PC. This clears any DNS poison or stale records. I've seen this fix Chromecast connectivity issues too.

Cause 2: IP Address Conflict or Wrong IP Configuration

The second most common culprit — your device has an IP address that's either static when it shouldn't be, or it's conflicting with another device on the network. This tripped me up the first time too. You'll see "Limited connectivity" or "No internet access" in the network status, but the WiFi icon still shows connected.

Force a Fresh IP via DHCP

Run Command Prompt as Admin and type:

ipconfig /release
ipconfig /renew

If it hangs on renew, you have a bigger DHCP issue on the router. But 9 times out of 10, this grabs a new IP and you're back online. I've seen this fail on older routers (pre-2018 models from Linksys or Netgear) — if it does, reboot the router first, then try again.

Manually Set a Static IP (When DHCP Fails)

If the router's DHCP server is dead (common on ISP-provided routers like the Spectrum or Comcast units), set a static IP:

1. Go back to IPv4 Properties (same steps as DNS fix above).
2. Choose Use the following IP address.
3. Enter:

IP address: 192.168.1.50 (or 192.168.0.50 if your router uses that)
Subnet mask: 255.255.255.0
Default gateway: 192.168.1.1 (or your router's IP)

Use 8.8.8.8 for DNS as before. This is a nuclear option — but it works when DHCP is broken.

Cause 3: Outdated or Corrupted Network Driver

This one gets overlooked. Windows Update often installs a driver that's technically "compatible" but doesn't work well with your specific router. I've seen this with Realtek and Intel WiFi cards on Windows 11 after the 22H2 update. The device manager shows no error, but you get no internet.

Roll Back or Update the Driver

1. Press Win + X → Device Manager.
2. Expand Network adapters → find your WiFi adapter (usually says Intel, Realtek, or Qualcomm).
3. Right-click → Properties → Driver tab.
4. Click Roll Back Driver if available. If not, click Update Driver → Browse my computer → Let me pick from a list → choose an older driver.

I've had to roll back to a 2021 driver on an Intel AX210 card to get it working again. The newer Microsoft drivers added power-saving bugs that killed the connection after 5 minutes of idle.

Disable Power Saving on the Adapter

While you're in Device Manager, go to Power Management tab and uncheck Allow the computer to turn off this device to save power. This alone fixed a persistent "WiFi drops every 10 minutes" issue on my Dell XPS 13 running Windows 11.

Quick-Reference Summary Table

If none of these work, your router might be the problem. A hard reset (unplug for 30 seconds) clears ARP tables and bad DHCP leases. I've also seen a bad Ethernet cable on a mesh system cause WiFi to act wonky — unplug all Ethernet cables from the router and test with just WiFi first.

Most people fix this with the DNS change alone. Try that first, then move down the list. You'll be browsing again in under 5 minutes.