Why does my T-Mobile Home Internet show connected but I get no internet access?

T-Mobile Home Internet gateways (Nokia 5G or Arcadyan KVD21) can assign local IPs via DHCP but lose their WAN routing session. Power-cycle the gateway by unplugging it for 60 seconds. If the WAN IP at 192.168.12.1 shows 0.0.0.0 after restart, try repositioning the gateway for stronger 5G signal and reboot again. If this happens repeatedly, contact T-Mobile support as it may indicate a provisioning issue on their backend.

My Cox internet is connected but nothing loads — what should I check first?

First, check downdetector.com/status/cox on your phone's mobile data to rule out a Cox outage. If no outage, power-cycle your Cox Panoramic modem (unplug 60 seconds). Then navigate to your modem's signal page at 192.168.100.1 and verify upstream/downstream channel bonding and power levels are within spec. If upstream power is out of range, Cox may need to adjust the signal at the tap outside your home. Also confirm your modem's MAC address is registered in your Cox account under 'My Equipment'.

Frontier internet shows connected with no internet — is it my router or the ONT?

Check your Frontier ONT (the white box usually mounted in a closet or outside) and look at its WAN or PON light. A solid green light means the fiber link is healthy and the problem is likely your router. A red, blinking, or off WAN light means the fiber signal is lost and you need to call Frontier for a technician visit. If the ONT lights are normal, log into your router at 192.168.1.1, check the WAN status page for a valid public IP, and power-cycle if it shows 0.0.0.0.

My laptop says 'connected, no internet' but my phone works fine on the same Wi-Fi — what's wrong?

This is almost certainly a device-specific issue, not the router or ISP. On Windows, open Command Prompt as administrator and run: ipconfig /flushdns, then netsh winsock reset, then netsh int ip reset, and reboot. Also check Device Manager for your wireless adapter — disable and re-enable it. A VPN client, antivirus firewall, or a corrupted Windows network profile can cause this. Try creating a new network profile: forget the Wi-Fi network and reconnect with your password.

How do I fix the 'No Internet, Secured' error on Windows 10 or Windows 11?

'No Internet, Secured' means Windows can associate with the Wi-Fi network (WPA2/WPA3 handshake succeeded) but the NCSI (Network Connectivity Status Indicator) probe to Microsoft's connectivity check servers is failing. This can be caused by ISP blocking, DNS failure, or firewall rules. Run: ping 8.8.8.8 to test routing, then ipconfig /flushdns, then netsh winsock reset. If on a corporate network or VPN, the VPN split-tunnel policy may be blocking Microsoft's connectivity probe (connectivitycheck.microsoft.com). Disable the VPN and test.

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

Fix 'connected but no internet' on any device or ISP. Step-by-step DNS flush, gateway reset, and adapter fixes for T-Mobile, Cox, Frontier, and laptops.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,322 words

Key Takeaways

Root cause 1: Your device shows a valid IP and Wi-Fi signal, but DNS resolution is failing — meaning the network stack is connected locally, but cannot translate domain names to IP addresses, so no web traffic flows.
Root cause 2: The gateway or modem/router has a stale ARP cache, NAT table overflow, or firmware hang — especially common on T-Mobile Home Internet (Nokia/Arcadyan gateways), Cox Panoramic modems, and Frontier ONT/routers — causing IP assignment to succeed but upstream routing to silently drop packets.
Root cause 3: A misconfigured network adapter on Windows or macOS (invalid metric, duplicate IP, or disabled IPv6 fallback) causes the OS to believe it is connected while all outbound traffic is blackholed.
Quick fix summary: Power-cycle your gateway (unplug 60 seconds), flush DNS cache on your device, release/renew DHCP lease, and verify DNS servers are reachable. For ISP-specific issues, check for outages before deeper troubleshooting.

Fix Approaches Compared
Method	When to Use	Time	Risk
Gateway power-cycle (unplug 60s)	First step for any ISP — T-Mobile, Cox, Frontier	2 min	None
DNS flush + reset (ipconfig /flushdns)	Browser errors: ERR_NAME_NOT_RESOLVED, DNS_PROBE_FINISHED_NXDOMAIN	1 min	None
DHCP release/renew (ipconfig /release + /renew)	169.254.x.x self-assigned IP or wrong subnet	1 min	Temporary disconnection
Change DNS to 8.8.8.8 / 1.1.1.1	ISP DNS is slow or returning NXDOMAIN for valid domains	2 min	None
Winsock/TCP stack reset (netsh int ip reset)	Persistent failure after DNS fix — Windows only	3 min + reboot	Low — resets TCP config
Network adapter disable/re-enable	Laptop shows connected with exclamation mark (no internet)	1 min	None
Factory reset router/gateway	All above failed; gateway in bad state	15 min	Medium — loses custom config
ISP modem replacement or ONT swap	Frontier ONT or Cox modem hardware failure confirmed	1–3 days	Requires ISP coordination

Understanding the 'Connected But No Internet' Error

When your device shows a Wi-Fi or Ethernet connection with full bars but no web pages load, you are experiencing a split between Layer 2/3 connectivity (you have a local network link) and Layer 4–7 reachability (you cannot route packets to the public internet). The OS confirms a physical link and a valid IP address, but something upstream is broken.

On Windows, you will see the yellow exclamation icon on the network tray with the message 'No Internet access' or 'No network access'. Browsers display errors like ERR_NAME_NOT_RESOLVED, DNS_PROBE_FINISHED_NO_INTERNET, or ERR_INTERNET_DISCONNECTED. On macOS, Safari shows 'Safari Can't Connect to the Internet' and the network preference pane shows a green dot (connected) while ping to 8.8.8.8 fails.

Phase 1: Identify the Failure Layer

Before touching any settings, run the following diagnostic sequence to pinpoint exactly where the break occurs.

Step 1.1 — Check your assigned IP address

Open a terminal or Command Prompt and run ipconfig (Windows) or ifconfig / ip addr (Linux/macOS). Look for the IP address of your wireless or Ethernet adapter:

169.254.x.x — APIPA self-assigned address. Your device never received a DHCP lease. The router/gateway is not responding to DHCP requests.
192.168.x.x or 10.x.x.x — Valid private IP. DHCP succeeded. The problem is upstream (DNS, NAT, WAN link).
No IP / disconnected — Physical or driver-level failure.

Step 1.2 — Ping the default gateway

Run ping 192.168.1.1 (or whatever your gateway IP is from ipconfig). If this fails, the problem is between your device and the router. If it succeeds, the local link is healthy.

Step 1.3 — Ping a public IP (bypass DNS)

Run ping 8.8.8.8. If the gateway ping succeeded but this fails, the router is not forwarding traffic to the WAN — NAT or WAN link issue. If this succeeds but websites don't load, the problem is DNS-only.

Step 1.4 — Test DNS resolution

Run nslookup google.com 8.8.8.8. If this returns an IP address, your ISP's DNS is the culprit. If it fails, you have a broader routing problem.

Phase 2: Fix by Root Cause

Fix A: DNS Failure

If ping 8.8.8.8 works but ping google.com fails, your DNS is broken.

Flush DNS cache: Run ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS, or sudo systemd-resolve --flush-caches on Linux.
Change DNS servers: In your network adapter settings (Windows) or System Preferences > Network (macOS), set primary DNS to 1.1.1.1 (Cloudflare) and secondary to 8.8.8.8 (Google).
Disable DNS-over-HTTPS temporarily in Firefox or Chrome flags to rule out browser-level DNS conflicts.

Fix B: DHCP / IP Address Failure (169.254.x.x)

Release and renew your IP: Run ipconfig /release then ipconfig /renew on Windows.
If the problem persists, power-cycle your modem and router. Unplug power for 60 seconds, plug the modem in first, wait 2 minutes, then plug in the router.
On Linux: sudo dhclient -r && sudo dhclient

Fix C: Gateway / WAN Link Failure

If you can ping the gateway but not 8.8.8.8, the router's WAN side is broken.

Power-cycle the gateway — for T-Mobile Home Internet (Nokia 5G Gateway or Arcadyan KVD21), hold the reset button for 5 seconds (soft reset, not factory reset) or unplug for 60 seconds.
Check for ISP outages: Visit downdetector.com/status/t-mobile, downdetector.com/status/cox, or downdetector.com/status/frontier from your mobile data.
Log into the router admin panel (usually 192.168.1.1 or 192.168.0.1) and check the WAN status page. Look for 'WAN IP: 0.0.0.0' or 'No WAN connection' which indicates the ISP is not provisioning an upstream IP.
For Cox: Check that your modem's MAC address is registered in your Cox account. Cox Panoramic modems sometimes lose provisioning after a firmware update.
For Frontier: Check the ONT (Optical Network Terminal) LED status — a solid green WAN light is required. A flashing or red WAN light indicates a fiber signal issue requiring a technician.

Fix D: Windows TCP Stack Corruption

If all pings succeed but browsers and apps still cannot reach the internet:

Reset Winsock: netsh winsock reset
Reset TCP/IP stack: netsh int ip reset
Reset IPv4 and IPv6: netsh int ipv4 reset and netsh int ipv6 reset
Reboot after all resets.

Fix E: Laptop-Specific — Network Adapter Issues

On laptops, the wireless adapter driver can enter a bad state especially after sleep/wake cycles:

Open Device Manager > Network Adapters, right-click your Wi-Fi adapter, and select Disable device, wait 5 seconds, then Enable device.
Update the driver: Right-click the adapter > Update driver > Search automatically.
Check the power management setting: Right-click adapter > Properties > Power Management > uncheck 'Allow the computer to turn off this device to save power'.
On Windows 11, check that Network Reset has not cleared your DNS settings: Settings > Network & Internet > Advanced network settings > Network reset.

ISP-Specific Notes

T-Mobile Home Internet: The 5G gateway (Nokia or Arcadyan) performs NAT and sometimes enters a state where it assigns DHCP leases but stops routing WAN traffic. The fix is almost always a 60-second power cycle. If the problem recurs, log into 192.168.12.1 and check the WAN IP — if it shows 0.0.0.0, T-Mobile's 5G cell is not registering the device. Try moving the gateway near a window for better signal.

Cox Internet: Cox uses DOCSIS 3.0/3.1. After outages or rolling firmware updates, the modem can fail to re-register on the cable plant. The modem's signal page (usually at 192.168.100.1) will show upstream power levels — if they are above +50 dBmV or below +38 dBmV, call Cox for a line check.

Frontier Internet: Frontier FiOS and fiber customers have an ONT that bridges fiber to Ethernet. The ONT's WAN light must be solid green. If the ONT light is red or off, the issue is outside your home and requires a Frontier technician. Frontier DSL customers should check line sync status at the modem admin panel.

Laptops (all ISPs): Laptop-specific issues almost always come down to driver state after sleep, VPN client conflicts, or antivirus/firewall software blocking the network stack. Disable your VPN and antivirus temporarily to test.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# =============================================================
# Internet Connectivity Diagnostic Script
# Works on Linux and macOS; Windows equivalents commented below
# =============================================================

echo "===== STEP 1: Check assigned IP address ====="
if command -v ip &>/dev/null; then
  ip addr show | grep -E 'inet |inet6 '
else
  ifconfig | grep -E 'inet |inet6 '
fi
# Windows equivalent: ipconfig /all

echo ""
echo "===== STEP 2: Identify default gateway ====="
if command -v ip &>/dev/null; then
  GATEWAY=$(ip route | grep default | awk '{print $3}' | head -1)
else
  GATEWAY=$(netstat -rn | grep default | awk '{print $2}' | head -1)
fi
echo "Default gateway: $GATEWAY"
# Windows equivalent: ipconfig /all | findstr 'Default Gateway'

echo ""
echo "===== STEP 3: Ping gateway (Layer 3 local link test) ====="
ping -c 3 "$GATEWAY"
# Windows: ping -n 3 <gateway_ip>

echo ""
echo "===== STEP 4: Ping public IP (bypasses DNS) ====="
ping -c 3 8.8.8.8
# Windows: ping -n 3 8.8.8.8

echo ""
echo "===== STEP 5: DNS resolution test ====="
nslookup google.com 8.8.8.8
# Windows: nslookup google.com 8.8.8.8

echo ""
echo "===== STEP 6: Traceroute to identify hop where packets drop ====="
if command -v traceroute &>/dev/null; then
  traceroute -m 15 8.8.8.8
else
  traceroute 8.8.8.8
fi
# Windows: tracert 8.8.8.8

echo ""
echo "===== STEP 7: Check current DNS servers ====="
if [ -f /etc/resolv.conf ]; then
  cat /etc/resolv.conf
fi
# Windows: ipconfig /all | findstr 'DNS Servers'

echo ""
echo "===== STEP 8: Flush DNS cache ====="
if command -v systemd-resolve &>/dev/null; then
  sudo systemd-resolve --flush-caches && echo "systemd DNS cache flushed"
elif [[ "$OSTYPE" == "darwin"* ]]; then
  sudo dscacheutil -flushcache
  sudo killall -HUP mDNSResponder
  echo "macOS DNS cache flushed"
fi
# Windows CMD (run as Administrator):
#   ipconfig /flushdns

echo ""
echo "===== STEP 9: Release and renew DHCP lease ====="
# Linux:
# sudo dhclient -r eth0 && sudo dhclient eth0
# sudo dhclient -r wlan0 && sudo dhclient wlan0
# macOS: Use System Preferences > Network > Renew DHCP Lease
# Windows CMD (run as Administrator):
#   ipconfig /release
#   ipconfig /renew

echo ""
echo "===== STEP 10: Windows TCP stack reset (run in elevated CMD) ====="
echo "# netsh winsock reset"
echo "# netsh int ip reset"
echo "# netsh int ipv4 reset"
echo "# netsh int ipv6 reset"
echo "# Reboot after running all four commands"

echo ""
echo "===== STEP 11: Test alternate DNS (change to Cloudflare/Google) ====="
echo "Temporary DNS override test:"
nslookup google.com 1.1.1.1
nslookup google.com 8.8.8.8
# If these succeed but your normal DNS fails, change your adapter's DNS
# Windows: ncpa.cpl > Adapter Properties > IPv4 Properties > Use the following DNS
# Set preferred: 1.1.1.1  alternate: 8.8.8.8

echo ""
echo "===== Diagnostic complete. Review output above for failure point. ====="

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and network administrators with combined experience spanning cloud infrastructure, ISP-level networking, and end-user device troubleshooting. We specialize in translating complex system failures into clear, actionable fixes for both technical and non-technical audiences. Our guides are tested against real-world environments including enterprise networks, residential ISP setups, and cloud platforms.

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.