Why does my AT&T Wi-Fi say 'connected, no internet' after a power outage?

Power outages frequently cause AT&T BGW gateways to come back online before the ONT has fully re-established the GPON fiber link, leaving the gateway in a state where it passes Wi-Fi but has no WAN connectivity. The fix is to unplug the gateway for 60 seconds after power is restored, then power it back on and wait the full 3-5 minutes for the broadband light to turn solid green before connecting devices.

My phone shows 'ATT connected without internet' but my laptop works fine — why?

This is almost always an IP address conflict or a stale DHCP lease on the phone. Your phone's lease may have expired while it was asleep, and on reconnect it received an IP already in use by another device. Toggle Airplane Mode off/on on the phone, or forget the Wi-Fi network and reconnect. If it recurs, assign the phone a static IP via the AT&T gateway's DHCP reservation feature at http://192.168.1.254.

Ping to 8.8.8.8 works but websites still don't load on AT&T — what's wrong?

This is a DNS-only failure. AT&T's DNS servers (68.94.156.1 and 68.94.157.1) are either down or returning bad responses. Run 'ipconfig /flushdns' on Windows or 'sudo resolvectl flush-caches' on Linux, then manually set your DNS servers to 8.8.8.8 (primary) and 8.8.4.4 (secondary) in your network adapter settings. If websites load after that, AT&T's DNS infrastructure is the culprit.

The broadband light on my AT&T BGW320 is red — is there an outage?

A red broadband light means the gateway cannot authenticate with AT&T's network, which is a WAN-side or ONT-side failure you cannot fix on your own LAN. First, check AT&T's outage map at att.com/outages or the myAT&T app. If no outage is listed, try power-cycling the gateway for 60 seconds. If the light remains red after restart, contact AT&T support at 800-288-2020 — the ONT may need reprovisioning or the fiber signal level may be out of range.

Can a firmware update cause AT&T Wi-Fi to show 'connected without internet'?

Yes. AT&T pushes automatic firmware updates to BGW gateways, typically during off-peak hours (2-5 AM). If a firmware update fails mid-flash or the gateway does not properly reboot after an update, it can enter a state where Wi-Fi association works but routing is broken. The fix is a power-cycle (60 seconds unplugged). If the gateway repeatedly fails after firmware updates, contact AT&T and request an RMA for a hardware replacement, as the flash storage on the gateway may be failing.

ATT Connected Without Internet: Full Troubleshooting Guide for 'Connected, No Internet' on AT&T Wi-Fi

Fix AT&T Wi-Fi 'connected without internet' in minutes. Step-by-step guide covering DNS resets, gateway reboots, IP conflicts, and advanced diagnostics.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,371 words

Key Takeaways

Root cause 1: DHCP lease failure — your device receives an APIPA address (169.254.x.x) instead of a valid AT&T gateway IP, blocking all internet routing.
Root cause 2: DNS resolution breakdown — AT&T's DNS servers (68.94.156.1 / 68.94.157.1) become unreachable or return NXDOMAIN for every query even when the Layer-2 link is up.
Root cause 3: AT&T BGW320/BGW210 gateway enters a hung state after a firmware push, passing Wi-Fi association but failing to bridge WAN traffic until power-cycled.
Root cause 4: IP address conflict — another device on the LAN holds the same lease, causing the gateway to withdraw the route silently.
Quick fix summary: Power-cycle the AT&T gateway (hold 30 sec), release/renew your DHCP lease, flush DNS cache, and if still failing, factory-reset the gateway or contact AT&T Tier-2 support to reprovision the ONT fiber signal.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle AT&T gateway (unplug 60 sec)	First step for any 'connected, no internet' symptom	2 min	None — safe for all users
Release & renew DHCP lease on client device	Device shows 169.254.x.x or wrong subnet IP	1 min	Very low — momentary disconnect
Flush DNS cache (ipconfig /flushdns or resolvectl flush)	Pages fail to load but ping by IP works	30 sec	None
Change DNS to public resolver (8.8.8.8 / 1.1.1.1)	AT&T DNS servers consistently timing out	3 min	Low — may bypass parental controls
Disable IPv6 on adapter	IPv6 prefix delegation fails causing dual-stack confusion	2 min	Low — IPv6 traffic falls back to IPv4
Check for IP conflict via ARP scan	Intermittent drops affecting one device only	5 min	None — read-only diagnostic
Factory reset AT&T BGW gateway	Gateway config corrupted after firmware update	15 min	Medium — loses custom port forwards and Wi-Fi passwords
Call AT&T to reprovision ONT / fiber line	All devices fail, gateway broadband light is red or amber	30-60 min	None on your end — carrier-side action

Understanding the 'ATT Connected Without Internet' Error

When your device reports 'Connected, no internet' on an AT&T network, Windows, macOS, Android, and iOS are all telling you the same thing: your device successfully completed a Wi-Fi association (Layer 2 is up) but cannot reach the public internet (Layer 3 routing is broken). AT&T's infrastructure stack — from the ONT (Optical Network Terminal) at the side of your home, through the BGW320 or BGW210 residential gateway, to your Wi-Fi client — has at least one broken handoff.

AT&T's gateway performs several critical jobs simultaneously:

Terminates the fiber GPON signal via the ONT
Authenticates to AT&T's network using 802.1X (EAP-TLS certificate)
Handles DHCP for your LAN (default pool: 192.168.1.2 – 192.168.1.253)
Provides DNS forwarding to AT&T's resolvers (68.94.156.1, 68.94.157.1)
Performs NAT/PAT for all outbound traffic

A failure at any of these layers produces the same user-visible symptom: connected without internet.

Step 1: Identify Which Layer Is Failing

Check your IP address first. Open a terminal or command prompt and run the appropriate command for your OS (see the code block section). Look for these patterns:

169.254.x.x → APIPA address — DHCP failed entirely. The AT&T gateway did not respond to your DISCOVER packet.
192.168.1.x with gateway 192.168.1.254 → DHCP worked. The problem is upstream (WAN, DNS, or routing).
192.168.1.x but gateway is unreachable → IP conflict or gateway hung state.

Ping the gateway directly:

ping 192.168.1.254

If this fails: the gateway itself is unreachable — power-cycle it.
If this succeeds: ping a public IP next: ping 8.8.8.8
- If ping 8.8.8.8 fails: WAN routing is broken. Check broadband status light on the gateway.
- If ping 8.8.8.8 succeeds: DNS is broken. Proceed to DNS fix.

Read the gateway status lights:

Green broadband light = fiber link and AT&T authentication are healthy.
Red/amber broadband light = ONT or AT&T authentication has failed. This requires AT&T intervention or a gateway power-cycle.
Flashing green = the gateway is still negotiating — wait 3-5 minutes.

Step 2: Fix — Work Through These in Order

Fix A: Power-Cycle the AT&T Gateway

This resolves the majority of 'ATT connected without internet' cases caused by firmware update hangs or DHCP daemon crashes.

Unplug the power cable from the rear of the BGW320/BGW210.
Wait a full 60 seconds (not 10 — capacitors need to discharge to clear NVRAM state).
Plug back in.
Wait 3-5 minutes for the broadband light to turn solid green before testing.

Fix B: Release and Renew Your DHCP Lease

If the gateway is healthy but your device has a stale or conflicted lease:

Windows: ipconfig /release && ipconfig /renew
macOS: System Settings → Network → your Wi-Fi → Details → TCP/IP → Renew DHCP Lease
Linux: sudo dhclient -r wlan0 && sudo dhclient wlan0
Android/iOS: Toggle Airplane Mode off/on, or forget the Wi-Fi network and reconnect.

Fix C: Flush DNS Cache

If Layer 3 routing works (ping 8.8.8.8 succeeds) but websites don't load, your DNS cache is corrupted or AT&T's resolvers are down.

Windows: ipconfig /flushdns
macOS (Ventura/Sonoma): sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
Linux (systemd-resolved): sudo resolvectl flush-caches

Then switch your DNS to a reliable public resolver: set your adapter's DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) and test again.

Fix D: Resolve an IP Address Conflict

Run an ARP scan on your LAN to detect duplicate IPs:

arp -a | grep 192.168.1

If two different MAC addresses map to the same IP, you have a conflict. Assign a static IP outside the AT&T gateway's DHCP pool, or log into http://192.168.1.254 and narrow the DHCP pool under Home Network → IP Allocation.

Fix E: Disable IPv6 on the Problematic Adapter

AT&T's BGW gateways sometimes fail to complete IPv6 prefix delegation (PD) after reboots, causing the OS to prefer a broken IPv6 path over a working IPv4 path.

Windows: netsh interface ipv6 set interface "Wi-Fi" disabled
macOS: Network settings → your adapter → Details → TCP/IP → Configure IPv6 → Off
Linux: sysctl -w net.ipv6.conf.wlan0.disable_ipv6=1

Test connectivity after disabling. If it works, the issue is IPv6-specific. Re-enable and investigate the gateway's IPv6 delegation settings.

Fix F: Factory Reset the AT&T Gateway

Use this only if power-cycling and the above steps all fail. The BGW320/BGW210 has a recessed reset button. Insert a paperclip and hold for 10 seconds until the device light blinks. The gateway will restore factory defaults and re-authenticate to AT&T's network. You will need to:

Reconnect all Wi-Fi devices with the default SSID/password printed on the gateway label.
Re-enter any custom port forwarding rules via http://192.168.1.254.

Fix G: Contact AT&T Support for ONT Reprovisioning

If the broadband light is red/amber after all of the above, the issue is outside your home network. AT&T's ONT may have lost its GPON signal, or your gateway's authentication certificate may need renewal on AT&T's end. Call 800-288-2020 (AT&T residential) and request a Tier-2 network check. They can:

Verify fiber signal levels at the ONT (optical power budget check)
Force a re-authentication of your gateway's EAP-TLS certificate
Dispatch a technician if the fiber strand or ONT hardware is at fault

Advanced: Capturing DHCP/DNS Failures with Wireshark

If you need to definitively prove where the failure occurs (useful for escalating to AT&T support), capture traffic on your Wi-Fi adapter:

# Linux: capture DHCP and DNS on wlan0 for 60 seconds
tcpdump -i wlan0 -w /tmp/att_debug.pcap 'port 67 or port 68 or port 53' & sleep 60; kill %1

Open the capture in Wireshark and look for:

Missing DHCPOFFER after DHCPDISCOVER → gateway DHCP daemon is dead
DHCPNAK → IP conflict confirmed
DNS queries with no response → AT&T resolver unreachable
ICMP 'destination unreachable' for 8.8.8.8 → WAN route missing

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# AT&T 'Connected Without Internet' Diagnostic Script
# Run on Linux/macOS. For Windows, see inline comments.
# ============================================================

ATT_GATEWAY="192.168.1.254"
PUBLIC_IP="8.8.8.8"
ATT_DNS1="68.94.156.1"
ATT_DNS2="68.94.157.1"
TEST_DOMAIN="www.att.com"

echo "=== Step 1: Show current IP configuration ==="
# Windows equivalent: ipconfig /all
ip addr show 2>/dev/null || ifconfig

echo ""
echo "=== Step 2: Check for APIPA (169.254.x.x) address ==="
APIPA=$(ip addr show | grep '169\.254\.' | awk '{print $2}')
if [ -n "$APIPA" ]; then
  echo "[FAIL] APIPA address detected: $APIPA — DHCP lease failed."
  echo "       Fix: power-cycle the AT&T gateway, then run:"
  echo "       sudo dhclient -r wlan0 && sudo dhclient wlan0"
else
  echo "[PASS] No APIPA address found. DHCP appears healthy."
fi

echo ""
echo "=== Step 3: Ping AT&T gateway ==="
# Windows: ping 192.168.1.254
if ping -c 3 -W 2 "$ATT_GATEWAY" > /dev/null 2>&1; then
  echo "[PASS] Gateway $ATT_GATEWAY is reachable."
else
  echo "[FAIL] Gateway $ATT_GATEWAY unreachable — power-cycle the BGW gateway."
  exit 1
fi

echo ""
echo "=== Step 4: Ping public IP (bypass DNS) ==="
# Windows: ping 8.8.8.8
if ping -c 3 -W 3 "$PUBLIC_IP" > /dev/null 2>&1; then
  echo "[PASS] Public IP $PUBLIC_IP reachable — WAN routing is working."
else
  echo "[FAIL] Cannot reach $PUBLIC_IP — WAN/NAT failure. Check broadband light."
fi

echo ""
echo "=== Step 5: Test AT&T DNS resolver ==="
# Windows: nslookup www.att.com 68.94.156.1
if command -v dig > /dev/null 2>&1; then
  RESULT=$(dig +short +timeout=5 @$ATT_DNS1 "$TEST_DOMAIN" 2>/dev/null)
  if [ -n "$RESULT" ]; then
    echo "[PASS] AT&T DNS $ATT_DNS1 resolved $TEST_DOMAIN -> $RESULT"
  else
    echo "[FAIL] AT&T DNS $ATT_DNS1 failed to resolve $TEST_DOMAIN."
    echo "       Fix: set DNS to 8.8.8.8 in your adapter settings."
    # Linux fix:
    echo "       Linux fix: echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf"
  fi
else
  echo "[SKIP] dig not installed. Install with: sudo apt install dnsutils"
fi

echo ""
echo "=== Step 6: Flush DNS cache ==="
# Detect OS and flush accordingly
if [[ "$OSTYPE" == "linux-gnu"* ]]; then
  if systemctl is-active --quiet systemd-resolved; then
    sudo resolvectl flush-caches && echo "[DONE] systemd-resolved cache flushed."
  else
    sudo /etc/init.d/nscd restart 2>/dev/null || echo "[INFO] No DNS cache daemon detected."
  fi
elif [[ "$OSTYPE" == "darwin"* ]]; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
  echo "[DONE] macOS DNS cache flushed."
fi
# Windows equivalent: ipconfig /flushdns

echo ""
echo "=== Step 7: Check for IP conflicts via ARP ==="
echo "Scanning LAN for duplicate MAC entries..."
arp -n | grep '192\.168\.1\.' | awk '{print $1, $3}' | sort | uniq -d -f1
if [ $? -eq 0 ]; then
  echo "[INFO] ARP table shown above. Look for same IP with two different MACs."
fi

echo ""
echo "=== Step 8: Check IPv6 delegation status ==="
IPV6_ADDR=$(ip -6 addr show scope global 2>/dev/null | grep 'inet6' | awk '{print $2}')
if [ -n "$IPV6_ADDR" ]; then
  echo "[INFO] IPv6 global address: $IPV6_ADDR"
  if ping6 -c 2 2001:4860:4860::8888 > /dev/null 2>&1; then
    echo "[PASS] IPv6 connectivity confirmed."
  else
    echo "[WARN] IPv6 address present but no connectivity. Consider disabling IPv6:"
    echo "       sudo sysctl -w net.ipv6.conf.wlan0.disable_ipv6=1"
  fi
else
  echo "[INFO] No IPv6 global address — running IPv4 only."
fi

echo ""
echo "=== Diagnostic Complete ==="
echo "If all steps pass but internet still fails, contact AT&T: 800-288-2020"
echo "Request a Tier-2 network check and ONT signal level verification."

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network specialists with combined experience spanning ISP infrastructure, enterprise networking, and consumer broadband troubleshooting. Our guides are based on real-world incident response, vendor documentation, and community-validated fixes. We specialize in translating complex Layer 2/3 failures into actionable steps that any user — from home consumers to IT administrators — can follow to restore connectivity quickly and confidently.

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.