Connected But No Internet: Complete Troubleshooting Guide for All Devices & Connections
Fix 'connected but no internet' on Windows 10/11, Mac, iPhone, Android, Ethernet & hotspot. Step-by-step commands and proven fixes. Resolve in minutes.
- Root cause 1: IP address conflict or DHCP failure — your device received an APIPA address (169.254.x.x) or no address at all, so it can reach the router but not the internet.
- Root cause 2: DNS misconfiguration or corruption — your device can get an IP but cannot resolve domain names, making every website appear unreachable even though the connection is live.
- Root cause 3: ISP-side outage, gateway misconfiguration, or captive portal interception — the router itself has no WAN connectivity, or a carrier portal is blocking traffic until credentials are submitted.
- Quick fix summary: Run 'ipconfig /release && ipconfig /renew' (Windows) or 'sudo ipconfig set en0 DHCP' (Mac), flush DNS with 'ipconfig /flushdns', switch DNS to 8.8.8.8, restart your modem/router in sequence, and test with 'ping 8.8.8.8' to isolate the layer at which connectivity breaks.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Release & Renew IP (ipconfig /release /renew) | Device shows 169.254.x.x or 0.0.0.0 IP address | < 1 min | None |
| Flush DNS Cache | Websites fail but ping to 8.8.8.8 succeeds | < 1 min | None |
| Change DNS to 8.8.8.8 / 1.1.1.1 | DNS resolution fails for all domains | 2 min | None |
| Power-cycle modem & router (30-30-30 method) | All devices on network lose internet simultaneously | 5 min | None |
| Reset TCP/IP stack (netsh int ip reset) | Persistent failure after all other steps on Windows | 2 min + reboot | Low — may clear custom IP rules |
| Reinstall network adapter driver | Adapter shows errors in Device Manager | 10 min | Low |
| Factory reset router | Router firmware corruption suspected | 15–30 min | Medium — erases all settings |
| Contact ISP / check outage map | WAN IP missing on router admin page | Varies | None |
Understanding 'Connected But No Internet'
The message 'Connected, no Internet' (Windows) or the yellow exclamation mark on your network icon means your device successfully joined a local network — Wi-Fi, Ethernet, hotspot, or mobile data — but cannot reach the public internet. The connection exists at Layer 2 (data link) but fails at Layer 3 (network/IP) or Layer 7 (application/DNS). Understanding which layer is broken is the key to a fast fix.
Windows detects internet connectivity by pinging www.msftconnecttest.com (Windows 10/11) or www.msftncsi.com (Windows 7/8). If that request fails, you see the 'no internet access' indicator even if some services still work.
Step 1: Identify the Scope of the Problem
Before touching any settings, answer these three questions:
Is only one device affected, or all devices?
- Only one device → problem is on the device (driver, DNS, IP config).
- All devices → problem is the router, modem, or ISP.
Is the problem Wi-Fi, Ethernet, or cellular/hotspot?
- Try a different connection type to isolate.
Can you ping the router's gateway IP?
- Open Command Prompt (Windows) or Terminal (Mac/Linux) and run
ping 192.168.1.1(replace with your gateway). If this fails, the issue is local. If it succeeds, the issue is between your router and the internet.
- Open Command Prompt (Windows) or Terminal (Mac/Linux) and run
Step 2: Check Your IP Address
An APIPA address in the range 169.254.x.x (Windows) or self-assigned (Mac) means your device failed to get an IP from the DHCP server.
Windows:
ipconfig /all
Look for IPv4 Address. If it starts with 169.254, DHCP has failed.
Mac: Go to System Preferences → Network → select your interface → click Advanced → TCP/IP tab. A 'Self-Assigned IP' label confirms APIPA.
Linux / Android (rooted):
ip addr show
Fix: Release and renew your IP (see the code block section for full commands).
Step 3: Test DNS Resolution
If your IP is valid (e.g., 192.168.x.x or 10.x.x.x), test whether DNS is the culprit:
ping 8.8.8.8
- Ping succeeds → IP routing works, DNS is broken. Change DNS servers.
- Ping fails → routing problem, go to Step 4.
Test DNS directly:
nslookup google.com 8.8.8.8
If this resolves but normal browsing fails, your assigned DNS servers are broken. Switch to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).
How to change DNS on Windows 10/11:
- Open Settings → Network & Internet → Change adapter options.
- Right-click your adapter → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties.
- Select 'Use the following DNS server addresses'.
- Preferred:
8.8.8.8| Alternate:8.8.4.4. - Click OK and test.
How to change DNS on Mac:
- System Preferences → Network → Advanced → DNS tab.
- Click
+and add8.8.8.8and1.1.1.1. - Click OK → Apply.
How to change DNS on iPhone/iPad:
Settings → Wi-Fi → tap the (i) next to your network → Configure DNS → Manual → add 8.8.8.8.
How to change DNS on Android:
Settings → Network & Internet → Private DNS → enter dns.google or one.one.one.one.
Step 4: Power-Cycle Your Network Hardware
For cable, fiber (Fios, Frontier, CenturyLink), satellite (HughesNet), or broadband connections where all devices are affected:
- Unplug the modem from power. Wait 60 seconds.
- Unplug the router from power. Wait 30 seconds.
- Plug the modem back in. Wait for all lights to stabilize (60–90 seconds).
- Plug the router back in. Wait 60 seconds.
- Reconnect your device and test.
This clears stale DHCP leases, resets WAN authentication (PPPoE), and forces the modem to re-register with the ISP.
Step 5: Reset the TCP/IP Stack and Winsock (Windows)
If IP renewal and DNS changes haven't worked, the TCP/IP stack itself may be corrupted — common after malware removal, VPN client uninstalls, or botched driver updates.
Run Command Prompt as Administrator and execute:
netsh int ip reset resetlog.txt
netsh winsock reset catalog
ipconfig /flushdns
ipconfig /registerdns
Restart your computer after these commands.
Step 6: Check for Captive Portals
Hotspots, hotel Wi-Fi, school networks, and some ISPs (including mobile carriers using US Cellular, Boost Mobile, or Alcatel LinkZone 2 hotspots) intercept HTTP traffic to display a login or terms-of-service page. Your device shows 'connected' because it has an IP, but all traffic is redirected.
Fix: Open a browser and navigate to http://neverssl.com or http://captive.apple.com. This forces an HTTP (non-HTTPS) request that the captive portal can intercept and display. Complete the login, and internet access is restored.
Step 7: Device-Specific Fixes
Ethernet connected but no internet (Windows 10/11/7):
- Check that the Ethernet cable is fully seated (click into place).
- Try a different cable or port on the router.
- Update or reinstall the network adapter driver: Device Manager → Network Adapters → right-click → Update Driver.
- Disable and re-enable the adapter:
ncpa.cpl→ right-click adapter → Disable → Enable.
Mac / iMac connected but no internet:
- System Preferences → Network → select interface → click the gear icon → Make Service Inactive → Make Service Active.
- Create a new network location: Network → Location dropdown → Edit Locations → add new location.
- Renew DHCP lease: Advanced → TCP/IP → Renew DHCP Lease.
iPhone / iPad connected but no internet:
- Toggle Airplane Mode on and off.
- Forget the Wi-Fi network and reconnect: Settings → Wi-Fi → tap
(i)→ Forget This Network. - Reset network settings: Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings.
Android hotspot / tablet connected but no internet:
- Toggle mobile data off and on.
- Check data plan status — carrier throttling or data cap exhaustion causes this exactly.
- APN settings may be wrong: Settings → Network & Internet → Mobile Network → Advanced → APNs. Contact your carrier for correct APN settings (critical for Alcatel LinkZone 2, US Cellular, and 4G LTE routers).
Smart TV (Hisense, LG) connected but no internet:
- Use a wired Ethernet connection to bypass Wi-Fi issues.
- Set DNS manually in the TV's network settings to
8.8.8.8. - Perform a soft reset: unplug the TV from power for 60 seconds.
4G LTE / 5G router or MiFi connected but no internet:
- Log into the router admin panel (usually
192.168.0.1or192.168.8.1). - Check WAN status — if no IP is assigned, verify APN settings.
- Check signal strength; move the device to a window or elevated position.
- Reinsert the SIM card and ensure it is activated.
Step 8: Check the Router's WAN Status
Log into your router's admin interface (usually http://192.168.1.1 or http://192.168.0.1). Navigate to the WAN or Internet status page. Look for:
- WAN IP address: Should be a public IP (not
0.0.0.0or blank). If blank, the router is not authenticated with the ISP. - DNS from ISP: Should show valid DNS IPs.
- Connection type: If set to PPPoE (Fios, Frontier, CenturyLink DSL), ensure credentials are correctly entered.
If the WAN IP is missing, contact your ISP. Check their outage map or status page before calling:
- Verizon Fios:
downdetector.com/status/verizon-fios - HughesNet:
status.hughes.net - CenturyLink:
centurylink.com/local/outages.html - Frontier:
frontier.com/local/support/outages
Step 9: Check Firewall and Security Software
Antivirus programs, VPN clients, and third-party firewalls can intercept connections and cause the 'connected but no internet' symptom.
Test: Temporarily disable your antivirus or firewall and test connectivity. If internet is restored, the security software is the culprit. Re-enable it and check for:
- Web shield or HTTPS scanning settings blocking traffic.
- VPN split-tunneling misconfiguration.
- DNS filtering rules blocking all external DNS.
Step 10: When to Call Your ISP
Call your ISP if:
- The WAN IP on your router is
0.0.0.0or blank after a full power-cycle. - All devices are affected and local troubleshooting has failed.
- The problem appeared after a recent service change, installation, or area storm.
- The modem's online/sync light is red or not lit.
Frequently Asked Questions
# ============================================================
# CONNECTED BUT NO INTERNET - DIAGNOSTIC & FIX SCRIPT
# Run elevated Command Prompt (Windows) or Terminal (Mac/Linux)
# ============================================================
# --- WINDOWS COMMANDS ---
# 1. Check current IP configuration (look for 169.254.x.x = APIPA = DHCP failure)
ipconfig /all
# 2. Check default gateway reachability (replace 192.168.1.1 with your gateway)
ping 192.168.1.1 -n 4
# 3. Test raw internet connectivity bypassing DNS
ping 8.8.8.8 -n 4
# 4. Test DNS resolution
nslookup google.com
nslookup google.com 8.8.8.8
# 5. Release and renew IP address (fixes DHCP/APIPA issues)
ipconfig /release
ipconfig /renew
# 6. Flush DNS resolver cache
ipconfig /flushdns
# 7. Register DNS
ipconfig /registerdns
# 8. Reset TCP/IP stack (run as Administrator, then reboot)
netsh int ip reset C:\resetlog.txt
# 9. Reset Winsock catalog (run as Administrator, then reboot)
netsh winsock reset catalog
# 10. Disable and re-enable network adapter (replace "Ethernet" with adapter name)
netsh interface set interface "Ethernet" admin=disable
netsh interface set interface "Ethernet" admin=enable
# 11. Set DNS manually to Google DNS
netsh interface ip set dns name="Ethernet" static 8.8.8.8
netsh interface ip add dns name="Ethernet" 8.8.4.4 index=2
# 12. Check routing table
route print
# 13. Trace route to diagnose where connection breaks
tracert 8.8.8.8
# 14. Windows Network Diagnostics reset (PowerShell as Admin)
Get-NetAdapter | Restart-NetAdapter
# ============================================================
# --- MAC / LINUX COMMANDS ---
# ============================================================
# 1. Check IP address (Mac)
ifconfig en0
# or for newer macOS:
ip addr show en0
# 2. Ping gateway
ping -c 4 192.168.1.1
# 3. Test internet (bypass DNS)
ping -c 4 8.8.8.8
# 4. Test DNS
dig google.com @8.8.8.8
# 5. Renew DHCP lease (Mac - replace en0 with your interface)
sudo ipconfig set en0 DHCP
# 6. Flush DNS cache (macOS Ventura/Sonoma)
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
# 7. Flush DNS cache (macOS Big Sur/Monterey)
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
# 8. Set DNS to Google via networksetup (Mac)
networksetup -setdnsservers Wi-Fi 8.8.8.8 8.8.4.4
# 9. Linux - restart networking
sudo systemctl restart NetworkManager
# 10. Linux - release and renew DHCP
sudo dhclient -r eth0
sudo dhclient eth0
# 11. Linux - flush DNS (systemd-resolved)
sudo systemd-resolve --flush-caches
# ============================================================
# --- ADVANCED: CHECK FOR CAPTIVE PORTAL ---
# ============================================================
# Attempt an HTTP (not HTTPS) request to detect portal redirect
curl -I http://captive.apple.com
curl -I http://neverssl.com
# If you get a 302 redirect to an unknown URL, a captive portal is active
# ============================================================
# --- ROUTER WAN STATUS CHECK (Linux-based routers/SSH) ---
# ============================================================
# Check WAN interface IP
ip addr show eth1
# Check default route
ip route show
# Test from router to internet
ping -c 4 -I eth1 8.8.8.8Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, SREs, and network administrators with over a decade of experience diagnosing connectivity issues across ISPs, enterprise networks, and consumer devices. We specialize in translating complex TCP/IP and DNS troubleshooting into clear, actionable guides for users at every technical level.
Sources
- https://support.microsoft.com/en-us/windows/fix-wi-fi-connection-issues-in-windows-9424a1f7-6a3b-65a6-4d78-7f07eee84d2c
- https://support.apple.com/en-us/HT202222
- https://superuser.com/questions/1420719/connected-to-wifi-but-no-internet-access-169-254-x-x-ip-address
- https://developers.google.com/speed/public-dns/docs/using
- https://www.cloudflare.com/learning/dns/what-is-1.1.1.1/
- https://learn.microsoft.com/en-us/windows-server/networking/technologies/netsh/netsh-contexts
- https://support.google.com/android/answer/9654714