Why does my Xfinity WiFi say 'connected, no internet' after a power outage?

After a power outage, the modem must re-register with Comcast's CMTS (Cable Modem Termination System) and re-download its provisioning file. If power returns erratically or the modem powers on before Comcast's infrastructure stabilizes, it can get stuck mid-provisioning. The gateway hands out a local IP to your devices (so WiFi shows 'connected'), but the WAN interface never acquires a public IP. Fix: Perform a full power cycle — unplug the modem for 60 seconds, plug it back in alone, wait 3 minutes for the online LED to go solid, then plug in your router.

Why does my Xfinity internet work on some devices but not others on the same WiFi?

This is almost always a device-side DHCP or DNS cache problem, not a modem issue. The devices that work obtained a valid DHCP lease and have a clean DNS cache. The failing device may have a stale lease, a static IP that conflicts with another device, or a corrupted DNS cache. Fix: On the failing device, toggle WiFi off and on, or run 'ipconfig /release && ipconfig /renew' (Windows) / 'sudo dhclient -r && sudo dhclient' (Linux/macOS). If that doesn't work, set the device to DHCP (not static IP) and flush its DNS cache.

My Xfinity modem shows a solid white light but I still have no internet — what does that mean?

A solid white light on XB6/XB7/XB8 gateways means the modem has completed DOCSIS registration and believes it has internet connectivity. The disconnect could be: (1) DNS-only failure — test by pinging 8.8.8.8 directly; if that works, switch DNS to 8.8.8.8. (2) A routing issue between your client and the gateway — reboot just the router portion (not the modem). (3) An account issue — Xfinity may have suspended or throttled the account; check the My Account app or call 1-800-XFINITY. (4) IPv6 misconfiguration on the client — try disabling IPv6 on the device's adapter temporarily.

Will restarting my Xfinity gateway fix the 'no internet' issue without changing my WiFi password?

Yes — a standard restart (power cycle or the 'Restart' option in the admin UI at http://10.0.0.1) preserves all your custom settings, including WiFi SSID, password, port forwards, and firewall rules. Only a Factory Reset erases those settings. A restart simply re-registers the modem with Comcast and refreshes DHCP/DNS state. You can also use the Xfinity My Account app: go to Internet > Restart this device to initiate a safe restart remotely.

I get 'ERR_NAME_NOT_RESOLVED' or 'DNS_PROBE_FINISHED_NXDOMAIN' on Xfinity — is this a DNS problem?

Yes. ERR_NAME_NOT_RESOLVED and DNS_PROBE_FINISHED_NXDOMAIN are Chrome's error codes for DNS lookup failures — the browser can't translate a domain name (like google.com) into an IP address. This confirms the issue is DNS-specific, not a total connectivity loss. Steps: (1) Run 'ping 8.8.8.8' — if it succeeds, your network layer is fine but Xfinity DNS is failing. (2) Flush DNS cache: 'ipconfig /flushdns' on Windows, 'sudo dscacheutil -flushcache' on macOS. (3) Change your DNS server to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) in your network adapter settings. (4) If the problem persists network-wide, log into http://10.0.0.1 and change the DNS settings at the router level.

WiFi Connected But No Internet Xfinity: Complete Troubleshooting Guide (2020–2024)

Fix Xfinity WiFi connected but no internet access in minutes. Step-by-step diagnosis, modem reboot scripts, DNS fixes, and gateway resets covered.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,650 words

Key Takeaways

Root cause 1: Xfinity gateway DHCP lease failure or IP address conflict — your device connects to the router but the modem loses its WAN IP from Comcast's CMTS, breaking internet routing.
Root cause 2: DNS resolution failure — Xfinity's DNS servers (75.75.75.75 / 75.75.76.76) become unreachable or your device caches stale DNS, causing all browser requests to fail even though the TCP/IP layer is healthy.
Root cause 3: Modem firmware provisioning stuck — after a power cycle or Xfinity network update, the DOCSIS modem re-registers but the provisioning file never fully downloads, leaving the WAN interface unconfigured.
Quick fix summary: (1) Reboot modem and router in the correct sequence (modem first, wait 2 min, then router). (2) Flush DNS cache and renew DHCP on your client device. (3) If still failing, factory-reset the Xfinity gateway or call Xfinity to push a remote signal refresh from their end.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle modem + router (sequence reboot)	First step for any 'connected, no internet' issue; covers 70% of cases	3–5 min	None — safe for all users
Flush DNS cache + renew DHCP on client	Browser shows ERR_NAME_NOT_RESOLVED or sites load by IP but not hostname	1–2 min	None — non-destructive client-side command
Change DNS to Google (8.8.8.8) or Cloudflare (1.1.1.1)	Xfinity DNS servers are down or returning NXDOMAIN for valid domains	2 min	Low — slightly increases privacy exposure to third-party DNS
Release/renew WAN IP via Xfinity Admin UI (10.0.0.1)	Device shows 169.254.x.x or 0.0.0.0 WAN IP on gateway status page	5 min	Low — may briefly disconnect all clients
Factory reset Xfinity gateway (30-30-30 or button hold)	Persistent issue after all software fixes; corrupted config suspected	15–20 min	Medium — erases all custom WiFi, firewall, and port-forward settings
Call Xfinity support for remote signal/provisioning refresh	Upstream signal levels out of spec (T3/T4 timeouts in modem logs)	20–60 min	None — Xfinity pushes config remotely; no settings lost
Replace coax splitter or coax cable to modem	Modem logs show high uncorrectable errors or SNR below 30 dB	30 min	Low — hardware swap; no config change

Understanding the Error: Xfinity WiFi Connected But No Internet

When your device reports "WiFi connected, no internet" on an Xfinity network, the operating system has successfully associated with the wireless access point and received a local IP address (e.g., 192.168.1.x or 10.0.0.x), but packets cannot reach the public internet. Windows shows this as a yellow exclamation mark on the network icon with the message "No Internet Access" or "No internet, secured". macOS displays a globe icon instead of the WiFi bars and warns "Wi-Fi has the IP address [x] but your device can't connect to the internet." Android and iOS show "Connected, no internet" or a persistent "!" badge on the WiFi indicator.

The gap between local connectivity and internet access almost always lives in one of four places: the modem's WAN connection to Comcast's infrastructure, the gateway's DHCP/NAT configuration, DNS resolution, or your client device's network stack.

Step 1: Diagnose — Pinpoint Where the Break Occurs

1.1 Check the modem status lights

Xfinity gateways (XB6, XB7, XB8) use LED colors to signal status:

White/solid — fully operational
White/blinking — connecting or activity
Yellow/orange — limited connectivity or firmware update
Red — no signal or hardware fault
Blue (blinking) — WPS pairing mode

If your gateway LED is yellow or red, the problem is upstream (Comcast's network or your coax/coax signal), not your WiFi radio.

1.2 Ping the gateway from your device

Open a terminal and run:

ping 10.0.0.1

ping 192.168.1.1

(whichever matches your subnet). If this fails, you have a LAN-layer problem — likely a bad DHCP lease. If it succeeds, the router is reachable but the WAN is broken.

1.3 Ping a public IP address

ping 8.8.8.8

If this fails but the gateway ping succeeds, the modem has no WAN route — reboot the modem. If this succeeds but websites still don't load, you have a DNS-only failure.

1.4 Ping a public hostname

ping google.com

If 8.8.8.8 responds but google.com does not, DNS is broken. Proceed to the DNS fix in Step 2.3.

1.5 Check the modem's WAN IP via the admin UI

Navigate to http://10.0.0.1 in your browser (default for Xfinity XB-series gateways). Log in with admin / password (or your custom credentials). Go to Gateway > Connection > Status. Look at the WAN IP Address field:

A valid public IP (e.g., 96.x.x.x, 71.x.x.x) means provisioning succeeded.
0.0.0.0 or 169.254.x.x means DHCP from Comcast's CMTS failed — reboot the modem or call Xfinity.

1.6 Inspect modem event logs for DOCSIS errors

In the admin UI: Gateway > Connection > DOCSIS Event Log. Look for:

T3 timeout — upstream ranging failed; check coax connections
T4 timeout — no maintenance opportunity from CMTS; signal issue
DHCP FAILED — Comcast DHCP server not responding
BPI+ authorization — cable modem security handshake failing; call Xfinity

Step 2: Fix — Ordered From Fastest to Most Invasive

2.1 Correct power-cycle sequence (most common fix)

This resolves stale ARP entries, DHCP lease conflicts, and provisioning hangs:

Unplug the modem power cable. If you have a separate router, unplug it too.
Wait 60 seconds (not 10 — capacitors need to drain so the CMTS drops the old session).
Plug in modem only. Watch for the online light to go solid (up to 3 minutes).
Plug in the router (if separate). Wait 60 seconds.
Reconnect your devices.

If you have an all-in-one Xfinity gateway (XB6/XB7/XB8), you only have one device to reboot but the wait time is the same.

2.2 Renew DHCP lease on the client device

Windows:

ipconfig /release
ipconfig /renew

macOS/Linux:

sudo dhclient -r && sudo dhclient

Or toggle WiFi off and back on — this triggers a fresh DHCP DISCOVER.

2.3 Fix DNS failures

Flush the local DNS cache:

Windows: ipconfig /flushdns
macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linux (systemd): sudo systemd-resolve --flush-caches

If Xfinity DNS servers are down, temporarily switch to a reliable public DNS:

Google: 8.8.8.8 and 8.8.4.4
Cloudflare: 1.1.1.1 and 1.0.0.1

On Windows: Settings > Network & Internet > Change adapter options > Right-click adapter > Properties > IPv4 > Use the following DNS On macOS: System Preferences > Network > Advanced > DNS

2.4 Release and renew the WAN IP from the gateway admin UI

Navigate to http://10.0.0.1 > Gateway > Connection > Status and click Release then Renew under the WAN IP section. This forces the modem to send a DHCP DISCOVER to Comcast's CMTS without a full power cycle.

2.5 Reset network stack on Windows

Run Command Prompt as Administrator:

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

Reboot the PC afterward.

2.6 Factory reset the Xfinity gateway

Warning: This erases all custom settings — WiFi name, password, port forwards, firewall rules.

Method A (button): Find the Reset pinhole on the back of the gateway. Press and hold with a paperclip for 30 seconds until the LED changes. Release and wait 5 minutes for full reboot.

Method B (admin UI): Gateway > Troubleshooting > Reset/Restore Gateway > Factory Reset.

After reset, use the default credentials printed on the gateway label to reconfigure your network.

2.7 Check for Xfinity service outages

Before investing more time, verify there isn't a neighborhood outage:

Open the Xfinity My Account app (works on cellular data) and check the Status Center.
Visit https://www.xfinity.com/support/status on your mobile network.
Text "OUT" to 266278 (COMCST) for an automated outage check.

2.8 Check coax signal levels (advanced)

In the admin UI: Gateway > Connection > DOCSIS > Signal. Healthy values:

Downstream power: -7 to +7 dBmV (ideal 0)
Downstream SNR: ≥ 30 dB
Upstream power: 38–48 dBmV

If values are outside these ranges, inspect coax cable connections, replace any splitters with a higher-quality unit (≥ 1 GHz rated), and eliminate any barrel connectors or barrel adapters on the modem's direct coax run.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# =============================================================
# Xfinity WiFi Connected But No Internet — Diagnostic Script
# Compatible: macOS, Linux (run on Windows with Git Bash/WSL)
# Usage: chmod +x xfinity_diag.sh && ./xfinity_diag.sh
# =============================================================

set -euo pipefail

GATEWAY_IPS=("10.0.0.1" "192.168.1.1" "192.168.0.1")
PUBLIC_IP="8.8.8.8"
PUBLIC_HOST="google.com"
XFINITY_DNS1="75.75.75.75"
XFINITY_DNS2="75.75.76.76"

echo "===== Xfinity No-Internet Diagnostic Tool ====="
echo "Timestamp: $(date)"
echo ""

# --- 1. Show current IP configuration ---
echo "[1] Network Interface Configuration:"
if command -v ip &>/dev/null; then
  ip addr show | grep -E 'inet |link/'
elif command -v ifconfig &>/dev/null; then
  ifconfig | grep -E 'inet |ether '
else
  echo "  No ip/ifconfig found. Run 'ipconfig' on Windows."
fi
echo ""

# --- 2. Detect active gateway ---
echo "[2] Detecting Active Gateway:"
if command -v ip &>/dev/null; then
  DETECTED_GW=$(ip route | awk '/default/ {print $3; exit}')
elif command -v netstat &>/dev/null; then
  DETECTED_GW=$(netstat -rn | awk '/default|0\.0\.0\.0/ {print $2; exit}')
fi
echo "  Detected gateway: ${DETECTED_GW:-unknown}"
echo ""

# --- 3. Ping gateway ---
echo "[3] Ping Gateway (${DETECTED_GW:-10.0.0.1}):"
if ping -c 3 -W 2 "${DETECTED_GW:-10.0.0.1}" &>/dev/null; then
  echo "  PASS — Gateway is reachable on LAN."
else
  echo "  FAIL — Cannot reach gateway. Check WiFi association and DHCP lease."
fi
echo ""

# --- 4. Ping public IP (bypasses DNS) ---
echo "[4] Ping Public IP ($PUBLIC_IP — bypasses DNS):"
if ping -c 3 -W 3 "$PUBLIC_IP" &>/dev/null; then
  echo "  PASS — WAN routing is working. If websites fail, DNS is the issue."
else
  echo "  FAIL — No route to public internet. Reboot modem or check Xfinity outage."
fi
echo ""

# --- 5. DNS resolution test ---
echo "[5] DNS Resolution Test ($PUBLIC_HOST):"
if command -v dig &>/dev/null; then
  RESOLVED=$(dig +short "$PUBLIC_HOST" @"$XFINITY_DNS1" 2>/dev/null | head -1)
  echo "  Xfinity DNS ($XFINITY_DNS1) resolved $PUBLIC_HOST to: ${RESOLVED:-FAILED}"
  RESOLVED_CF=$(dig +short "$PUBLIC_HOST" @1.1.1.1 2>/dev/null | head -1)
  echo "  Cloudflare DNS (1.1.1.1) resolved $PUBLIC_HOST to: ${RESOLVED_CF:-FAILED}"
elif command -v nslookup &>/dev/null; then
  nslookup "$PUBLIC_HOST" "$XFINITY_DNS1" 2>/dev/null | grep 'Address' || echo "  FAILED via Xfinity DNS"
else
  echo "  dig/nslookup not found. Install dnsutils (Linux) or use nslookup on Windows."
fi
echo ""

# --- 6. Flush DNS cache (macOS/Linux) ---
echo "[6] DNS Cache Flush:"
if [[ "$(uname)" == "Darwin" ]]; then
  sudo dscacheutil -flushcache 2>/dev/null && sudo killall -HUP mDNSResponder 2>/dev/null
  echo "  macOS DNS cache flushed."
elif command -v systemd-resolve &>/dev/null; then
  sudo systemd-resolve --flush-caches 2>/dev/null
  echo "  systemd-resolved cache flushed."
elif [[ -f /etc/init.d/nscd ]]; then
  sudo /etc/init.d/nscd restart 2>/dev/null
  echo "  nscd restarted."
else
  echo "  Could not auto-flush. On Windows run: ipconfig /flushdns"
fi
echo ""

# --- 7. DHCP lease renew (Linux) ---
echo "[7] DHCP Lease Renewal (Linux only):"
if command -v dhclient &>/dev/null; then
  IFACE=$(ip route | awk '/default/ {print $5; exit}')
  if [[ -n "$IFACE" ]]; then
    echo "  Releasing and renewing DHCP lease on $IFACE..."
    sudo dhclient -r "$IFACE" 2>/dev/null && sudo dhclient "$IFACE" 2>/dev/null
    echo "  DHCP renewed. New IP:"
    ip addr show "$IFACE" | grep 'inet '
  else
    echo "  Could not detect interface. Run manually: sudo dhclient -r eth0 && sudo dhclient eth0"
  fi
else
  echo "  dhclient not found. On macOS toggle WiFi off/on. On Windows run: ipconfig /release && ipconfig /renew"
fi
echo ""

# --- 8. Check HTTP connectivity ---
echo "[8] HTTP Connectivity Check:"
if command -v curl &>/dev/null; then
  HTTP_CODE=$(curl -s -o /dev/null -w "%{http_code}" --max-time 5 http://connectivitycheck.gstatic.com/generate_204 2>/dev/null)
  if [[ "$HTTP_CODE" == "204" ]]; then
    echo "  PASS — HTTP internet access confirmed (204 response from Google connectivity check)."
  else
    echo "  FAIL — HTTP check returned code: $HTTP_CODE (expected 204). Internet is blocked."
  fi
else
  echo "  curl not found. Install curl to run HTTP check."
fi
echo ""

echo "===== Diagnostic Complete ====="
echo "If all pings pass but DNS fails: change DNS to 8.8.8.8 or 1.1.1.1"
echo "If public IP ping fails: power-cycle modem (60s unplug), wait 3 min for online LED"
echo "If gateway ping fails: reboot router, check WiFi band (try 2.4GHz)"
echo "Check Xfinity outages: https://www.xfinity.com/support/status"
echo "Xfinity admin UI: http://10.0.0.1 (user: admin, pass: on label)"

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 ISP, cloud, and enterprise environments. Our guides are tested on real hardware and reviewed against official vendor documentation before publication. We specialize in translating cryptic error messages and blinking LED patterns into clear, actionable troubleshooting steps for both home users and IT professionals.

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.