Quick fix: Open Terminal (Admin), run ipconfig /flushdns, then netsh int ip reset, then reboot — 70% of “connected but no internet” cases come back online with this three-command sequence.
Your Wi-Fi shows connected with full signal bars, but no website loads. The browser hangs at “Connecting…”. Some apps show offline. Other devices on the same network work fine. The connection is real but something between your laptop and the wider internet is broken — typically DNS, gateway routing, or a captive-portal authentication issue.
Affects: Windows 11 (and Windows 10) on Wi-Fi or Ethernet with a working physical connection.
Fix time: ~10 minutes.
What causes this
The connection chain has multiple layers, any of which can fail in isolation. DHCP: your PC has an IP address but it’s stale or wrong. DNS: your PC can’t resolve domain names even though IP-level connectivity works. Default gateway: routing is broken; packets don’t reach the internet. Captive portal: hotel/cafe Wi-Fi expects you to sign in via a browser, and Windows didn’t pop the page. VPN or proxy: a dead VPN tunnel is holding your traffic. Firewall: Windows Firewall or third-party security software is blocking outbound traffic.
Method 1: Diagnose with ping and reset DNS/TCP
Identifies which layer is broken in 30 seconds, then fixes it.
- Open Terminal (Admin).
- Test IP-level connectivity:
ping 8.8.8.8If this works: routing is fine. The issue is DNS. If this fails: routing is the issue.
- Test DNS resolution:
nslookup google.comIf this fails or times out: DNS is the problem.
- Reset the DNS cache and stack:
ipconfig /flushdns ipconfig /registerdns netsh int ip reset - Reboot. Test again.
- If DNS still fails, set explicit DNS servers: Settings → Network & internet → Wi-Fi → (your network) → DNS server assignment → Manual. Use 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google).
The combination of flushdns + ip reset clears the most common cause of “connected but no internet” — corrupted DNS cache.
Method 2: Check for and complete captive portal sign-in
Use this when you’re on hotel, airport, conference, or coffee shop Wi-Fi.
- Open a browser (Edge works most reliably for captive portals).
- Visit a plain HTTP site (not HTTPS):
http://example.comorhttp://neverssl.com. - The captive portal page should redirect you to a sign-in form (terms of service, room number, voucher code).
- Complete the sign-in. The captive portal whitelists your MAC address.
- If the redirect doesn’t happen, Windows’ captive portal detection failed. Force-trigger it: Settings → Network & internet → Wi-Fi → (your network) → Forget, then reconnect from scratch.
- For chronic captive portal issues, ensure Windows’ NCSI (Network Connectivity Status Indicator) probe is reaching
http://www.msftconnecttest.com/connecttest.txt— if firewall blocks this, captive portal pop-ups don’t appear.
The little globe icon (instead of Wi-Fi bars) usually signals captive portal — but on some Wi-Fi networks it shows full bars too.
Method 3: Disable VPN, proxy, and reset Winsock
Use when DNS and captive portal aren’t the issue.
- Check for active VPN connections: Settings → Network & internet → VPN. Disconnect any active VPN.
- Check for proxy settings: Settings → Network & internet → Proxy. Set Use a proxy server to Off if it’s on. Set Automatic proxy setup to Off as well.
- Reset Winsock and TCP/IP fully:
netsh winsock reset netsh int ip reset netsh int ipv4 reset netsh int ipv6 reset ipconfig /release ipconfig /renew ipconfig /flushdns - Check Windows Firewall status:
Get-NetFirewallProfile | Format-Table Name, Enabled, DefaultOutboundActionDefaultOutboundAction should be Allow. If it shows Block, run
Set-NetFirewallProfile -All -DefaultOutboundAction Allow. - Temporarily disable third-party antivirus (Norton, McAfee, Bitdefender, ESET). Many bundle a network filter that can block traffic after a software update.
- Reboot.
This sequence catches the residual cases — failed VPN tunnels, hidden proxy configurations, antivirus network filters.
How to verify the fix worked
- Run
Test-NetConnection -ComputerName www.google.com -Port 443in PowerShell. TcpTestSucceeded: True; NameResolutionSucceeded: True. - Open a browser. Multiple websites load at normal speed.
- The network icon in the system tray shows Wi-Fi bars (not a globe with X mark).
If none of these work
If the PC remains connected with no internet after all three methods, the issue is upstream of the laptop. Other devices working confirms the router and ISP are fine — so it’s a Windows-side configuration. Check Hosts file: open C:\Windows\System32\drivers\etc\hosts in Notepad (run Notepad as admin). Confirm there are no rogue entries blocking domains (recent malware sometimes adds entries that NX domains for major sites). The default hosts file has only comments and a single localhost line. Check date and time: if your PC’s clock is dramatically wrong (more than a few hours off), HTTPS connections fail certificate validation and appear as “no internet.” Fix in Settings → Time & language → Date & time → Sync now. Check IPv6 issues: try disabling IPv6 on the adapter (Network Connections → right-click adapter → Properties → uncheck IPv6) — some ISPs and routers handle IPv6 poorly. Persistent failure after all of this suggests reinstalling the network adapter driver, then performing a full Settings → Network reset as a last resort.
Bottom line: “Connected but no internet” is almost always DNS, captive portal, or stale TCP state — diagnose with ping, reset the stack, and check for captive portal sign-in pages.