Why does my laptop say 'Connected' but I still can't browse the internet?

Your laptop successfully joined the Wi-Fi network (Layer 2 is working) but cannot route traffic to the internet (Layer 3 is broken). The most common causes are: (1) your IP address is 169.254.x.x, meaning DHCP failed — run 'ipconfig /release' then 'ipconfig /renew'; (2) your DNS server is unreachable — change DNS to 8.8.8.8 in adapter settings; (3) a VPN client is intercepting traffic even when inactive — disconnect or uninstall it. Run 'ping 8.8.8.8' first. If that succeeds but websites fail, the issue is DNS-only.

My T-Mobile Home Internet gateway shows all green lights but I have no internet — what do I do?

Green lights on the T-Mobile gateway indicate the device is powered and has a cellular signal, but they do not guarantee the WAN session is established. Log into the admin UI at 192.168.12.1 and check the Connection Status page. If it shows 'Connecting' indefinitely, try: (1) a soft reboot from the admin UI; (2) a factory reset (10-second button hold); (3) checking the T-Mobile outage map at t-mobile.com/support/account/outage-information. If the gateway is in a low-signal area, the 5G/LTE data session may be registered but too degraded to pass traffic — check the RSRP/RSRQ values in the admin UI; RSRP below -110 dBm will cause reliability issues.

Cox internet shows connected but pages won't load — is it a DNS problem?

Possibly yes. Cox DNS servers (68.105.28.11 and 68.105.29.11) occasionally experience regional outages. To test, run 'nslookup google.com 8.8.8.8' — if this resolves correctly but 'nslookup google.com' fails (using Cox DNS), your ISP's DNS is down. Switch your DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) in your router's DHCP settings so all devices benefit. Also check your modem log at 192.168.100.1 for T3/T4 timeout errors, which indicate a physical signal problem that no DNS change will fix.

How do I fix 'internet connected but no internet' on Frontier fiber when the ONT looks fine?

If the ONT PON light is solid green but you still have no internet, the issue is likely between the ONT and your router or Frontier's network. Check: (1) The Ethernet cable between the ONT and router — replace it to rule out cable faults; (2) Your router's WAN page — if it shows 'No IP Address' or PPPoE 'Disconnected', verify your PPPoE credentials or switch to DHCP if Frontier updated your line to automatic provisioning; (3) Frontier's outage page or the MyFrontier app for active incidents. If your router shows a valid WAN IP but traffic fails, run 'traceroute 8.8.8.8' and share the output with Frontier support — the issue is upstream in their network.

I see 'No Internet, Secured' on Windows 11 — what does that mean and how do I fix it?

'No Internet, Secured' means Windows established an encrypted WPA2/WPA3 association with the access point (hence 'Secured') but failed the NCSI connectivity probe to msftconnecttest.com (hence 'No Internet'). This is almost always a DNS failure, IP routing failure, or a corporate firewall blocking the NCSI endpoint. Fix steps in order: (1) Run 'ipconfig /all' and verify your IP is not 169.254.x.x; (2) Run 'ping 8.8.8.8' — if this succeeds, the problem is DNS; switch to 8.8.8.8; (3) If ping fails, power-cycle your router and modem; (4) If on a corporate network, the NCSI probe may be legitimately blocked — this is a false alarm and your internet actually works. Test by opening a browser.

Internet Connected But No Internet Access: Complete Troubleshooting Guide (Wi-Fi, T-Mobile, Cox, Frontier & More)

Fix 'connected but no internet' errors on any ISP or device. Step-by-step commands and diagnostics for T-Mobile, Cox, Frontier, and laptops.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,833 words

Key Takeaways

Root cause 1: DNS resolution failure — your device is connected to the router but cannot resolve domain names, causing browsers to report 'no internet' even though the physical link is active.
Root cause 2: IP address conflict or DHCP failure — your device received an APIPA address (169.254.x.x) or an incorrect gateway, blocking all outbound traffic.
Root cause 3: ISP-side outage or modem/gateway misconfiguration — the WAN link between your router and the ISP is down, authenticated incorrectly, or throttled; affects T-Mobile Home Internet (gateway firmware), Cox (DOCSIS provisioning), and Frontier (PPPoE/ONT issues).
Quick fix summary: Restart devices in order (modem → router → client), flush DNS cache, release/renew IP, switch to a public DNS (8.8.8.8), and run the diagnostic commands in the code block below to isolate the exact failure layer in under 10 minutes.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle modem + router	First step for any 'connected but no internet' symptom	2–5 min	None — safe for all setups
Flush DNS cache (ipconfig /flushdns or sudo dscacheutil -flushcache)	Browser errors like ERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_NXDOMAIN	30 sec	None
Release and renew IP (ipconfig /release + /renew or dhclient)	Device shows 169.254.x.x (APIPA) or wrong subnet gateway	1–2 min	Temporarily drops network connection
Switch to public DNS (8.8.8.8 / 1.1.1.1)	ISP DNS servers are down or returning SERVFAIL	2 min	Low — may bypass ISP DNS filtering
Reset network stack (netsh int ip reset)	Persistent failures after all other steps, especially post-Windows-update	5 min + reboot	Low — reverses with a reboot if needed
Factory reset gateway / router	Firmware corruption, T-Mobile gateway stuck in provisioning loop	10–20 min	Medium — erases custom settings
Call ISP / check outage map	WAN light is off, modem logs show T3/T4 timeouts (Cox), PPPoE auth failures (Frontier)	Varies	None — escalation only
Reinstall network adapter driver (laptop)	Device Manager shows yellow exclamation on Wi-Fi adapter after update	5–10 min	Low

Understanding the 'Internet Connected But No Internet' Error

When your device reports it is connected to a Wi-Fi network yet cannot load any webpage, you are experiencing a disconnect between Layer 2 connectivity (your device successfully associated with the access point) and Layer 3/7 reachability (actual routable internet traffic). Windows displays this as a yellow exclamation mark on the network icon with the tooltip 'No Internet access'; macOS shows a Wi-Fi symbol with an alert triangle; Android and iOS show 'Connected, no internet' beneath the SSID.

Under the hood, modern operating systems run a Network Connectivity Status Indicator (NCSI) check — they attempt to fetch a known URL (on Windows: http://www.msftconnecttest.com/connecttest.txt; on Android: http://connectivitycheck.gstatic.com/generate_204) and verify the response. If that probe fails for any reason, the OS marks the connection as having no internet, even if some traffic is flowing.

Step 1: Identify the Failure Layer

Before applying any fix, you need to know where the chain is broken. There are four possible failure points:

Client → Router (local LAN issue)
Router → Modem/Gateway (home network misconfiguration)
Modem/Gateway → ISP (WAN/provisioning issue)
ISP → Internet (upstream outage)

Run the diagnostic commands in the Code Block section below to test each layer in sequence. The key commands are:

ping 192.168.1.1 (or your default gateway) — tests Layer 1–2 connectivity to router
ping 8.8.8.8 — tests Layer 3 routing to the internet (bypasses DNS)
nslookup google.com — tests DNS resolution
tracert 8.8.8.8 (Windows) / traceroute 8.8.8.8 (Linux/macOS) — shows where packets stop

Interpreting results:

Gateway ping fails → local LAN problem (IP conflict, wrong gateway, adapter issue)
Gateway ping succeeds, ping 8.8.8.8 fails → router/modem WAN issue or ISP outage
Both pings succeed, nslookup fails → pure DNS failure
Everything succeeds but browser still fails → captive portal, proxy, or NCSI false positive

Step 2: Fix by ISP and Device Type

Universal Fixes (All ISPs, All Devices)

Power-cycle in the correct order:

Unplug your modem (or ISP gateway combo unit) from power.
Unplug your router (if separate).
Wait 60 seconds — this forces DHCP leases to expire and clears ARP caches.
Plug in the modem first. Wait for all lights to stabilize (up to 3 minutes for DOCSIS modems to re-register).
Plug in the router. Wait 60 seconds.
Reconnect your device.

Flush DNS and renew IP (Windows):

ipconfig /flushdns
ipconfig /release
ipconfig /renew

Switch DNS servers: In your network adapter settings, set the Preferred DNS to 8.8.8.8 and Alternate DNS to 1.1.1.1. This is the single fastest fix when the ISP DNS server is down.

T-Mobile Home Internet: Connected But No Internet

T-Mobile Home Internet uses an LTE/5G gateway (Arcadyan KVD21, Nokia FastMile, or Sagemcom RAC2V1S). Common failure modes:

Gateway stuck in provisioning: The gateway's WAN light is solid white/amber but it cannot reach T-Mobile's core network. Fix: hold the reset button for 10 seconds, then allow 5–10 minutes for re-provisioning.
Band steering conflict: The gateway is connected to a congested band. Access the admin UI at 192.168.12.1, disable the 2.4 GHz radio temporarily, and force your client to 5 GHz or the mmWave band.
Firmware update loop: After an automatic firmware push, the gateway may reboot repeatedly. If the POWER light blinks amber for more than 10 minutes, contact T-Mobile support — the unit may need a remote re-flash.
Double NAT: If you have your own router behind the T-Mobile gateway, both devices perform NAT. Put the T-Mobile gateway into IP Passthrough mode (admin UI → Settings → Network) to eliminate the double NAT and resolve connectivity issues caused by conflicting DHCP scopes.

Cox Internet: Connected But No Internet

Cox uses DOCSIS 3.0/3.1 modems. The modem log (accessible at 192.168.100.1 on most ARRIS/Motorola modems) is the most valuable diagnostic tool.

T3/T4 timeout errors in modem log: These indicate the modem cannot maintain a stable upstream channel. Common causes: loose coaxial cable, corroded splitter, or a neighborhood node issue. Check all physical coax connections first.
'Partial Service' mode: The modem registered on some but not all channels. Run ping 8.8.8.8 -t and look for intermittent packet loss. This almost always requires a Cox technician visit.
MAC address not provisioned: If you replaced your modem, Cox must provision the new device's MAC address. Call Cox or use the self-activation portal at activate.cox.net.
Cox DNS outage: Cox has experienced regional DNS outages. Switch to 8.8.8.8 as a workaround and check the Cox outage map at cox.com/residential/support/outages.html.

Frontier Internet: Connected But No Internet

Frontier uses either DSL (PPPoE) or fiber (ONT with GPON). Both have distinct failure modes:

PPPoE authentication failure: The router log will show LCP: timeout sending Config-Requests or PAP authentication failed. Verify your PPPoE username and password in the router's WAN settings. Frontier usernames are typically in the format phonenumber@frontiernet.net.
ONT not passing light: For fiber customers, the ONT (Optical Network Terminal, usually a white box on an exterior wall) has a PON or LOS LED. A red or off LOS light means no optical signal — this requires a Frontier field technician.
IP address not assigned: Frontier's DHCP server may fail to assign an IP during a partial outage. Manually configure a static IP using the last known working lease, or force a DHCP renew every 30 seconds using a cron job until service restores.
Frontier router firmware bug: Certain Frontier-issued Arris NVG routers have a known bug where the WAN interface freezes after 30+ days of uptime. Log into the router at 192.168.254.254, check uptime, and schedule weekly automatic reboots in the router's maintenance settings.

Laptop: Internet Connected But No Internet

Laptop-specific issues often survive a reboot and affect only one device:

Corrupted TCP/IP stack (Windows): Run netsh int ip reset and netsh winsock reset, then reboot. This rewrites core networking registry keys.
VPN client conflict: Many VPN clients (Cisco AnyConnect, GlobalProtect) install virtual adapters that can intercept all traffic even when the VPN is disconnected. Fully uninstall the VPN client to test, or check for a split-tunnel configuration.
Wi-Fi adapter driver issue: After a Windows Update, adapter drivers sometimes roll back or corrupt. Open Device Manager → Network Adapters → right-click your Wi-Fi adapter → Update Driver or Roll Back Driver.
IPv6 misconfiguration: If the router advertises IPv6 but the upstream ISP does not support it, Windows may prefer IPv6 for DNS and fail. Disable IPv6 on the adapter temporarily: netsh interface ipv6 set global randomizeidentifiers=disabled or uncheck IPv6 in adapter properties.
Proxy settings locked: Enterprise laptops or malware may set a system-wide proxy. Check: Settings → Network → Proxy (Windows) or System Preferences → Network → Advanced → Proxies (macOS). Remove any unexpected proxy entries.

Step 3: Verify the Fix

After applying any fix, confirm full connectivity:

ping 8.8.8.8 -c 4 — confirms IP routing
nslookup google.com — confirms DNS
curl -I https://www.google.com — confirms HTTPS end-to-end
Open a browser and load three different HTTPS sites

If all four pass, your connection is fully restored. If only step 1 passes, return to the DNS fix. If none pass, escalate to ISP support with your modem event log and traceroute output ready.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# =============================================================
# Internet Connectivity Diagnostic Script
# Works on: Linux, macOS (bash/zsh)
# For Windows equivalents, see the PowerShell commands below
# =============================================================

echo "========================================="
echo " Internet Connectivity Diagnostic Tool"
echo "========================================="

# --- 1. Show current IP configuration ---
echo ""
echo "[1] Current IP Configuration:"
if command -v ip &>/dev/null; then
  ip addr show | grep -E 'inet |inet6 ' | grep -v 127.0.0.1
else
  ifconfig | grep -E 'inet |inet6 ' | grep -v 127.0.0.1
fi

# --- 2. Identify default gateway ---
echo ""
echo "[2] Default Gateway:"
if command -v ip &>/dev/null; then
  GATEWAY=$(ip route | grep default | awk '{print $3}' | head -1)
else
  GATEWAY=$(route -n get default 2>/dev/null | grep gateway | awk '{print $2}')
fi
echo "Gateway: ${GATEWAY:-NOT FOUND}"

# --- 3. Ping gateway (Layer 2/3 local test) ---
echo ""
echo "[3] Pinging gateway (${GATEWAY}):"
if ping -c 3 -W 2 "$GATEWAY" &>/dev/null; then
  echo "  PASS - Gateway is reachable"
else
  echo "  FAIL - Cannot reach gateway. Check physical connection or DHCP."
fi

# --- 4. Ping Google DNS (Layer 3 internet routing test, bypasses DNS) ---
echo ""
echo "[4] Pinging 8.8.8.8 (internet routing test, no DNS):"
if ping -c 3 -W 3 8.8.8.8 &>/dev/null; then
  echo "  PASS - Internet routing works"
else
  echo "  FAIL - Cannot reach internet. ISP or modem/router WAN issue."
  echo "         Check modem event log and ISP outage map."
fi

# --- 5. DNS resolution test ---
echo ""
echo "[5] DNS Resolution Test:"
if nslookup google.com 8.8.8.8 &>/dev/null; then
  echo "  PASS (via Google DNS 8.8.8.8)"
else
  echo "  FAIL via Google DNS 8.8.8.8 - unexpected"
fi
if nslookup google.com &>/dev/null; then
  echo "  PASS (via system/ISP DNS)"
else
  echo "  FAIL via system DNS - ISP DNS is likely down. Switch to 8.8.8.8"
fi

# --- 6. HTTP connectivity test ---
echo ""
echo "[6] HTTP/HTTPS Connectivity Test:"
curl -o /dev/null -s -w "HTTP Status: %{http_code}  Time: %{time_total}s\n" \
     --max-time 10 https://www.google.com || echo "  FAIL - HTTPS request failed"

# --- 7. Traceroute to first 5 hops ---
echo ""
echo "[7] Traceroute (first 5 hops to 8.8.8.8):"
if command -v traceroute &>/dev/null; then
  traceroute -m 5 8.8.8.8 2>/dev/null
elif command -v tracepath &>/dev/null; then
  tracepath -m 5 8.8.8.8 2>/dev/null
fi

# --- 8. Flush DNS cache (Linux/macOS) ---
echo ""
echo "[8] Flushing DNS Cache:"
if systemctl is-active --quiet systemd-resolved 2>/dev/null; then
  sudo resolvectl flush-caches && echo "  systemd-resolved cache flushed"
elif command -v dscacheutil &>/dev/null; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder \
    && echo "  macOS DNS cache flushed"
else
  echo "  No known DNS cache manager found (nscd/dnsmasq may need manual restart)"
fi

# --- 9. Renew DHCP lease ---
echo ""
echo "[9] Renewing DHCP Lease:"
INTERFACE=$(ip route | grep default | awk '{print $5}' | head -1)
if [ -n "$INTERFACE" ]; then
  if command -v dhclient &>/dev/null; then
    sudo dhclient -r "$INTERFACE" && sudo dhclient "$INTERFACE" \
      && echo "  DHCP lease renewed on $INTERFACE"
  elif command -v dhcpcd &>/dev/null; then
    sudo dhcpcd -n "$INTERFACE" && echo "  dhcpcd renewed on $INTERFACE"
  fi
fi

echo ""
echo "========================================="
echo " Diagnostic Complete"
echo "========================================="

# =============================================================
# WINDOWS POWERSHELL EQUIVALENTS (run as Administrator)
# =============================================================
# ipconfig /all                          # Show IP config
# Test-NetConnection -ComputerName 8.8.8.8 -InformationLevel Detailed
# Resolve-DnsName google.com -Server 8.8.8.8
# ipconfig /flushdns
# ipconfig /release; ipconfig /renew
# tracert 8.8.8.8
# netsh int ip reset                     # Reset TCP/IP stack (requires reboot)
# netsh winsock reset                    # Reset Winsock catalog (requires reboot)
# netsh interface ipv6 set global randomizeidentifiers=disabled  # Disable IPv6 privacy ext
# Get-NetAdapter | Disable-NetAdapter -Confirm:$false; Start-Sleep 5; Get-NetAdapter | Enable-NetAdapter
# =============================================================
# T-MOBILE SPECIFIC: Check admin UI at 192.168.12.1
# COX MODEM LOG:     Check at http://192.168.100.1
# FRONTIER ROUTER:   Check at http://192.168.254.254
# =============================================================

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network administrators with 10+ years of combined experience diagnosing connectivity issues across enterprise, SMB, and residential environments. We specialize in turning cryptic error messages into actionable, step-by-step fixes backed by real commands and official documentation.

Sources

Explore More wifi Guides

"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.

"Connected Without Internet" Error: Complete Fix Guide for WiFi, Routers, Android & ISP Issues

Fix the 'connected without internet' error on WiFi, Android, hotspots & ISPs like Cox, CenturyLink & Fios. Step-by-step commands and solutions inside.

"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.