Seeing the Wi‑Fi status say "Connected, no Internet" on Windows or macOS is maddening. The good news: it usually points to a simple chain issue — your device can talk to the router, but the router (or its settings) isn’t reaching the Internet. This guide gives you fast, 3‑minute fixes first. If those don’t stick, follow an 8‑step diagnostic ladder that systematically checks your device, DNS, DHCP, and router WAN so you can get back online with confidence.
Table of Contents
- Why This Error Happens
- Three‑Minute Quick Fixes
- Eight‑Step Diagnostic Ladder
- Conclusion & Next Steps
- Frequently Asked Questions
Why This Error Happens
When you see "Wi‑Fi connected, no Internet," local connectivity is fine (device ⇄ router), but outbound connectivity (router ⇄ Internet) or name resolution may be broken. Common culprits include stale IP leases (DHCP), bad DNS answers, a hiccuping Wi‑Fi adapter or driver, or an ISP/router WAN outage. The steps below address these in the most time‑efficient order.
Three‑Minute Quick Fixes
Try these first. They resolve a large share of cases without deeper digging.
- Quick Fix 1: Power‑cycle your router/modem. Unplug power, wait 10–15 seconds, plug back in, then wait 1–2 minutes for a full boot. This clears transient faults and refreshes the WAN session.
- Quick Fix 2: Restart your computer. A clean reboot flushes temporary network glitches and resets the Wi‑Fi stack.
- Quick Fix 3: Check other devices on the same Wi‑Fi. If other devices can browse, the problem is likely on your computer. If none can browse, focus on the router/ISP side.
Prefer a walkthrough? Tap the thumbnail to watch the fast video guide.
Eight‑Step Diagnostic Ladder
Work through these in order. Test browsing after each step.
Step 1 — Run built‑in troubleshooters (Windows)
- Windows: Go to Settings > Network & Internet > Status > Network Troubleshooter. It can auto‑detect issues like gateway/DNS misconfigurations and reset components.
- macOS: If issues persist after the quick fixes, proceed to Step 2; you’ll address IP/DNS directly via System Settings and Terminal.
Step 2 — Renew your IP lease (DHCP)
- Windows: Open Command Prompt (Admin) and run: ipconfig /release then ipconfig /renew. This requests a fresh IP/gateway from the router.
- macOS: System Settings > Network > Wi‑Fi > Details > TCP/IP > Renew DHCP Lease.
Step 3 — Flush the DNS cache
- Windows: Open Command Prompt (Admin) and run: ipconfig /flushdns.
- macOS: Open Terminal and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your password if prompted. This clears stale lookups that can cause "connected, no Internet" symptoms.
Step 4 — Reset the Wi‑Fi adapter link
- Windows: Device Manager > Network adapters > right‑click your Wi‑Fi adapter > Disable device, then Enable device.
- macOS: Toggle Wi‑Fi off/on from Control Center or System Settings. This forces a fresh association with the access point.
Step 5 — Update Wi‑Fi drivers and OS
- Windows: In Device Manager, check for driver updates, or download the latest from your PC/Wi‑Fi adapter manufacturer.
- macOS: Install the latest system updates (driver updates are bundled). Outdated stacks often cause intermittent "no Internet" states.
Step 6 — Reset network settings
- Windows: Settings > Network & Internet > Advanced network settings > Network reset. This reinstalls adapters and resets sockets, DNS, and firewall profiles. You’ll need to reconnect to Wi‑Fi afterward.
- macOS: For a thorough reset, remove and re‑add your Wi‑Fi service in System Settings > Network, then reconnect. Advanced users can remove network preferences files before rebooting to fully rebuild network configs.
Step 7 — Switch to reliable public DNS
- Why: If your router’s or ISP’s DNS is down, you’ll be "connected" but unable to resolve websites.
- Windows/macOS: Set DNS to Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1) in your Wi‑Fi adapter’s IPv4 DNS settings. Reconnect and test.
Step 8 — Hardware and router WAN checks
- Swap hardware to rule out faults: If on Ethernet, try a different cable/port. If using a USB Wi‑Fi adapter, try another adapter if available.
- Check router WAN status: Confirm the Internet/WAN light is solid (not red/blinking). Log into the router admin page and verify it has a valid WAN IP (not 0.0.0.0). If there’s no WAN IP, reboot the modem and router; if still down, contact your ISP.
- Test raw connectivity: If you can, try browsing a known IP by entering http://1.1.1.1. If that loads but sites don’t, it’s a DNS issue (Step 7). If nothing loads and WAN shows down, it’s likely an ISP or line problem.
Conclusion & Next Steps
Start simple: power‑cycle the router, reboot your computer, and test another device. If the issue persists, walk the ladder — renew IP (DHCP), flush DNS, reset/re‑enable the adapter, update drivers/OS, reset network settings, switch DNS, and verify router WAN health. This sequence isolates the root cause quickly and safely.
If you found a specific step that fixed it, consider keeping that setting (for example, public DNS) and note the change for future reference. And if your router’s WAN keeps dropping, contact your ISP with the time of the outage and what you’ve already tried.
Frequently Asked Questions
Why does my laptop say it’s connected to Wi‑Fi but there’s no Internet?
Your device can reach the router, but name resolution (DNS), IP assignment (DHCP), or the router’s WAN/ISP link is failing. The ladder above pinpoints which layer is at fault.
Is changing DNS to Google or Cloudflare safe?
Yes. Public DNS providers like Google (8.8.8.8) and Cloudflare (1.1.1.1) are widely used, fast, and reliable. You can always switch back to automatic DNS later.
Will a network reset delete my Wi‑Fi passwords?
On Windows, Network reset removes and reinstalls adapters and clears saved networks, so you’ll re‑enter Wi‑Fi passwords. On macOS, removing a service or preferences also requires reconnecting.
What if only one device has the problem?
Focus on device‑side steps: restart, renew DHCP, flush DNS, re‑enable the adapter, update drivers/OS, and reset network settings. If other devices work, the router/ISP is likely fine.


Leave a Reply