Why does my device say 'Connected' to Xfinity WiFi but there is no internet access?

This happens when your device successfully completes the WiFi handshake (WPA2/WPA3 authentication) with the Xfinity gateway but fails at a higher network layer. Common causes include: (1) DHCP failure — your device got a 169.254.x.x self-assigned address instead of a real gateway IP; (2) WAN-side failure — the modem hasn't completed DOCSIS provisioning so there is no upstream internet route; (3) DNS failure — domain names cannot be resolved even though the physical connection works. Start with a 60-second modem power-cycle, then run `ipconfig /all` (Windows) or `ifconfig` (macOS/Linux) to check your IP address.

Why am I connected to the XfinityWiFi hotspot but have no internet?

Public XfinityWiFi hotspots require you to authenticate through a captive portal web page before traffic is routed to the internet. If that redirect fails silently, your device shows 'connected' but all traffic is blocked. Fix: open a browser and navigate to `http://xfinitywifi.com` (use HTTP not HTTPS). If that does not load, try `http://1.1.1.1`. Also disable any active VPN, DNS-over-HTTPS settings, or Private WiFi MAC address randomization before connecting, as these can break captive portal detection on iOS, Android, Windows, and macOS.

My Xfinity modem's Online light is solid but I still have no internet — what's wrong?

A solid Online light confirms the modem has completed DOCSIS provisioning and has a WAN connection. If you still have no internet, the problem is likely on the router or device side: (1) Check if your router's WAN port received an IP from the modem (`ipconfig` on a device directly wired to the modem to rule out the router). (2) Check for a DNS outage — run `nslookup google.com 8.8.8.8` to test with Google's DNS directly. (3) Check for an IP conflict — run `arp -a` to see if two devices share an IP. (4) Reboot your router (separate from the modem) if you have one.

Xfinity WiFi says 'No Internet, Secured' on Windows — how do I fix it?

The 'No Internet, Secured' message in Windows 10/11 means WPA2 authentication succeeded (hence 'Secured') but Windows Network Connectivity Status Indicator (NCSI) could not reach Microsoft's connectivity check endpoint (`http://www.msftconnecttest.com/connecttest.txt`). This can mean actual internet loss OR a firewall/DNS issue blocking only Microsoft's test URL. Steps: (1) Run `ping 8.8.8.8` in Command Prompt. If it replies, your internet is working and you need to allow NCSI through your firewall or re-enable it via Group Policy. (2) If ping fails, run `ipconfig /release && ipconfig /renew` and reboot the modem. (3) Run `netsh winsock reset` and restart Windows to clear corrupted network stack state.

How long does Xfinity modem rebooting take and what lights should I see?

A full Xfinity modem/gateway cold boot takes between 2 and 5 minutes. Light sequence: Power light comes on immediately. DS (Downstream) light blinks during channel scanning, then goes solid when it locks onto the downstream DOCSIS channel (30–90 seconds). US (Upstream) light blinks during ranging, then goes solid. Online/Internet light blinks during DOCSIS provisioning and CM registration, then goes solid green when internet access is established. If the Online light never goes solid (stays blinking for more than 10 minutes), the modem is failing provisioning — try the Xfinity app's remote restart, check for local outages, or call support.

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

Fix Xfinity no internet connection fast. Step-by-step guide covering modem resets, DNS fixes, IP conflicts, and hotspot issues. Restore access in minutes.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,637 words

Key Takeaways

Root cause 1: IP address conflict or DHCP lease failure — your device connects to the Xfinity gateway but never receives a valid routable IP address, leaving you in a 'connected but no internet' state.
Root cause 2: DNS resolution failure — the gateway is online but the DNS servers assigned by Xfinity are unreachable or returning errors, so domain names cannot be resolved even though the physical connection is active.
Root cause 3: Xfinity modem/gateway firmware or provisioning issue — the cable modem has not completed its downstream channel bonding or DOCSIS provisioning sequence, resulting in a WAN-side link with no internet routing.
Root cause 4: XfinityWiFi hotspot captive portal not completing authentication — when connecting to a public XfinityWiFi hotspot, the captive portal redirect fails silently, leaving the device 'connected' with no routable traffic.
Quick fix summary: Power-cycle the modem/gateway (unplug 60 seconds), release and renew DHCP on your device, switch DNS to 8.8.8.8, and if on a hotspot manually navigate to xfinitywifi.com to trigger the captive portal.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle modem/gateway (unplug 60 sec)	Modem lights abnormal; all devices affected; WAN light off or blinking	2–5 min	Low — no data loss
Release & renew DHCP on client device	Single device affected; 169.254.x.x or 0.0.0.0 IP assigned	< 1 min	Low — reconnects automatically
Flush DNS cache & switch to public DNS (8.8.8.8)	Connected but can't load websites; ping by IP works but hostnames fail	< 1 min	Low — easily reversible
Factory reset Xfinity gateway (reset button 30 sec)	Gateway web UI unreachable; persistent provisioning failure after modem restart	10–20 min	Medium — loses custom WiFi/password settings
Xfinity hotspot captive portal manual trigger	Connected to XfinityWiFi SSID; browser shows 'no internet' or timeout	< 2 min	None
Re-provision modem via Xfinity app or My Account	Modem recently moved, replaced, or shows offline in Xfinity portal	5–10 min	Low
Check & resolve IP address conflict (static IP clash)	Intermittent drops; other devices fine; ARP shows duplicate MAC	5 min	Low
Contact Xfinity support / check outage map	All methods fail; neighborhood-wide issue; CM status shows T3/T4 timeout	Varies	None — escalation only

Understanding 'Xfinity No Internet Connection'

The error message 'No Internet Connection' or 'Connected, no Internet' appears in Windows, macOS, iOS, and Android when a device successfully associates with the WiFi network at Layer 2 (data link) but fails to establish routable connectivity at Layer 3 (network/internet). On Xfinity networks — whether your home gateway or a public XfinityWiFi hotspot — this is one of the most frequently reported issues and has several distinct root causes.

Understanding the OSI layer where the failure occurs is the key to choosing the right fix quickly.

Step 1: Identify the Scope of the Problem

Before touching any settings, answer these diagnostic questions:

1a. Is the problem affecting all devices or just one?

All devices → the issue is almost certainly the modem, gateway, or Xfinity's upstream network.
One device → the issue is device-specific (DHCP, DNS, IP conflict, or driver).

1b. What IP address does the affected device have? On Windows: ipconfig /all On macOS/Linux: ip addr or ifconfig

169.254.x.x (APIPA) → DHCP lease failed entirely. The device gave up waiting for the gateway and self-assigned a link-local address. Fix: restart the DHCP client or power-cycle the gateway.
192.168.x.x or 10.x.x.x → Valid RFC1918 address obtained. The problem is WAN-side or DNS.
0.0.0.0 → DHCP negotiation stuck mid-way.

1c. Can you ping the gateway?

ping 192.168.1.1

Gateway responds → LAN is healthy; WAN or DNS is the problem.
Gateway does not respond → LAN connectivity broken; check WiFi association, gateway reboot needed.

1d. Can you ping an external IP without using a hostname?

ping 8.8.8.8

Responds → DNS is broken, not internet. Fix: change DNS servers.
Does not respond → WAN routing is broken. Fix: reboot modem or contact Xfinity.

Step 2: Fix #1 — Power-Cycle the Xfinity Modem/Gateway

This is the correct first action when all devices show no internet.

Unplug the power cable from the back of the Xfinity modem or gateway (xFi gateway, Arris, Netgear CM, etc.).
If you have a separate router connected to the modem, unplug that too.
Wait a full 60 seconds. This forces the DOCSIS downstream scan to restart and clears stale DHCP bindings.
Plug the modem back in first. Watch the front panel lights:
- Power → solid
- DS (Downstream) → solid (channel lock acquired)
- US (Upstream) → solid
- Online/Internet → solid (provisioning complete) This process takes 2–4 minutes. Do not proceed until the Online light is solid.
Plug the router back in (if separate), wait 30 seconds, then reconnect devices.

What you might see in the modem event log (accessible at 192.168.100.1): T3 Timeout, T4 Timeout, 16 consecutive T3 timeouts, No Ranging Response received These are DOCSIS upstream ranging errors indicating the modem cannot lock onto Xfinity's CMTS. A full reboot usually resolves transient T3/T4 timeouts.

Step 3: Fix #2 — Release and Renew DHCP on the Client Device

When a single device shows 'connected but no internet' and has a 169.254.x.x address:

Windows:

ipconfig /release
ipconfig /renew

macOS: System Preferences → Network → Wi-Fi → Advanced → TCP/IP → Renew DHCP Lease

Linux:

sudo dhclient -r wlan0
sudo dhclient wlan0

Android/iOS: Toggle WiFi off and back on, or forget the network and reconnect.

Step 4: Fix #3 — Flush DNS Cache and Switch DNS Servers

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

Flush DNS cache:

Windows:

ipconfig /flushdns

macOS (Monterey/Ventura/Sonoma):

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux (systemd-resolved):

sudo systemd-resolve --flush-caches

Change DNS servers to bypass Xfinity DNS:

Windows (PowerShell, replace 'Wi-Fi' with your adapter name):

Set-DnsClientServerAddress -InterfaceAlias 'Wi-Fi' -ServerAddresses ('8.8.8.8','8.8.4.4')

macOS: System Preferences → Network → Wi-Fi → Advanced → DNS → add 8.8.8.8 and 1.1.1.1

Linux:

echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf

Step 5: Fix #4 — XfinityWiFi Hotspot Captive Portal Not Triggering

Public XfinityWiFi SSIDs (xfinitywifi, XFINITY, CableWiFi) use a WISPr-style captive portal. When your device connects, it should automatically be redirected to a sign-in page. If this redirect fails:

Connect to the xfinitywifi SSID.
Open a browser and manually navigate to http://xfinitywifi.com (use HTTP, not HTTPS, to trigger redirect).
Sign in with your Xfinity credentials or choose 'Get Pass' for a free session.
If the page does not load, try http://1.1.1.1 — this often triggers the captive portal intercept.
Disable any VPN or DNS-over-HTTPS (DoH) on your device before connecting — these interfere with captive portal detection.
On iOS: Settings → Wi-Fi → tap the info icon next to xfinitywifi → ensure 'Private Wi-Fi Address' is toggled appropriately (some hotspots reject randomized MACs).

Step 6: Fix #5 — Re-provision the Modem via Xfinity App

If the modem completed its reboot but the Online light never goes solid, re-provisioning is needed:

Open the Xfinity app (iOS or Android) and log in.
Navigate to Internet → Troubleshoot.
Select Restart Modem from the app — this triggers a remote re-provision from Xfinity's CMTS, which differs from simply unplugging.
Alternatively, visit my.xfinity.com → Internet → Devices → select your modem → Restart.
If the modem still shows offline after 10 minutes, call 1-800-XFINITY (1-800-934-6489) and request a remote signal refresh.

Step 7: Factory Reset the Gateway (Last Resort)

If all else fails and the gateway web UI at 10.0.0.1 or 192.168.1.1 is unreachable:

Locate the Reset pinhole on the back of the gateway.
With the gateway powered on, press and hold the reset button for 30 seconds using a paperclip.
Release. The gateway will reboot (2–4 minutes).
Reconnect using the default WiFi name and password printed on the gateway label.
Re-run Xfinity setup via the app or xfinity.com/activate.

Warning: This erases all custom settings including WiFi SSID, password, port forwarding rules, and parental controls.

Step 8: Check for a Service Outage

If nothing works:

Visit statuspage.xfinity.com or the Xfinity Status Center in the app.
Check downdetector.com/status/xfinity for user-reported outages in your area.
Log into my.xfinity.com — if your account shows an active outage in your service area, no local troubleshooting will help. Wait for Xfinity to restore service.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# Xfinity No Internet Diagnostic Script
# Works on macOS and Linux. Run with: bash xfinity_diag.sh
# ============================================================

GATEWAY="192.168.1.1"   # Change to 10.0.0.1 for xFi gateways
DNS_TEST_HOST="google.com"
PUBLIC_IP_TEST="8.8.8.8"

echo "=== Xfinity Internet Diagnostic Tool ==="
echo ""

# --- 1. Show current IP configuration ---
echo "[1] Network Interface Configuration:"
if command -v ip &>/dev/null; then
  ip addr show | grep -E 'inet |^[0-9]+:'
else
  ifconfig | grep -E 'inet |flags'
fi
echo ""

# --- 2. Detect APIPA (DHCP failure indicator) ---
echo "[2] Checking for APIPA address (169.254.x.x = DHCP failure):"
if ip addr 2>/dev/null | grep -q '169.254' || ifconfig 2>/dev/null | grep -q '169.254'; then
  echo "  WARNING: APIPA address detected! DHCP lease failed."
  echo "  Fix: sudo dhclient -r && sudo dhclient  (Linux)"
  echo "  Fix: Renew DHCP Lease in Network Preferences  (macOS)"
else
  echo "  OK: No APIPA address detected."
fi
echo ""

# --- 3. Ping the default gateway ---
echo "[3] Pinging gateway ($GATEWAY):"
if ping -c 3 -W 2 "$GATEWAY" &>/dev/null; then
  echo "  OK: Gateway is reachable. LAN connectivity is healthy."
else
  echo "  FAIL: Cannot reach gateway $GATEWAY"
  echo "  Fix: Check gateway address with 'ip route | grep default', reboot modem."
fi
echo ""

# --- 4. Ping external IP (tests WAN routing, bypasses DNS) ---
echo "[4] Pinging external IP $PUBLIC_IP_TEST (tests WAN, bypasses DNS):"
if ping -c 3 -W 3 "$PUBLIC_IP_TEST" &>/dev/null; then
  echo "  OK: WAN routing is working."
else
  echo "  FAIL: Cannot reach $PUBLIC_IP_TEST"
  echo "  Fix: WAN-side issue. Reboot modem. Check Xfinity outage map."
fi
echo ""

# --- 5. DNS resolution test ---
echo "[5] Testing DNS resolution for $DNS_TEST_HOST:"
if nslookup "$DNS_TEST_HOST" &>/dev/null; then
  echo "  OK: Default DNS is resolving hostnames."
else
  echo "  FAIL: Default DNS cannot resolve $DNS_TEST_HOST"
  echo "  Testing with Google DNS (8.8.8.8)..."
  if nslookup "$DNS_TEST_HOST" 8.8.8.8 &>/dev/null; then
    echo "  OK: Google DNS works. Xfinity DNS is the problem."
    echo "  Fix: Change DNS to 8.8.8.8 in network settings."
  else
    echo "  FAIL: Even Google DNS fails. WAN routing is down."
  fi
fi
echo ""

# --- 6. Check default route ---
echo "[6] Default route:"
if command -v ip &>/dev/null; then
  ip route | grep default || echo "  WARNING: No default route found!"
else
  netstat -rn | grep default || echo "  WARNING: No default route found!"
fi
echo ""

# --- 7. Check for IP conflicts via ARP ---
echo "[7] ARP table (check for duplicate IPs):"
arp -a 2>/dev/null | head -20
echo ""

# --- 8. Flush DNS cache ---
echo "[8] Flushing local DNS cache:"
if [[ "$(uname)" == "Darwin" ]]; then
  sudo dscacheutil -flushcache
  sudo killall -HUP mDNSResponder
  echo "  macOS DNS cache flushed."
elif systemctl is-active --quiet systemd-resolved 2>/dev/null; then
  sudo systemd-resolve --flush-caches
  echo "  systemd-resolved DNS cache flushed."
else
  echo "  DNS flush not applicable on this system."
fi
echo ""

# --- 9. HTTP connectivity test ---
echo "[9] HTTP connectivity test (simulates browser request):"
if curl -s --max-time 5 http://www.google.com -o /dev/null -w "%{http_code}" | grep -q '200\|301\|302'; then
  echo "  OK: HTTP request to google.com succeeded."
else
  echo "  FAIL: HTTP request to google.com failed."
  echo "  Trying xfinity captive portal check..."
  curl -sv --max-time 5 http://xfinitywifi.com 2>&1 | grep -E 'Connected to|HTTP|Location' | head -5
fi
echo ""

echo "=== Diagnostic Complete ==="
echo "If all checks pass above but browser shows no internet:"
echo "  1. Try a different browser"
echo "  2. Disable VPN or proxy"
echo "  3. Check firewall rules blocking outbound traffic"
echo "  4. Visit https://www.xfinity.com/support/status to check outages"

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network administrators with 10+ years of experience diagnosing connectivity, DNS, DHCP, and ISP-level issues across enterprise and residential environments. Our guides are tested on real hardware and real networks before publication.

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.