Why does my Xfinity WiFi say 'connected' but I have no internet on my phone?

Your phone successfully joined the WiFi network (Layer 2 association) but the Xfinity gateway failed to route traffic to the internet (Layer 3). Try forgetting the WiFi network on your phone and reconnecting. If that doesn't work, reboot the gateway by unplugging it for 60 seconds. If your phone's cellular data shows internet while WiFi doesn't, the problem is definitely in the gateway or Xfinity's network, not your phone.

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

A solid white LED on Xfinity gateways (like the XB7 or XB8) means the gateway is powered on and WiFi is broadcasting, but it does NOT guarantee WAN connectivity. Log into the admin panel at http://10.0.0.1, go to Status > Connection, and verify that the WAN IP field shows a valid public IP (not 0.0.0.0). If WAN IP is missing, the modem hasn't received a lease from Comcast — reboot the gateway and check for service outages via the Xfinity app.

I'm getting ERR_NAME_NOT_RESOLVED on Chrome but I can ping 8.8.8.8 — how do I fix this on Xfinity?

ERR_NAME_NOT_RESOLVED with a successful ping to 8.8.8.8 confirms DNS is the only issue. Comcast's DNS servers are either overloaded or unreachable. Fix: Go to your network adapter settings and manually set DNS to 8.8.8.8 (Google) and 1.1.1.1 (Cloudflare). On Windows, also run 'ipconfig /flushdns' in an elevated command prompt. Chrome caches its own DNS — clear it at chrome://net-internals/#dns then click 'Clear host cache'. Restart Chrome and test again.

My Xfinity internet was working, then dropped to 'connected without internet' after a storm or power outage — how do I recover?

Power outages commonly cause two issues: (1) the gateway's DHCP lease expired or wasn't properly released, and (2) Comcast's local infrastructure (CMTS, node) may still be recovering. Steps: First, wait 15–30 minutes for Comcast's network to stabilize. Then power-cycle your gateway (unplug 60 seconds). Check the Xfinity Status Center at xfinity.com/support/status for reported outages in your ZIP code. If no outage is reported but internet remains down after a full gateway reboot, call Xfinity and request a remote provisioning refresh — this is common after power events.

Can a bad coaxial cable cause 'connected without internet' on Xfinity?

Yes. A damaged, loose, or low-quality coaxial cable between the wall outlet and your Xfinity gateway is a frequently overlooked cause. A bad coax causes signal degradation that prevents DOCSIS registration even if the gateway boots and broadcasts WiFi normally. Symptoms include uncorrectable codeword errors visible in the gateway's signal stats page and intermittent or zero downstream lock. Fix: Hand-tighten all coax connectors, replace the coax cable (use RG-6 rated cable), and eliminate any splitters from the cable run. After re-cabling, reboot the gateway and verify downstream lock in the admin panel.

Xfinity Connected Without Internet: How to Fix 'WiFi Connected but No Internet' on Xfinity

Fix Xfinity connected without internet in minutes. Step-by-step guide covering modem resets, DNS flush, gateway configs, and advanced network diagnostics.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,183 words

Key Takeaways

Root cause 1: The Xfinity gateway or modem has lost its WAN IP lease from Comcast's DHCP servers, leaving your device with a local IP but no upstream connectivity.
Root cause 2: DNS resolution is failing — your device is associated with the WiFi network but cannot resolve hostnames, producing the 'connected, no internet' status.
Root cause 3: An IP address conflict or stale ARP cache on your router or device is preventing proper routing even though the WiFi handshake succeeded.
Root cause 4: Xfinity's backend provisioning system hasn't fully authenticated your gateway (common after a power outage or firmware update), blocking internet traffic.
Quick fix summary: Power-cycle the Xfinity gateway (unplug for 60 seconds), flush DNS on your device, release/renew your IP, and verify through the Xfinity app or xfinityportal.com that your account is active and the gateway is online.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle the Xfinity gateway	First step for any 'connected without internet' scenario — resets WAN lease	2–5 min	None
Flush DNS & renew IP (ipconfig/nmcli)	DNS resolution failing; browser shows ERR_NAME_NOT_RESOLVED	1–2 min	None
Factory reset the Xfinity gateway	Persistent no-internet after multiple reboots; corrupted config suspected	10–15 min	Medium — wipes WiFi credentials
Change DNS servers to 8.8.8.8 / 1.1.1.1	ISP DNS unreachable but gateway WAN IP is valid	2 min	Low
Bypass gateway with a direct modem connection	Isolate whether issue is in router vs. modem vs. Xfinity WAN	5 min	Low
Contact Xfinity support / provisioning refresh	Account provisioning issue, outage, or MAC address mismatch	20–45 min	None
Replace Ethernet cable or NIC driver update	Physical layer or driver fault on a wired client showing no internet	10–20 min	Low

Understanding the 'Xfinity Connected Without Internet' Error

When your device shows 'Connected, no internet' or 'No internet access' while associated with your Xfinity WiFi network, it means the Layer 2 (WiFi) handshake succeeded — your device has a local IP — but Layer 3 (IP routing) or Layer 7 (DNS/HTTP) connectivity to the public internet is broken somewhere between your device and Comcast's upstream network.

Windows users see this as the yellow exclamation mark on the network taskbar icon and the message "Connected, no internet access" or "No network access". macOS shows the WiFi bars with a warning triangle. Browsers return errors like ERR_NAME_NOT_RESOLVED, ERR_INTERNET_DISCONNECTED, or DNS_PROBE_FINISHED_NO_INTERNET.

Step 1: Identify Where the Break Occurs

Before touching any settings, isolate the failure layer:

1a. Check if other devices have internet. If your phone on the same Xfinity WiFi has internet but your laptop doesn't, the problem is device-specific (NIC driver, IP conflict, OS network stack). If all devices are down, the issue is in the gateway or upstream.

1b. Ping the gateway. Open a terminal and run:

ping 10.0.0.1

(Default Xfinity gateway address; may also be 192.168.1.1 or 192.168.0.1 — check via ipconfig /all on Windows or ip route on Linux/Mac.)

Gateway responds, internet does not → WAN or DNS issue.
Gateway does not respond → local network/routing issue or wrong gateway IP.

1c. Ping a public IP (bypassing DNS):

ping 8.8.8.8

If 8.8.8.8 responds but websites don't load → DNS is broken.
If 8.8.8.8 does not respond → WAN connectivity is broken at the modem/gateway level.

1d. Check your WAN IP in the Xfinity Admin Tool. Navigate to http://10.0.0.1 (gateway admin), log in (default: admin / password), and check the Status > Connection page. If the WAN IP field shows 0.0.0.0 or is blank, the modem has not received an IP from Comcast's DHCP — this is the most common root cause.

Step 2: Power-Cycle the Xfinity Gateway (Fix #1 — Try First)

Unplug the power cable from the back of the Xfinity gateway/modem.
Wait a full 60 seconds (not 10 — capacitors need to fully discharge so the DHCP lease is truly released).
Plug power back in.
Wait 3–5 minutes for the gateway to fully initialize and re-register with Comcast's provisioning servers. Watch the LED: solid white or green = ready.
Re-test internet on all devices.

This resolves approximately 60% of 'connected without internet' cases by forcing a fresh DHCP lease from Comcast and re-authenticating the gateway's cable modem registration (DOCSIS provisioning).

Step 3: Flush DNS and Renew Your Device's IP (Fix #2)

If internet is still broken only on one device after the gateway is confirmed online:

Windows:

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

Restart the device after running these commands.

macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
sudo ipconfig set en0 DHCP

Linux (Ubuntu/Debian with NetworkManager):

nmcli networking off && sleep 3 && nmcli networking on
sudo systemd-resolve --flush-caches

Step 4: Change DNS Servers (Fix #3 — DNS-Specific Issues)

If pinging 8.8.8.8 works but websites don't load, Comcast's DNS servers are unreachable. Set manual DNS:

On Windows: Control Panel → Network → Adapter Properties → IPv4 → Use the following DNS:

Preferred: 8.8.8.8
Alternate: 1.1.1.1

On macOS: System Settings → Network → Your Connection → DNS → add 8.8.8.8 and 1.1.1.1.

On the Xfinity Gateway itself (applies to all clients): Log into http://10.0.0.1 → Advanced → DNS → enter 8.8.8.8 as primary and 1.1.1.1 as secondary. This overrides Comcast's default DNS for your entire home network.

Step 5: Check for IP Address Conflicts

If your device received a self-assigned IP (169.254.x.x on Windows/Mac, or a non-RFC-1918 address), there's a DHCP failure:

Log into the gateway admin (http://10.0.0.1).
Go to Connected Devices (or DHCP Clients List).
Look for duplicate IP assignments.
Restart the DHCP server from the admin panel or reboot the gateway.
On the affected device, manually assign a static IP in the same subnet (e.g., 192.168.1.150, gateway 192.168.1.1, DNS 8.8.8.8) as a temporary workaround.

Step 6: Factory Reset the Xfinity Gateway (Fix #4 — Last Resort Before Calling Support)

If all above steps fail:

Press and hold the Reset button on the back of the gateway for 10 seconds until the LED blinks.
Wait 5–10 minutes for a full reset and re-provisioning.
Reconfigure your WiFi network name (SSID) and password.
Test internet access.

Warning: A factory reset erases all custom settings including port forwarding rules, static IP assignments, and parental controls.

Step 7: Verify Account Status and Check for Outages

If none of the above resolves the issue:

Open the Xfinity app on your mobile phone (on cellular data) and check for service outages in your area.
Log into https://www.xfinity.com/support/status to view account status.
Call Xfinity support at 1-800-XFINITY (1-800-934-6489) and ask them to send a re-provisioning signal to your gateway. This is a backend reset that Comcast technicians can perform remotely and often resolves lingering no-internet states after equipment changes or power events.
If you recently moved your gateway, Xfinity may need to re-associate your gateway's MAC address with your account.

Advanced: Check DOCSIS Registration Status

For users comfortable with gateway administration, the cable modem's DOCSIS registration status tells you definitively whether Comcast's head-end has accepted your modem:

Navigate to http://10.0.0.1/cmStatus.htm (or similar path depending on gateway model) and look for:

Downstream Lock: Should show locked channels
Upstream Lock: Should show locked channels
Registration Status: Should show Operational or Registered

If Registration Status shows Unregistered or Ranging, Comcast's CMTS (Cable Modem Termination System) hasn't provisioned your modem — this requires Xfinity support intervention.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# Xfinity "Connected Without Internet" Diagnostic Script
# Run on the affected client device (Linux/macOS)
# Windows users: use the equivalent ipconfig/ping commands below
# ============================================================

echo "=== [1] Local Network Interface Info ==="
if command -v ip &>/dev/null; then
  ip addr show
  ip route show
else
  ifconfig
  netstat -rn
fi

echo ""
echo "=== [2] Gateway Detection ==="
GATEWAY=$(ip route show default 2>/dev/null | awk '/default/ {print $3}' | head -1)
if [ -z "$GATEWAY" ]; then
  GATEWAY=$(route -n get default 2>/dev/null | awk '/gateway/ {print $2}')
fi
echo "Detected gateway: $GATEWAY"

echo ""
echo "=== [3] Ping Gateway (Layer 3 local reachability) ==="
ping -c 4 "${GATEWAY:-10.0.0.1}"

echo ""
echo "=== [4] Ping Public IP 8.8.8.8 (bypass DNS) ==="
ping -c 4 8.8.8.8

echo ""
echo "=== [5] DNS Resolution Test ==="
if command -v dig &>/dev/null; then
  dig +short google.com @8.8.8.8
  dig +short google.com @1.1.1.1
else
  nslookup google.com 8.8.8.8
fi

echo ""
echo "=== [6] Traceroute to Public Internet ==="
if command -v traceroute &>/dev/null; then
  traceroute -m 10 8.8.8.8
elif command -v tracepath &>/dev/null; then
  tracepath -m 10 8.8.8.8
fi

echo ""
echo "=== [7] Flush DNS Cache (Linux) ==="
if command -v systemd-resolve &>/dev/null; then
  sudo systemd-resolve --flush-caches && echo "DNS cache flushed via systemd-resolve"
elif command -v resolvectl &>/dev/null; then
  sudo resolvectl flush-caches && echo "DNS cache flushed via resolvectl"
fi

echo ""
echo "=== [8] Release and Renew DHCP (Linux with NetworkManager) ==="
# Uncomment the lines below to execute DHCP renewal
# INTERFACE=$(ip route show default | awk '/default/ {print $5}' | head -1)
# echo "Renewing DHCP on interface: $INTERFACE"
# sudo dhclient -r $INTERFACE && sudo dhclient $INTERFACE

echo ""
echo "=== [9] Check Current DNS Servers ==="
cat /etc/resolv.conf 2>/dev/null || resolvectl status 2>/dev/null

echo ""
echo "=== [10] Xfinity Gateway Admin Access Test ==="
curl -s -o /dev/null -w "Gateway admin HTTP status: %{http_code}\n" http://10.0.0.1 --connect-timeout 5

echo ""
echo "=== WINDOWS EQUIVALENT COMMANDS (run in elevated CMD) ==="
echo "  ipconfig /all"
echo "  ping 10.0.0.1"
echo "  ping 8.8.8.8"
echo "  nslookup google.com 8.8.8.8"
echo "  ipconfig /release"
echo "  ipconfig /flushdns"
echo "  ipconfig /renew"
echo "  netsh winsock reset"
echo "  netsh int ip reset"
echo "  tracert 8.8.8.8"
echo ""
echo "=== Diagnostic Complete ==="

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, DNS, routing, and ISP provisioning issues across enterprise and residential environments. Our guides are tested against real hardware and validated against official vendor documentation 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.