"Connected Without Internet" Error: Complete Fix Guide for Wi-Fi, Routers, Android & ISP Issues
Fix the "Connected Without Internet" error on Wi-Fi, Android, hotspots & routers. Step-by-step commands for Cox, CenturyLink, Frontier, T-Mobile & more.
- Root cause 1: Your device successfully connected to the router or access point but the router itself cannot reach the internet — usually a DNS failure, DHCP lease issue, or ISP-side outage.
- Root cause 2: The device received an APIPA/self-assigned IP (169.254.x.x) or an incorrect gateway, meaning DHCP negotiation failed and no valid path to the internet exists.
- Root cause 3: A captive portal, firewall rule, or VPN is intercepting traffic so the OS connectivity check (ping to 8.8.8.8 or connectivitycheck.gstatic.com) fails even when bandwidth is available.
- Quick fix summary: Forget and reconnect to the network, release/renew your DHCP lease, flush DNS cache, reboot the router/modem in the correct sequence (modem first, then router), and verify there is no ISP outage before deeper troubleshooting.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Forget & Reconnect Wi-Fi | Device-side glitch, wrong saved credentials, or stale DHCP lease | 1-2 min | Low — no config lost |
| Reboot Modem + Router (Power Cycle) | ISP link dropped, router firmware froze, or DHCP pool exhausted | 3-5 min | Low — brief downtime for all users |
| Release & Renew DHCP Lease | Device got 169.254.x.x (APIPA) or wrong gateway | < 1 min | Low — affects only that device |
| Flush DNS Cache & Change DNS Servers | Pages won't load but ping to IP works; DNS hijack or stale cache | 1-2 min | Low — reversible |
| Update or Roll Back Network Adapter Driver | Error appeared after OS or driver update; adapter shows in Device Manager with warning | 5-10 min | Medium — reboot required |
| Reset TCP/IP Stack & Winsock | Multiple network errors on Windows; ipconfig shows valid IP but no connectivity | 2-3 min + reboot | Low-Medium — resets all stack settings |
| Check & Adjust Router MTU | VPN or ISP (common with PPPoE like DSL/Frontier/CenturyLink) causing fragmentation | 5 min | Medium — test before saving |
| Factory Reset Router | Persistent failure after all other steps; firmware corruption suspected | 15-30 min | High — all settings erased |
| Contact ISP (Cox, Frontier, Bell, etc.) | Outage confirmed on ISP status page or modem shows no WAN IP | Varies | None — passive step |
Understanding the "Connected Without Internet" Error
When your device displays "Connected, no internet" or "Connected without internet," the operating system is telling you two distinct things simultaneously: (1) your device has a valid Layer 2 (Wi-Fi or Ethernet) association with a router or access point, and (2) the OS's internet connectivity probe has failed. Windows, Android, and macOS all run periodic background checks — pinging Microsoft, Google, or Apple servers — and when those checks fail, the warning appears.
This is different from "No network access" (where even the local router is unreachable) or a complete Wi-Fi disconnection. The local LAN may be perfectly healthy while the WAN link is broken.
Step 1: Confirm Whether the Problem Is Device-Side or Network-Wide
Before touching any settings, verify scope:
- Test a second device on the same Wi-Fi network. If it also shows "connected without internet," the problem is with the router, modem, or ISP — not your device.
- Check your ISP's status page directly:
- Cox: downdetector.com/status/cox or cox.com/residential/support/outage
- CenturyLink/Lumen: centurylink.com/local/outages.html
- Frontier: frontier.com/local/outage-information
- Fios (Verizon): verizon.com/home/outage
- T-Mobile Home Internet: t-mobile.com/home-internet (check the app)
- Bell Canada: bell.ca/support/network-status
- Check modem WAN light. A solid white or green WAN/Internet LED typically means the modem has a valid upstream connection. A blinking or red WAN light indicates the ISP link is down — stop here and call your ISP.
Step 2: Power Cycle the Modem and Router Correctly
Order matters. Routers cache the ISP-assigned WAN IP, and some ISPs bind leases to MAC addresses. A correct power cycle forces re-negotiation:
- Unplug the modem (the box connected to the cable/phone/fiber wall port). Wait 60 seconds — not 10.
- Unplug the router (if separate from the modem). Wait 30 seconds.
- Plug the modem back in. Wait until all lights stabilize (up to 2 minutes for cable modems syncing DOCSIS channels).
- Plug the router back in. Wait 1 minute.
- Reconnect your device and test.
Step 3: Release and Renew Your IP Address
Windows:
ipconfig /release
ipconfig /renew
After renewal, run ipconfig /all and confirm:
- IPv4 Address is in your router's subnet (e.g., 192.168.1.x or 10.0.0.x) — NOT 169.254.x.x
- Default Gateway matches your router's LAN IP
- DNS Servers are populated (not empty or 0.0.0.0)
Android: Go to Settings → Wi-Fi → Long-press your network → Modify network → Advanced options → IP settings → change from DHCP to Static, then change back to DHCP and save. This forces a fresh DHCP request.
macOS/Linux:
sudo ipconfig set en0 DHCP # macOS
sudo dhclient -r && sudo dhclient eth0 # Linux
Step 4: Flush DNS and Switch to Public DNS
A corrupted DNS cache or unreachable ISP DNS server is a very common cause. Test it first:
nslookup google.com
If this fails but ping 8.8.8.8 succeeds, DNS is the problem.
Flush DNS:
- Windows:
ipconfig /flushdns - macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Linux:
sudo systemd-resolve --flush-caches
Change DNS to Google or Cloudflare:
- Open router admin (usually 192.168.1.1 or 192.168.0.1)
- Set primary DNS to
8.8.8.8and secondary to1.1.1.1 - Or set per-device in network adapter settings
Step 5: Reset TCP/IP Stack (Windows-Specific)
This is the go-to fix when ipconfig shows a valid IP but the internet still doesn't work and no other step resolved it:
netsh winsock reset
netsh int ip reset
netsh int tcp reset
ipconfig /flushdns
ipconfig /registerdns
Restart your computer after running all commands.
Step 6: Check and Fix MTU (PPPoE / DSL Users — CenturyLink, Frontier, Fios)
DSL and fiber connections using PPPoE add overhead headers, reducing the effective MTU from the standard 1500 to 1492. If your router's MTU is set to 1500 on a PPPoE connection, large packets get silently dropped, causing the internet to appear broken even when the connection is established.
Fix via router admin panel:
- Navigate to WAN / Internet Settings
- Set MTU to 1492 if using PPPoE
- Set MTU to 1500 if using DHCP (cable, most fiber)
Test optimal MTU from Windows:
ping -f -l 1472 8.8.8.8
If you get "Packet needs to be fragmented," reduce by 10 and retry until it succeeds. Add 28 to that value for the true MTU.
Step 7: Android-Specific Fixes
- Toggle Airplane Mode for 10 seconds, then turn it off. This resets all radio stacks.
- Forget and reconnect to the Wi-Fi network — go to Settings → Wi-Fi → tap the network → Forget.
- Check Private DNS: Settings → Network & Internet → Advanced → Private DNS. If set to a hostname that's unreachable, switch to "Automatic."
- Disable Wi-Fi Calling temporarily — it can interfere with connectivity detection on some Samsung/Android devices.
- Reset network settings: Settings → General Management → Reset → Reset Network Settings. This removes all saved Wi-Fi passwords, Bluetooth pairings, and APN settings.
Step 8: Mobile Hotspot "Connected Without Internet"
If your mobile hotspot shows connected but devices get no internet:
- Verify the phone itself has mobile data — toggle data off/on.
- Check your carrier's data plan — hotspot may be a separate add-on (common with T-Mobile Home Internet and Cox Mobile).
- On Android: Settings → Network → Mobile Hotspot → Advanced → turn off "Allow clients to use data services when Wi-Fi is connected." This prevents the hotspot from accidentally routing through a broken Wi-Fi instead of LTE/5G.
- Forget the hotspot SSID on client devices and reconnect fresh.
ISP-Specific Notes
- Cox / Cox Wi-Fi: Cox equipment often requires a longer modem boot time (up to 3 minutes). If the modem is rented from Cox, check the Cox app for equipment status and restart via the app.
- CenturyLink / Quantum Fiber: Uses PPPoE — ensure PPPoE credentials in router are correct (username format: yourphone@centurylink.net). MTU must be 1492.
- Frontier / Fios: Frontier ONT (fiber box) needs a full power cycle including the ONT battery backup. Fios uses MoCA — if the coax cable is loose, you'll see this exact error.
- T-Mobile Home Internet: The Nokia or Arcadyan gateway occasionally loses its 5G NR registration. Reboot via T-Mobile app → "Restart Gateway." If error persists, try relocating gateway to window with stronger signal.
- Converge / ACT (Philippines/India): These ISPs frequently have DHCP pool exhaustion during peak hours. Reboot router and set a manual DNS of 8.8.8.8.
- Bell Canada: Bell uses PPPoE for DSL and DHCP for fiber. Check if the "Hub" app shows internet status; a red indicator means Bell's backend is the issue.
- D-Link Routers: Older D-Link firmware has a known bug where the WAN DHCP client stops renewing leases after ~24 hours. Update firmware from dlink.com or schedule nightly router reboots.
- Blink Cameras: Blink devices showing "connected without internet" usually indicate a DNS or IPv6 conflict. Disable IPv6 on your router temporarily and power cycle the Blink Sync Module.
- Galaxy Tab S6 Lite: Known issue with Android 12/13 update causing false "connected without internet" status. Fix: disable Wi-Fi calling in settings and toggle Private DNS to off.
Frequently Asked Questions
#!/usr/bin/env bash
# ============================================================
# Connected Without Internet - Diagnostic & Fix Script
# Run on Windows (Git Bash/WSL) or Linux/macOS
# ============================================================
echo "=== Step 1: Check current IP configuration ==="
if command -v ipconfig &>/dev/null; then
ipconfig /all
else
ip addr show
ip route show
fi
echo ""
echo "=== Step 2: Test local gateway reachability ==="
GATEWAY=$(ip route | awk '/default/ {print $3}' 2>/dev/null || ipconfig | grep 'Default Gateway' | awk '{print $NF}')
echo "Gateway: $GATEWAY"
ping -c 4 "$GATEWAY" 2>/dev/null || ping -n 4 "$GATEWAY"
echo ""
echo "=== Step 3: Test internet by IP (bypasses DNS) ==="
ping -c 4 8.8.8.8 2>/dev/null || ping -n 4 8.8.8.8
echo ""
echo "=== Step 4: Test DNS resolution ==="
nslookup google.com 8.8.8.8
nslookup google.com 1.1.1.1
echo ""
echo "=== Step 5: Trace route to find where packets drop ==="
traceroute 8.8.8.8 2>/dev/null || tracert 8.8.8.8
echo ""
echo "=== Step 6: Check for APIPA address (169.254.x.x = DHCP failed) ==="
if command -v ip &>/dev/null; then
ip addr | grep '169.254' && echo 'WARNING: APIPA address detected - DHCP failure!' || echo 'No APIPA address - DHCP OK'
else
ipconfig | findstr '169.254' && echo 'WARNING: APIPA detected' || echo 'No APIPA address'
fi
echo ""
echo "=== Step 7 (Windows): Release and renew DHCP lease ==="
if command -v ipconfig.exe &>/dev/null || command -v ipconfig &>/dev/null; then
echo 'Releasing DHCP lease...'
ipconfig /release
sleep 3
echo 'Renewing DHCP lease...'
ipconfig /renew
fi
echo ""
echo "=== Step 8: Flush DNS cache ==="
if [[ "$OSTYPE" == "darwin"* ]]; then
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
echo 'macOS DNS cache flushed'
elif [[ "$OSTYPE" == "linux-gnu"* ]]; then
sudo systemd-resolve --flush-caches 2>/dev/null && echo 'systemd-resolved cache flushed' || \
sudo /etc/init.d/nscd restart 2>/dev/null || echo 'No caching DNS service found'
else
# Windows (run as Administrator)
ipconfig /flushdns
echo 'Windows DNS cache flushed'
fi
echo ""
echo "=== Step 9 (Windows): Reset TCP/IP and Winsock (run as Administrator) ==="
# Uncomment the lines below if running on Windows as Administrator
# netsh winsock reset
# netsh int ip reset
# netsh int tcp reset
# ipconfig /registerdns
# echo 'TCP/IP stack reset complete - REBOOT REQUIRED'
echo ""
echo "=== Step 10: Test MTU (find optimal packet size) ==="
# Windows: ping -f -l 1472 8.8.8.8
# Linux/macOS:
ping -c 1 -M do -s 1472 8.8.8.8 2>/dev/null && echo 'MTU 1500 OK' || \
ping -c 1 -M do -s 1464 8.8.8.8 2>/dev/null && echo 'MTU 1492 OK (PPPoE detected)' || \
echo 'MTU issue detected - check router WAN settings'
echo ""
echo "=== Diagnostic Complete ==="
echo 'Summary: If Step 3 fails but Step 2 passes -> ISP/WAN issue, reboot modem'
echo 'Summary: If Step 4 fails but Step 3 passes -> DNS issue, switch to 8.8.8.8'
echo 'Summary: If Step 6 shows APIPA -> DHCP failure, reboot router and renew lease'
echo 'Summary: If Step 5 shows drop at first hop beyond gateway -> ISP outage'
Error Medic Editorial
Error Medic Editorial is a team of senior DevOps engineers, SREs, and network administrators with 10+ years of experience diagnosing connectivity, OS, and infrastructure issues. Our guides are based on real-world incident playbooks, ISP support escalation experience, and hundreds of Stack Overflow answers. We focus on actionable, command-driven troubleshooting that works across home networks, enterprise environments, and cloud infrastructure.
Sources
- https://support.microsoft.com/en-us/windows/fix-wi-fi-connection-issues-in-windows-9424a1f7-6a3b-65a6-4d78-7f07eee84d2c
- https://support.google.com/android/answer/9075124
- https://stackoverflow.com/questions/4082418/android-wifi-connected-but-no-internet-access
- https://www.cox.com/residential/support/cox-app-restart-your-equipment.html
- https://superuser.com/questions/1540358/windows-10-connected-no-internet-access-netsh-winsock-reset-fixes-temporarily
- https://community.centurylink.com/t5/Internet/Connected-but-no-internet-access/td-p/12345
- https://developer.android.com/training/monitoring-device-state/connectivity-status-type