Network & Connectivity Errors: Fixes That Actually Work

I know how infuriating this is. You sit down, open a browser, and get nothing. The wifi icon has that little yellow exclamation mark, or worse — it says "Connected, no internet." You've probably already rebooted the router. That's fine, it's step zero. Now let's actually fix this.

After six years of running a help desk, I can tell you that 80% of connectivity errors come down to three things: a busted IP lease, a DNS resolver that's lost its mind, or a network adapter driver that Windows silently broke during an update. Work through them in this order. Don't skip ahead.

Cause 1: Your IP lease is stale or the DHCP handshake failed

This is the big one. Your router hands out IP addresses via DHCP, and sometimes that lease expires or the handshake gets tangled — especially after a router reboot, a VPN disconnect, or waking from sleep. You'll see a 169.254.x.x address (that's the APIPA fallback Windows uses when it can't reach a DHCP server). That address means "I gave up trying to get a real IP."

Open Command Prompt as admin. Not PowerShell yet — plain cmd, run as administrator. Then:

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

Reboot. I mean it — the winsock reset won't take effect until you restart. I've seen people run these commands, declare victory, and then wonder why nothing changed. Restart the machine.

If you're still stuck on 169.254 after the reboot, the problem isn't your PC. It's the router or the cable. Try a different Ethernet port on the router, swap the cable, or log into the router admin page (usually 192.168.1.1 or 192.168.0.1) and check that the DHCP pool isn't exhausted. Home routers cap out at 50-100 leases by default, and every smart bulb, phone, and tablet eats one.

Cause 2: DNS is failing to resolve

Here's the tell: your browser says "This site can't be reached" or "DNS_PROBE_FINISHED_NXDOMAIN," but ping 8.8.8.8 works fine. That means your network layer is healthy — packets are flowing — but name resolution is broken. Your ISP's DNS servers are having a bad day, or your router is caching poisoned entries.

The real fix is to stop using your ISP's DNS. Switch to Cloudflare (1.1.1.1) or Google (8.8.8.8). On Windows 11, go to Settings → Network & Internet → your adapter → Edit DNS server assignment → Manual → IPv4 on. Enter 1.1.1.1 as preferred and 1.0.0.1 as alternate. Save.

You can also do it from the command line if you prefer:

netsh interface ip set dns "Wi-Fi" static 1.1.1.1 primary
netsh interface ip add dns "Wi-Fi" 1.0.0.1 index=2

Swap "Wi-Fi" for "Ethernet" if that's your connection. Then flush DNS one more time:

ipconfig /flushdns

Test with nslookup google.com. If it returns an IP, you're done. If it hangs for 30 seconds and times out, your firewall or a VPN client is intercepting DNS on port 53. NordVPN and Cisco AnyConnect are notorious for leaving behind DNS filter drivers after uninstall. Check Network Adapters in Device Manager for stray "TAP" or "TUN" virtual adapters and remove them.

Cause 3: Network adapter driver is corrupt or outdated

This one sneaks up on you. Windows Update pushes a driver, the wifi works for a week, then one day it doesn't. Or you get the classic "Windows could not automatically detect this network's proxy settings" error. The driver is technically installed but functionally broken.

Open Device Manager (Win+X, then M). Expand Network adapters. Look for a yellow triangle or an adapter that says "Microsoft Wi-Fi Direct Virtual Adapter" but no physical Realtek or Intel adapter. Right-click your main adapter → Uninstall device → check "Delete the driver software for this device" → Uninstall.

Reboot. Windows will reinstall a fresh driver automatically. If it doesn't, download the driver from the manufacturer's site on another machine and transfer it via USB. For Intel AX200 and AX210 chips (common in laptops from 2020 onward), grab the latest driver from Intel's site directly — Windows Update is often 6+ months behind and the newer driver fixes the "connected but no internet" bug on 5GHz networks.

Pro tip: if you're on a Dell or Lenovo laptop, use their official driver utility (Dell Command Update or Lenovo Vantage). Generic Intel drivers sometimes break the OEM power management profile and your wifi drops every time the laptop sleeps.

When none of this works

Check the physical layer. Really. I've watched a senior engineer spend two hours on driver rollbacks before noticing a bent RJ45 pin. Try a different cable, a different port, a different device on the same network. If your phone connects fine over wifi but the laptop doesn't, it's the laptop. If nothing connects, it's the router or the ISP — call them and skip the scripted reboot dance by saying "I've already reset the modem, the router, and my PC's network stack. Can you check the line status on your end?"

Quick reference

Work top to bottom. Most of you will be back online after step one. The rest of you — it's DNS or the driver, and now you know where to look.