Why does my device say 'Connected to Xfinity WiFi but no internet' when other devices work fine?

When only one device shows no internet while others on the same Xfinity network work, the problem is local to that device. The most common causes are: (1) a failed DHCP lease — the device received an APIPA address (169.254.x.x) instead of a valid IP; (2) a corrupted DNS cache; or (3) a corrupted OS network stack. Fix: open a command prompt and run 'ipconfig /release' then 'ipconfig /renew' on Windows, or forget and reconnect to the WiFi network on mobile. Then run 'ipconfig /flushdns'. If those fail, run 'netsh winsock reset' and reboot.

Why is my XfinityWiFi hotspot connected but showing no internet access?

Public XfinityWiFi hotspots (SSIDs: 'xfinitywifi' and 'XFINITY') use a captive portal authentication system. When you first connect, the hotspot blocks all internet traffic until you authenticate via a web login page. If that portal page never appeared, open any HTTP URL (try http://neverssl.com) to trigger the redirect, or navigate directly to http://wifi.xfinity.com. If you are an Xfinity subscriber, hotspot access is included in your plan — sign in with your Xfinity ID. Also disable MAC address randomization for this network, as it can break RADIUS authentication.

My Xfinity modem/gateway light is white but I still have no internet — what does that mean?

A solid white light on an Xfinity xFi Gateway (XB6, XB7, XB8) indicates the modem believes it has internet connectivity, but this is not always accurate during partial outages. Log into http://10.0.0.1 and check the Event Log for T3 or T4 timeout errors, and verify that downstream SNR is above 33 dB and power levels are within spec. Also check https://www.xfinity.com/support/status for area outages. If signal levels look good and no outage is reported, use the Xfinity app to send a refresh signal to your modem, which re-provisions it from the CMTS.

How do I fix 'connected to Xfinity but no internet' after a power outage or storm?

Power outages and storms are the most common cause of sudden Xfinity internet loss. After power is restored: (1) Unplug your Xfinity gateway for 60 seconds, then plug it back in. (2) Wait 5 full minutes for DOCSIS registration to complete. (3) Check gateway signal levels at http://10.0.0.1 — storms often cause physical cable damage or corrosion in connectors that degrades signal. (4) If T3/T4 timeouts appear in the event log or signal levels are out of spec, call Xfinity to report a service issue and request a technician visit. Surge-protect your gateway with a quality UPS to prevent future issues.

Why does Xfinity WiFi say 'no internet' on my phone but work on my laptop?

Device-specific 'no internet' issues on phones commonly stem from: (1) MAC address randomization — modern iOS and Android randomize the WiFi MAC per network, and if your router uses MAC-based DHCP reservations or an older firmware, it may not issue a proper lease to the randomized MAC. Disable private/random WiFi address for your Xfinity network in WiFi settings. (2) IPv6 misconfiguration — some phones prefer IPv6 and if the gateway's IPv6 stack is having issues, connectivity appears broken. Try toggling 'IP settings' to DHCP only in the WiFi advanced settings on Android. (3) A stuck DHCP lease — forget the network and reconnect to force a fresh DHCP request.

Xfinity No Internet Connection: Fix 'Connected But No Internet' on Xfinity WiFi & Hotspots

Fix Xfinity no internet connection errors fast. Step-by-step guide for 'connected to Xfinity but no internet' on home routers and XfinityWiFi hotspots.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,955 words

Key Takeaways

Root cause 1: IP address or DNS misconfiguration — your device is associated with the Xfinity gateway or hotspot but fails to obtain a valid routable IP or receive proper DNS responses, showing 'connected, no internet' in the OS network tray.
Root cause 2: Xfinity gateway or modem signal loss — upstream DOCSIS signal degradation, T3/T4 timeout events, or an uncorrectable downstream channel causes the gateway to lose its WAN connection while LAN clients still show as 'connected'.
Root cause 3: XfinityWiFi hotspot captive portal not completing — public hotspot authentication (RADIUS/802.1X or captive portal redirect) stalls, leaving your device in a partially authenticated state with no routable internet access.
Quick fix summary: Power-cycle your gateway (unplug 60 seconds), release/renew your IP (ipconfig /release && ipconfig /renew on Windows or sudo dhclient -r on Linux/macOS), flush DNS cache, and if on a public XfinityWiFi hotspot, open a browser to trigger the captive portal or disconnect/reconnect your Xfinity account via the Xfinity app.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle modem/gateway	WAN link down, all devices affected, event logs show T3/T4 timeouts	2–5 min	Low — brief outage during reboot
Release & renew IP address	Single device shows 'connected no internet', others work fine, APIPA (169.254.x.x) address assigned	30 sec	Very Low
Flush DNS cache	Sites fail to load but ping by IP succeeds, NXDOMAIN errors in nslookup	10 sec	Very Low
Change DNS servers to 8.8.8.8 / 1.1.1.1	Xfinity DNS servers unresponsive or slow, DNS resolution timeouts	2 min	Low — may bypass Xfinity DNS filtering
Reset network stack (netsh/ip link)	Persistent adapter errors, corrupted TCP/IP stack, driver issues	5 min	Low — requires reboot
Factory reset gateway	Firmware corruption, persistent config issues after all other fixes fail	15–30 min	Medium — erases all custom settings
Captive portal re-authentication (XfinityWiFi hotspot)	Public XfinityWiFi hotspot shows connected but browser requests stall	2 min	Very Low
Call Xfinity support / schedule tech visit	Signal issues confirmed in modem logs, provisioning failure, hardware fault	30–60 min	None

Understanding the 'Xfinity No Internet Connection' Error

When your device reports 'Connected, No Internet' while on Xfinity, the OS (Windows, macOS, Android, iOS) has successfully associated with the WiFi network at Layer 2 (802.11 association and 4-way WPA2/3 handshake) but one or more higher-layer requirements have failed:

DHCP failure: No IP address obtained, or APIPA fallback (169.254.x.x) assigned.
DNS failure: IP obtained but DNS queries return NXDOMAIN or time out.
WAN failure: Gateway has LAN connectivity but its upstream DOCSIS link is down.
Captive portal block: Hotspot is intentionally blocking traffic until authentication completes.
Account/provisioning issue: Xfinity has suspended or not provisioned your modem's MAC address (CM MAC).

Windows detects this via NCSI (Network Connectivity Status Indicator), which sends an HTTP request to http://www.msftncsi.com/ncsi.txt. If that request fails, the yellow exclamation mark appears. macOS uses http://captive.apple.com. Android uses http://connectivitycheck.gstatic.com/generate_204. Understanding which layer is failing is the key to a fast fix.

Step 1: Identify the Scope of the Problem

Is it one device or all devices?

If all devices on your home network show no internet: the problem is upstream — your Xfinity gateway, coax cable signal, or Xfinity's network itself.
If only one device shows no internet while others work: the problem is local to that device (IP config, DNS, network adapter driver, or OS network stack).
If you are on a public XfinityWiFi hotspot: the problem is almost always captive portal authentication or account authentication.

Check your gateway's signal lights:

Xfinity xFi Gateway (XB6, XB7, XB8): A solid white light means normal operation. A red or orange light means no internet. A blinking white light means it is booting up.
Older Xfinity gateways: A solid green power and upstream light with no downstream activity indicates a WAN-side issue.

Step 2: Check the Gateway's Event Log for DOCSIS Errors

Access your gateway's admin UI at http://10.0.0.1 or http://192.168.100.1 (varies by model). Navigate to Status > Event Log.

Look for these critical log entries:

T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx
T4 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx
Started Unicast Maintenance Ranging - No Response received - T3 time-out
Lost MDD Timeout
REG-RSP-MP message not received before expiration of T20 timer

T3 timeouts mean the modem sent ranging requests but received no response from the CMTS (Cable Modem Termination System). T4 timeouts mean the modem lost the station maintenance interval entirely — a more severe signal issue. These almost always indicate a coax cable plant problem (loose splitter, corroded connector, damaged cable) or an Xfinity node issue in your area.

Check downstream channel SNR and power levels under Status > Signal. Acceptable ranges:

Downstream Power Level: -7 dBmV to +7 dBmV (DOCSIS 3.0), -15 dBmV to +15 dBmV (DOCSIS 3.1)
Downstream SNR: ≥ 33 dB (QAM256), ≥ 30 dB (QAM64)
Upstream Power Level: 38 dBmV to 48 dBmV

Values outside these ranges require an Xfinity technician visit.

Step 3: Power-Cycle the Gateway

This is the most effective first fix for a home network-wide outage:

Unplug the power cable from the gateway (do NOT press the reset button — that factory resets).
Wait 60 full seconds to allow capacitors to drain and the CMTS to clear the session.
Plug the power back in.
Wait 3–5 minutes for the full DOCSIS registration and provisioning sequence to complete (D3.0: downstream scan → ranging → DHCP → TFTP config file download → registration).
Watch the gateway lights return to solid white/green.

Step 4: Fix IP Address Issues on a Single Device

If only one device is affected, it almost certainly has an IP configuration problem.

Windows — Check current IP:

Open Command Prompt (Admin) and run ipconfig /all. Look at the IPv4 address for your WiFi adapter. If you see 169.254.x.x, you have an APIPA address — DHCP failed.

Windows — Release and renew:

ipconfig /release
ipconfig /renew

macOS/Linux — Renew DHCP lease:

sudo dhclient -r wlan0   # Linux, replace wlan0 with your interface
sudo dhclient wlan0
# macOS:
sudo ipconfig set en0 DHCP

Android/iOS: Go to WiFi settings → tap the network → Forget → reconnect.

Step 5: Flush DNS Cache and Test Resolution

A stale or corrupted DNS cache can make it appear that the internet is down even when connectivity exists.

Windows:

ipconfig /flushdns
nslookup google.com
ping 8.8.8.8

macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
nslookup google.com

Linux:

sudo systemd-resolve --flush-caches
resolvectl statistics
nslookup google.com 8.8.8.8

If ping 8.8.8.8 succeeds but ping google.com fails, the problem is definitively DNS. Change your DNS servers in your network adapter settings to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).

Step 6: Reset the Windows Network Stack

For persistent Windows issues where the above steps do not resolve the problem:

netsh winsock reset
netsh int ip reset
netsh int ipv6 reset
netsh int tcp reset
ipconfig /flushdns
ipconfig /registerdns

Reboot after running these commands. This resets the Winsock catalog, TCP/IP stack, and IPv6 configuration to defaults.

Step 7: Fix XfinityWiFi Hotspot 'Connected No Internet'

When connected to an XfinityWiFi public hotspot (SSIDs: xfinitywifi or XFINITY) and seeing no internet:

Open a browser and navigate to any HTTP (not HTTPS) URL, e.g., http://neverssl.com. This should trigger a redirect to the Xfinity captive portal login page.
Sign in with your Xfinity credentials (or create a free trial account).
If the portal does not appear, navigate directly to http://wifi.xfinity.com.
If you are an Xfinity Internet subscriber, hotspot access is included — ensure you are logged into the Xfinity WiFi app or your Xfinity account.
Forget the network and reconnect if the portal loop does not resolve. On reconnect, the captive portal redirect should trigger immediately after association.
Check that Private WiFi Address (MAC randomization) is disabled for this network — some hotspot authentication systems tie to MAC and randomization can break re-authentication.

Step 8: Check for Xfinity Service Outages

Before spending more time troubleshooting, verify whether Xfinity is experiencing an outage in your area:

Open the Xfinity app on mobile data (not WiFi) → navigate to Account > Troubleshoot > Check for outages.
Visit https://www.xfinity.com/support/status on a different network.
Check https://downdetector.com/status/xfinity for real-time user reports.

If an outage is confirmed, no local troubleshooting will resolve the issue — wait for Xfinity to restore service.

Step 9: Escalate to Xfinity Support

If all the above steps fail and no outage is reported:

Xfinity app: Chat with an agent and request a modem signal refresh / re-provisioning — this remotely re-sends the DOCSIS configuration file to your modem.
Provide the agent with your T3/T4 timeout counts from the event log.
Request a tech dispatch if signal levels are out of spec — this is often a coax plant issue requiring physical inspection.
Ask about modem replacement if your gateway is older than 5 years.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# Xfinity No Internet Diagnostic & Fix Script
# Compatible with: Linux, macOS (bash)
# Run as root or with sudo
# ============================================================

set -euo pipefail

GREEN='\033[0;32m'
RED='\033[0;31m'
YELLOW='\033[1;33m'
NC='\033[0m'

log_info()  { echo -e "${GREEN}[INFO]${NC}  $*"; }
log_warn()  { echo -e "${YELLOW}[WARN]${NC}  $*"; }
log_error() { echo -e "${RED}[ERROR]${NC} $*"; }

# ---- Detect OS ----
OS="$(uname -s)"
log_info "Detected OS: $OS"

# ---- Step 1: Identify active network interface ----
if [[ "$OS" == "Linux" ]]; then
  IFACE=$(ip route show default 2>/dev/null | awk '/default/ {print $5; exit}')
elif [[ "$OS" == "Darwin" ]]; then
  IFACE=$(route -n get default 2>/dev/null | awk '/interface:/ {print $2}')
fi

if [[ -z "${IFACE:-}" ]]; then
  log_error "No default route found. You may have no network interface active."
else
  log_info "Active interface: $IFACE"
fi

# ---- Step 2: Check current IP address ----
echo ""
log_info "=== Current IP Configuration ==="
if [[ "$OS" == "Linux" ]]; then
  ip addr show "${IFACE}" 2>/dev/null | grep -E 'inet |inet6' || log_warn "No IP addresses assigned to $IFACE"
elif [[ "$OS" == "Darwin" ]]; then
  ifconfig "${IFACE}" 2>/dev/null | grep -E 'inet |inet6' || log_warn "No IP addresses assigned to $IFACE"
fi

# Detect APIPA (169.254.x.x) -- indicates DHCP failure
CURRENT_IP=""
if [[ "$OS" == "Linux" ]]; then
  CURRENT_IP=$(ip addr show "${IFACE}" 2>/dev/null | awk '/inet / {print $2}' | head -1 | cut -d'/' -f1)
elif [[ "$OS" == "Darwin" ]]; then
  CURRENT_IP=$(ifconfig "${IFACE}" 2>/dev/null | awk '/inet / {print $2}' | head -1)
fi

if [[ "${CURRENT_IP}" == 169.254.* ]]; then
  log_error "APIPA address detected ($CURRENT_IP). DHCP lease failed!"
  log_warn "Attempting DHCP renewal..."
  if [[ "$OS" == "Linux" ]]; then
    sudo dhclient -r "${IFACE}" 2>/dev/null && sudo dhclient "${IFACE}" 2>/dev/null
  elif [[ "$OS" == "Darwin" ]]; then
    sudo ipconfig set "${IFACE}" DHCP
  fi
else
  log_info "IP address: $CURRENT_IP (looks valid)"
fi

# ---- Step 3: Test gateway reachability ----
echo ""
log_info "=== Gateway Reachability ==="
if [[ "$OS" == "Linux" ]]; then
  GW=$(ip route show default 2>/dev/null | awk '/default/ {print $3; exit}')
elif [[ "$OS" == "Darwin" ]]; then
  GW=$(netstat -rn 2>/dev/null | awk '/default/ {print $2; exit}')
fi

if [[ -n "${GW:-}" ]]; then
  log_info "Default gateway: $GW"
  if ping -c 3 -W 2 "$GW" &>/dev/null; then
    log_info "Gateway ping: SUCCESS"
  else
    log_error "Gateway ping: FAILED — possible WAN outage or gateway crash. Power-cycle your Xfinity gateway."
  fi
else
  log_error "No default gateway found."
fi

# ---- Step 4: Test DNS resolution ----
echo ""
log_info "=== DNS Resolution Test ==="
DNS_TEST_HOST="google.com"
if nslookup "$DNS_TEST_HOST" &>/dev/null; then
  log_info "DNS resolution for $DNS_TEST_HOST: SUCCESS"
else
  log_error "DNS resolution for $DNS_TEST_HOST: FAILED"
  log_warn "Trying alternate DNS (8.8.8.8)..."
  if nslookup "$DNS_TEST_HOST" 8.8.8.8 &>/dev/null; then
    log_info "Alternate DNS (8.8.8.8) works! Your Xfinity DNS is unresponsive."
    log_warn "Fix: Change DNS servers to 8.8.8.8 and 1.1.1.1 in your network settings."
  else
    log_error "Both primary and alternate DNS failed. Likely a WAN-side outage."
  fi
fi

# ---- Step 5: Test internet connectivity ----
echo ""
log_info "=== Internet Connectivity Test ==="
PING_IPS=("8.8.8.8" "1.1.1.1" "208.67.222.222")
INTERNET_OK=false
for ip in "${PING_IPS[@]}"; do
  if ping -c 2 -W 2 "$ip" &>/dev/null; then
    log_info "Ping to $ip: SUCCESS"
    INTERNET_OK=true
    break
  else
    log_warn "Ping to $ip: FAILED"
  fi
done

if [[ "$INTERNET_OK" == "false" ]]; then
  log_error "No internet connectivity detected. WAN link is likely down."
  log_warn "Actions to take:"
  log_warn "  1. Power-cycle your Xfinity gateway (unplug 60 sec)"
  log_warn "  2. Check http://10.0.0.1 event log for T3/T4 timeouts"
  log_warn "  3. Check https://www.xfinity.com/support/status for outages"
else
  log_info "Internet is reachable by IP."
fi

# ---- Step 6: Flush DNS cache ----
echo ""
log_info "=== Flushing DNS Cache ==="
if [[ "$OS" == "Linux" ]]; then
  if systemctl is-active --quiet systemd-resolved 2>/dev/null; then
    sudo systemd-resolve --flush-caches && log_info "systemd-resolved cache flushed"
  elif command -v nscd &>/dev/null; then
    sudo nscd -i hosts && log_info "nscd cache flushed"
  fi
elif [[ "$OS" == "Darwin" ]]; then
  sudo dscacheutil -flushcache
  sudo killall -HUP mDNSResponder 2>/dev/null
  log_info "macOS DNS cache flushed"
fi

# ---- Step 7: HTTP connectivity check (NCSI-style) ----
echo ""
log_info "=== HTTP Connectivity Check ==="
NCIS_URL="http://www.msftncsi.com/ncsi.txt"
if curl -s --max-time 5 --output /dev/null --write-out "%{http_code}" "$NCIS_URL" | grep -q "200"; then
  log_info "HTTP connectivity to NCSI check URL: SUCCESS"
elif curl -s --max-time 5 -o /dev/null -w "%{http_code}" "http://neverssl.com" | grep -q "200"; then
  log_info "HTTP connectivity (neverssl.com): SUCCESS"
else
  log_error "HTTP check failed. If ping to 8.8.8.8 succeeded but HTTP fails, you may be hitting a captive portal."
  log_warn "If on XfinityWiFi hotspot: open http://wifi.xfinity.com in a browser to authenticate."
fi

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

# ---- Windows commands reference (run in Admin CMD/PowerShell) ----
# ipconfig /release
# ipconfig /renew
# ipconfig /flushdns
# netsh winsock reset
# netsh int ip reset
# netsh int ipv6 reset
# netsh int tcp reset
# nslookup google.com
# nslookup google.com 8.8.8.8
# ping 8.8.8.8
# ping google.com
# tracert 8.8.8.8

Error Medic Editorial

Error Medic's editorial team is composed of senior DevOps engineers, SREs, and network specialists with over 15 years of combined experience troubleshooting ISP connectivity, DOCSIS infrastructure, enterprise networking, and cloud systems. Our guides are grounded in real-world incident response, official vendor documentation, and community-validated fixes. We specialize in making complex networking diagnostics accessible and actionable for both technical and non-technical audiences.

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.