How to Fix Constant 'Limited Connectivity' or 'No Internet' Warnings
Your device shows 'Limited Connectivity' or 'No Internet' warnings even though WiFi is connected - here's how to fix these persistent errors.
What's Happening
The Wi-Fi shows connected but Windows or your phone slaps a yellow triangle or "No Internet" on it. The thing to understand is that "limited connectivity" is a verdict your device reaches, not a fact about the line. Your device hands out a DHCP lease, then runs a quiet reachability test (Windows pings a Microsoft endpoint, Apple checks a captive-portal URL). If the gateway, DHCP, or DNS step fails, you get the warning even when other devices are fine — or you get the warning while everything actually works because the test itself was blocked. Almost every fix below is about figuring out which of those steps broke.
Quick Checks (Do These First)
- Does the internet actually work? Load a real website before troubleshooting. The warning is often wrong.
- One device or all of them? One device = that device's network stack. All devices = the router or the line.
- Check the modem's internet/WAN light. Solid and the right color = the ISP link is up. Red or off = nothing below this point matters until that's fixed.
- Restart the affected device once. A stuck adapter state clears on reboot more often than people expect.
Read the Numbers Before You Touch a Setting
This one check tells you exactly which step failed. Open Command Prompt and run ipconfig /all, then read three lines:
- IP address starts with
169.254.x.x→ DHCP failed. The device never got a real lease from the router. This is a router/DHCP problem (Fix 1 then Fix 7), not DNS — changing DNS won't help. - Normal IP (192.168.x.x) but a blank or wrong Default Gateway → routing is broken; the device doesn't know where to send traffic. Reset the adapter (Fix 1).
- Normal IP and gateway, but websites fail by name while
ping 1.1.1.1works → it's pure DNS. Go straight to Fix 2.
That three-line read replaces twenty minutes of guessing — each result points at exactly one fix and rules the others out.
Step-by-Step Fixes
Fix 1: Reset the Network Adapter (Windows)
Use this when you see a 169.254 address or a missing gateway — the adapter is holding a bad state.
- Right-click Start and open Terminal (Admin) or Command Prompt (Admin)
- Run these one at a time:
ipconfig /releaseipconfig /flushdnsipconfig /renewnetsh winsock resetnetsh int ip reset
- Restart the computer
- Reconnect to Wi-Fi and recheck
ipconfig /all— you should now have a real IP and gateway
Fix 2: Change DNS Servers
Use this only when names fail but raw IPs work.
- Settings > Network & Internet > Wi-Fi > Hardware properties
- Edit next to DNS server assignment > Manual > turn on IPv4
- Preferred:
1.1.1.1(Cloudflare). Alternate:8.8.8.8(Google) - Save and test
Mac: System Settings > Network > your connection > Details > DNS > add 1.1.1.1 and 8.8.8.8, remove the rest.
Fix 3: Turn Off the Metered Connection Flag
Windows throttles background networking when it thinks a connection is metered, which can surface as limited connectivity.
- Settings > Network & Internet > Wi-Fi > click your network
- Turn Metered connection OFF
- Disconnect and reconnect
Fix 4: Disable IPv6 (Test Only)
A network that advertises IPv6 but routes it poorly can trip the connectivity check while IPv4 works fine.
- Settings > Network & Internet > Advanced network settings > More network adapter options
- Right-click your Wi-Fi adapter > Properties
- Uncheck Internet Protocol Version 6 (TCP/IPv6) > OK
- Reconnect. If it doesn't help, turn it back on — IPv6 isn't the enemy by default
Fix 5: Update or Reinstall the Wi-Fi Driver
- Right-click Start > Device Manager > expand Network adapters
- Right-click the Wi-Fi adapter > Update driver > Search automatically
- No update found? Right-click > Uninstall device (check "delete driver software"), then restart — Windows reinstalls it
Fix 6: Set a Static IP (When DHCP Keeps Failing on One Device)
- Run
ipconfig /alland note Subnet Mask, Default Gateway, and a free IP in your range - Wi-Fi > Hardware properties > Edit next to IP assignment > Manual > IPv4
- Enter an unused address (e.g.
192.168.1.50), the subnet mask, the gateway, and DNS1.1.1.1/8.8.8.8 - Save and test
Fix 7: Check Router DHCP (When Multiple Devices Get 169.254)
- Log into the router (usually
192.168.1.1) - Confirm the DHCP server is Enabled with a pool of at least 50 addresses and a 24-hour lease
- Reboot the router after changes
Where DIY Stops — And Why
If the warning sticks across every device after a clean adapter reset and a confirmed-good DHCP pool, you've passed what settings can fix. Past this point it's usually one of three things, and none of them is something you change in a menu:
- The router's DHCP service is intermittently failing — it hands out leases sometimes and not others, so devices flip between working and 169.254. That's a router fault, not a device one.
- The modem isn't fully provisioning — it powers on and the WAN light may look right, but it never authorizes cleanly with the ISP, so traffic stalls upstream of everything you can configure.
- A weak or noisy line in — coax/DSL signal out of spec causes packet loss that the connectivity test reads as "no internet" even though the link technically exists.
Separating a flaky router from a marginal incoming line takes looking at the modem's signal page and watching DHCP behavior over time — the diagnostic step a homeowner has no easy way to run, and exactly the kind of thing a network repair visit settles in one pass instead of by trial and replacement.
Need Professional Help?
If you're in the Tampa Bay area and need hands-on assistance, Geeks in Sneaks provides friendly, on-site tech support in Clearwater, Clearwater Beach, and Dunedin.
Related Topics
Need Professional Help?
If you're still having trouble, our expert technicians can help.
Learn about our network repair serviceMore Router & WiFi Fixes
See all Router & WiFi fixes →Business-Grade vs Consumer Routers for Home Use
Considering a business-grade router for your home? Find out if the premium price delivers real benefits for residential use.
Buying Used or Refurbished Routers: Safe or Risky?
Tempted to save money with a used router? Learn the real security risks and when buying secondhand is safe versus when it's dangerous.
How Long Should a Router Last? When to Replace Yours
Your router is a few years old and you're wondering if it's time to replace it. Learn the typical lifespan and warning signs it's failing.
Gaming Routers: Real Benefits vs Marketing Hype
Wondering if a gaming router is worth the premium price? We separate the real performance benefits from marketing gimmicks.
Renting ISP Equipment vs Buying Your Own: Real Cost Comparison
Paying monthly rental fees for your modem and router? Find out how much you could save by buying your own equipment.
Matching Router Capabilities to Your Internet Speed Tier
Have gigabit internet but not getting those speeds? Your router might be the bottleneck. Learn how to match equipment to your plan.
What to Look for When Buying a Home Router in 2026
Shopping for a new router can be overwhelming with all the technical specs and marketing claims—here's what actually matters in 2026.
When to Move from Single Router to Mesh WiFi System
Dead zones and weak WiFi in parts of your home? Find out if it's time to upgrade from a traditional router to a mesh system.