What does 'Connected without internet' actually mean?

It means your device successfully joined the local WiFi network and received an IP address from the router, but the router or modem cannot reach the public internet. Your OS (Windows, Android, etc.) runs a background connectivity test (pinging Microsoft or Google servers) and displays this warning when the test fails. The device is on your local network but has no path to external websites or services.

How do I fix 'Connected without internet' on my Android phone or mobile hotspot?

First, toggle Airplane Mode on for 30 seconds and back off to force a fresh cellular registration. If that doesn't help, go to Settings → General Management → Reset → Reset Network Settings. For mobile hotspots showing this error, check that your cellular data plan is active and that your APN settings match your carrier's requirements. You can also use ADB to reset captive portal detection: run 'adb shell settings put global captive_portal_detection_enabled 0' from a connected computer.

My Cox/CenturyLink/Fios WiFi says connected without internet — is it an outage?

It could be. First check your ISP's outage page or app. Then look at your modem's WAN/Internet LED — if it's red, off, or blinking abnormally, it's a modem or line issue. Power-cycle the modem (unplug for 60 seconds). If the WAN LED doesn't turn solid green/white after 3-5 minutes, call your ISP. For CenturyLink, PPPoE credentials may need to be re-entered in your router. For Fios, check the ONT fiber terminal's PON light.

Why does my hotspot say 'connected without internet' even though I have signal?

Cell signal and data connectivity are separate. You can have bars (voice signal) but no data if: (1) your data plan is exhausted or throttled to zero, (2) your carrier has a data network outage in your area, (3) your APN settings are misconfigured, or (4) your device failed to authenticate with the carrier's data gateway. Check your data balance in the carrier app, toggle Airplane Mode, and verify APN settings under Settings → Mobile Networks → Access Point Names.

How can I be connected without internet — isn't that a contradiction?

No — 'connected' in this context means connected to the local network (your router's LAN), not to the internet. The internet is a separate system your ISP provides access to. Your router creates a private local network (LAN) that all your devices join via WiFi. The router then connects to the internet via a separate WAN link through your modem and ISP. You can be on the LAN (local network) without the WAN link working — like being inside a building with no exit to the street.

"Connected Without Internet" Error: What It Means and How to Fix It (All Devices & ISPs)

Fix the 'Connected Without Internet' WiFi error on Android, router, hotspot, Cox, CenturyLink, Fios & more. Step-by-step commands and solutions inside.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,385 words

Key Takeaways

Root Cause 1: Your device successfully connected to the router or access point, but the router itself cannot reach the internet — typically due to ISP outage, modem failure, incorrect DNS, or expired DHCP lease.
Root Cause 2: A misconfigured network adapter, corrupted TCP/IP stack, or a captive portal detection failure is causing the OS to falsely report 'no internet' even when connectivity exists (common on Android and Windows).
Root Cause 3: ISP-side issues (Cox, CenturyLink, Frontier, Fios, T-Mobile Home Internet, Converge) including provisioning failures, authentication errors (PPPoE), or line signal degradation prevent the WAN link from establishing.
Quick Fix Summary: Reboot modem → router → device in sequence; flush DNS and renew DHCP; try Google DNS (8.8.8.8); check ISP outage page; reset network settings on Android; or run 'netsh winsock reset' on Windows — most cases resolve in under 10 minutes.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle modem + router	First step for any 'connected without internet' scenario on any ISP	2-5 min	None
Flush DNS + renew DHCP (Windows/Mac)	Device connected but sites won't load; ping to 8.8.8.8 fails or is inconsistent	1-2 min	None
Change DNS to 8.8.8.8 / 1.1.1.1	DNS resolution failing (ping IP works, ping domain fails)	2 min	None
Netsh winsock reset (Windows)	Corrupted TCP/IP stack; other fixes didn't work on Windows	3-5 min + reboot	Low
Reset network settings (Android)	Android phone/tablet shows 'Connected, no internet' persistently	1-2 min, reconnect all WiFi	Low — loses saved WiFi passwords
Disable captive portal detection (Android)	Connected to valid network but Android still shows warning	1 min	Low — suppresses future portal warnings
Factory reset router	All else failed; router firmware corrupted or mis-configured	15-30 min	High — all settings lost
Contact ISP (Cox, CenturyLink, Fios, etc.)	WAN light on modem is off/red; ISP outage confirmed or modem MAC not provisioned	30+ min	None

Understanding the "Connected Without Internet" Error

When your device displays "Connected, no internet" or "Connected without internet," it means the local network handshake succeeded (your device got an IP address from the router), but the router (or modem) cannot reach the public internet. The operating system performs a periodic connectivity check — Windows pings www.msftconnecttest.com, while Android pings Google's servers (connectivitycheck.gstatic.com). If that check fails, the warning appears.

This error is not the same as having no connection at all. Your device is genuinely on the local network; the problem lives upstream.

Step 1: Identify Which Layer Is Broken

Before applying any fix, determine exactly where the break is:

1a. Check your modem's WAN/Internet LED.

Solid green/white = modem has a WAN link (problem is likely DNS, DHCP, or device-side).
Blinking amber, red, or off = modem cannot sync with ISP (line issue, outage, or provisioning problem — call your ISP).

1b. Ping test from a computer on the same network:

ping 8.8.8.8          # Tests raw internet connectivity (bypasses DNS)
ping google.com       # Tests DNS resolution + internet

If ping 8.8.8.8 fails: problem is at the router/modem/ISP layer.
If ping 8.8.8.8 passes but ping google.com fails: DNS is broken.
If both pass but browser shows no internet: captive portal or browser/proxy issue.

1c. Check ISP outage pages:

Cox: https://www.cox.com/residential/support/outage.html
CenturyLink/Lumen: https://www.lumen.com/en-us/outage-center.html
Frontier: https://frontier.com/local/outages
Fios (Verizon): https://www.verizon.com/home/outage/
T-Mobile Home Internet: https://www.t-mobile.com/support/account/outage-information

Step 2: Power-Cycle Your Modem and Router (All ISPs)

This resolves the majority of cases by forcing the modem to re-authenticate with the ISP and the router to renew its WAN IP.

Power off your modem (unplug power cable). If modem and router are separate devices, power off the router too.
Wait 60 seconds — this clears volatile memory and forces the ISP's DHCP server to release the old lease.
Power on the modem first. Wait for all lights to stabilize (≈ 2 minutes).
Power on the router. Wait 1 minute.
Reconnect your device and test.

Step 3: Fix DNS and DHCP on Windows

Open Command Prompt as Administrator and run:

ipconfig /release
ipconfig /flushdns
ipconfig /renew
netsh winsock reset
netsh int ip reset

Reboot after running these commands. These steps:

Release the old DHCP lease and request a new IP.
Clear the local DNS resolver cache.
Reset the Windows Sockets API (fixes corrupted network stacks).
Reset the IP routing table.

Set manual DNS (if auto DNS is failing):

netsh interface ip set dns "Wi-Fi" static 8.8.8.8
netsh interface ip add dns "Wi-Fi" 1.1.1.1 index=2

Replace "Wi-Fi" with your actual adapter name (check with netsh interface show interface).

Step 4: Fix on macOS

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
sudo ipconfig set en0 DHCP

Or go to System Settings → Network → WiFi → Details → Renew DHCP Lease.

To change DNS on macOS:

System Settings → Network → WiFi → Details → DNS
Click (+) and add 8.8.8.8 and 1.1.1.1
Click OK → Apply

Step 5: Fix on Android (Phone, Tablet, Galaxy Tab S6 Lite, Mobile Hotspot)

Android shows "Connected, no internet" for two distinct reasons: A) The network genuinely has no internet (follow Steps 1-4 for the router). B) Android's captive portal detection is failing on a valid network (common with VPNs, private DNS, or corporate networks).

Fix A — Reset Network Settings:

Go to Settings → General Management (or System) → Reset → Reset Network Settings.
Confirm. This re-initializes all WiFi adapters, saved passwords, Bluetooth, and mobile data settings.
Reconnect to your WiFi and test.

Fix B — Disable or change captive portal check (requires ADB or Developer Options): Using ADB from a computer:

adb shell settings put global captive_portal_detection_enabled 0
# OR redirect check to a different server:
adb shell settings put global captive_portal_server connectivitycheck.gstatic.com
adb shell settings put global captive_portal_use_https 1

Or in Developer Options (if available on your Android version): disable "Aggressive Wi-Fi to Cellular handover" which sometimes triggers false no-internet flags.

Fix for Android Mobile Hotspot / T-Mobile Home Internet:

Toggle Airplane Mode on for 30 seconds, then off — forces a fresh registration to the cell tower.
Check APN settings: Settings → Connections → Mobile Networks → Access Point Names. For T-Mobile, default APN is fast.t-mobile.com.
For 5G home internet gateways, ensure the device is placed near a window for optimal signal. Low SINR causes intermittent WAN drops that appear as "connected without internet."

Step 6: ISP-Specific Fixes

Cox / Cox WiFi: Cox modems (Panoramic WiFi) occasionally lose provisioning. Log into the Cox modem admin at 192.168.100.1 — if you see "No Internet" on the status page, reboot modem from admin UI or call Cox (1-800-234-3993) to re-provision the modem MAC.

CenturyLink / Lumen (now Quantum Fiber): CenturyLink uses PPPoE authentication. If the WAN link shows "Disconnected" in the router admin:

Log into router at 192.168.0.1 (or 192.168.1.1).
Navigate to WAN / Internet Settings → PPPoE.
Re-enter your CenturyLink username (format: youruser@centurylink.net) and password.
Save and reconnect.

Frontier / Fios (Verizon): Fios uses a combination of ONT (fiber terminal) and router. Check the ONT device — a solid green "PON" light is required for internet. If it's red or off, the fiber line has a physical issue — call Fios support.

Converge / Bell / ACT: For regional ISPs using GPON (fiber): check the ONU/ONT signal lights. "LOS" (Loss of Signal) red light = fiber break or ISP provisioning issue. Log tickets via the ISP app or call support.

D-Link Router Specific: If using a D-Link router (not provided by ISP): log into 192.168.0.1 → Status → WAN. If WAN IP is 0.0.0.0, try:

Clone your PC's MAC address to the router's WAN interface (some ISPs bind to the first MAC they see).
Go to Setup → Internet Connection Setup → MAC Clone → Clone your PC's MAC → Save.

Step 7: Advanced — Router Firmware and Factory Reset

If all else fails and the router itself is the problem:

Check for firmware updates in the router admin panel (usually under Administration → Firmware Update).
If the router is stuck in a bad state: perform a factory reset by holding the reset button for 10-30 seconds.
Reconfigure your internet connection type (DHCP, PPPoE, Static) as required by your ISP.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# Connected-Without-Internet Diagnostic Script
# Works on Linux/macOS. For Windows, see PowerShell commands below.
# Run as: bash diagnose_no_internet.sh
# ============================================================

echo "=== [1] Local IP & Gateway ==="
if command -v ip &>/dev/null; then
  ip route show default
  ip addr show | grep 'inet '
else
  ifconfig | grep 'inet '
  netstat -rn | grep 'default'
fi

echo ""
echo "=== [2] Ping Default Gateway ==="
GATEWAY=$(ip route show default 2>/dev/null | awk '/default/ {print $3}' | head -1)
if [ -z "$GATEWAY" ]; then
  GATEWAY=$(netstat -rn 2>/dev/null | awk '/default/ {print $2}' | head -1)
fi
echo "Gateway: $GATEWAY"
ping -c 3 "$GATEWAY" 2>/dev/null || echo "FAIL: Cannot reach gateway $GATEWAY"

echo ""
echo "=== [3] Ping Public IP (bypasses DNS) ==="
ping -c 3 8.8.8.8 && echo "PASS: Raw internet reachable" || echo "FAIL: Cannot reach 8.8.8.8 — problem is at router/modem/ISP layer"

echo ""
echo "=== [4] DNS Resolution Test ==="
nslookup google.com 8.8.8.8 && echo "PASS: DNS works via 8.8.8.8" || echo "FAIL: DNS resolution failed"
nslookup google.com && echo "PASS: Default DNS works" || echo "FAIL: Default DNS broken — try manual DNS"

echo ""
echo "=== [5] HTTP Connectivity Check ==="
curl -s --max-time 5 http://connectivitycheck.gstatic.com/generate_204 -o /dev/null -w "%{http_code}" | grep -q 204 && echo "PASS: HTTP internet reachable (204 response)" || echo "FAIL: HTTP connectivity check failed"

echo ""
echo "=== [6] Traceroute to 8.8.8.8 (first 10 hops) ==="
traceroute -m 10 8.8.8.8 2>/dev/null || tracepath -m 10 8.8.8.8 2>/dev/null || echo "traceroute not installed"

echo ""
echo "=== [7] DNS Cache Flush ==="
if [[ "$OSTYPE" == "darwin"* ]]; then
  echo "Flushing macOS DNS cache..."
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder && echo "Done."
elif command -v systemd-resolve &>/dev/null; then
  echo "Flushing systemd-resolved cache..."
  sudo systemd-resolve --flush-caches && echo "Done."
else
  echo "No known DNS cache manager found. Restart networking service manually."
fi

echo ""
echo "=== [8] DHCP Lease Renewal ==="
if command -v dhclient &>/dev/null; then
  IFACE=$(ip route show default 2>/dev/null | awk '/default/ {print $5}' | head -1)
  echo "Releasing and renewing DHCP on $IFACE..."
  sudo dhclient -r "$IFACE" 2>/dev/null
  sudo dhclient "$IFACE" 2>/dev/null
  echo "DHCP renewal attempted on $IFACE"
else
  echo "dhclient not found. Use 'nmcli connection down <name> && nmcli connection up <name>' to renew."
fi

echo ""
echo "============================================================"
echo "Windows PowerShell equivalent commands (run as Administrator):"
echo "ipconfig /release; ipconfig /flushdns; ipconfig /renew"
echo "netsh winsock reset"
echo "netsh int ip reset"
echo "Set-DnsClientServerAddress -InterfaceAlias 'Wi-Fi' -ServerAddresses ('8.8.8.8','1.1.1.1')"
echo "============================================================"

# Android ADB commands (run from connected computer):
# adb shell ping -c 3 8.8.8.8
# adb shell nslookup google.com
# adb shell settings get global captive_portal_detection_enabled
# adb shell settings put global captive_portal_detection_enabled 0
# adb shell settings put global captive_portal_server connectivitycheck.gstatic.com
# adb shell svc wifi disable && sleep 3 && adb shell svc wifi enable

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network specialists with 10+ years of experience diagnosing connectivity issues across enterprise and consumer environments. We've troubleshot WiFi and ISP failures for Fortune 500 companies, cloud infrastructure teams, and everyday users. Our guides are tested on real hardware before publication.

Sources

Explore More wifi Guides

2.4 GHz Not Working But 5 GHz Working on TP-Link (Complete Fix Guide)

Fix TP-Link 2.4 GHz not working while 5 GHz works. Step-by-step guide covering band issues, DNS problems, Chromecast conflicts, and login failures.

2.4 GHz Not Working but 5 GHz Working on TP-Link (Or Vice Versa): Full Troubleshooting Guide

Fix TP-Link 2.4 GHz or 5 GHz band not working. Step-by-step guide covering DNS errors, internet disconnected, Chromecast issues, and login problems.

2.4 GHz Not Working But 5 GHz Working on TP-Link Router (Full Fix Guide)

Fix TP-Link 2.4 GHz not working while 5 GHz works. Step-by-step guide covering band steering, DNS issues, Chromecast problems, and login failures.