Why does my ATT WiFi say 'Connected' but there is no internet access?

This happens because WiFi connectivity and internet routing are two separate things. Your device successfully associated with the ATT gateway's WiFi radio (Layer 2), but the gateway may have lost its upstream WAN connection to ATT's network, your device failed to get a valid IP via DHCP (showing 169.254.x.x), or DNS resolution is broken. Start by power-cycling the ATT gateway for 60 seconds, then run 'ipconfig /release && ipconfig /renew' on your device.

My ATT internet is connected without internet on only one device — other devices work fine. What's wrong?

If only one device is affected, the problem is on that device, not the gateway or ATT's network. Most likely causes: (1) Corrupted DHCP lease — run 'ipconfig /release && ipconfig /renew' (Windows) or 'sudo dhclient -r && sudo dhclient' (Linux). (2) Corrupted Winsock/TCP stack on Windows — run 'netsh winsock reset' and reboot. (3) A VPN or security software is intercepting traffic. (4) The device has a static IP configured that conflicts with another device. Check the device's IP address with 'ipconfig /all' — it should be 192.168.1.x, not 169.254.x.x.

My ATT BGW320 or BGW210 gateway shows a green broadband light but still no internet. How do I fix it?

A green broadband LED means the physical WAN link (fiber or DSL sync) is established, but the gateway may have lost its IP session with ATT. Log into http://192.168.1.254 and check if 'Broadband IPv4 Address' shows a valid public IP or 0.0.0.0. If it shows 0.0.0.0, the DHCP/PPPoE negotiation with ATT failed. Try a gateway power-cycle (unplug 60 sec). If the issue persists after 3 restarts, the problem is likely on ATT's side — check the ATT outage map at att.com/internet/outage or call ATT support at 800-288-2020.

Can I fix ATT 'connected without internet' on Android or iPhone without touching the router?

Yes. On Android: Go to Settings → Network & Internet → WiFi → Long-press your ATT network → Forget network, then reconnect. Also try toggling Airplane mode on and off to reset the network stack. On iPhone/iPad: Go to Settings → WiFi → Tap the (i) next to your ATT network → Forget This Network, then reconnect. You can also try Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings (this clears all saved WiFi passwords). For a quick DNS fix without forgetting the network, go to Settings → WiFi → tap (i) → Configure DNS → Manual → Add 8.8.8.8.

How do I tell if my 'ATT connected without internet' issue is an ATT outage vs. a local gateway problem?

Run this diagnostic: (1) Check http://192.168.1.254 — if you cannot load the gateway page, it's a local gateway or device issue. (2) If you CAN load the gateway page, check the 'Broadband' status. If the WAN IP shows 0.0.0.0, it strongly suggests an ATT-side provisioning or outage issue. (3) Visit https://downdetector.com/status/att/ or https://www.att.com/internet/outage/ on a mobile data connection to see reported outages in your area. (4) Call ATT at 800-288-2020 and use the automated system — it will check for known outages tied to your account address automatically.

ATT Connected Without Internet: Complete Troubleshooting Guide (WiFi Shows Connected But No Internet Access)

Fix ATT WiFi connected without internet in minutes. Step-by-step diagnostics: restart gateway, flush DNS, renew IP, reset network stack. All fixes covered.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,663 words

Key Takeaways

Root cause 1: IP address conflict or DHCP lease failure — your device receives an APIPA address (169.254.x.x) instead of a valid ATT gateway-assigned IP, causing no actual internet routing.
Root cause 2: DNS resolution failure — the ATT gateway obtains a WAN connection but DNS servers become unreachable or corrupted, so hostnames cannot be resolved even though TCP/IP connectivity exists.
Root cause 3: ATT BGW320/BGW210 gateway firmware bug or stuck NAT table — the gateway itself loses its PPPoE or DHCP WAN session with ATT's upstream network while still broadcasting a local WiFi SSID.
Root cause 4: Corrupted TCP/IP stack or Winsock catalog on the client device — common after Windows updates or VPN software installation.
Quick fix summary: (1) Power-cycle the ATT gateway for 60 seconds. (2) On your device, run 'ipconfig /release && ipconfig /renew' (Windows) or 'sudo dhclient -r && sudo dhclient' (Linux/Mac). (3) Flush DNS with 'ipconfig /flushdns'. (4) Reset the Winsock catalog with 'netsh winsock reset'. (5) If all else fails, factory-reset the ATT gateway via the pinhole button.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle ATT gateway (unplug 60 sec)	First step for any 'connected, no internet' scenario on ATT	2–5 min	None — non-destructive
IP release/renew on client device	Device shows 169.254.x.x or 0.0.0.0 IP address; DHCP lease expired	< 1 min	None — temporary disconnect only
DNS flush + change to 8.8.8.8	Pages time out but pings to IP addresses like 8.8.8.8 succeed	< 1 min	Very low — overrides ATT default DNS
Netsh Winsock reset (Windows)	After VPN uninstall, Windows update, or driver change broke TCP/IP stack	2 min + reboot	Low — requires reboot, rarely causes issues
Forget WiFi network and reconnect	Authentication/handshake stuck; gateway shows client connected but routing fails	2 min	None
ATT gateway soft reset (Settings UI)	Gateway WAN session dropped; DSL/fiber sync light is green but internet LED is red/off	5–10 min	Low — clears sessions but keeps config
ATT gateway factory reset (pinhole)	All other methods fail; suspected firmware corruption or misconfiguration	15–20 min	Medium — erases all custom settings
Update gateway firmware via ATT Smart Home Manager	Known firmware bug in BGW320 or BGW210 causing random WAN drops	10–15 min	Low — applied by ATT automatically
Contact ATT support / dispatch technician	WAN signal levels (DSL/fiber) are out of spec; line issue suspected	Hours–days	None — passive action

Understanding the 'ATT Connected Without Internet' Error

When your device shows 'Connected' to your ATT WiFi network but has no internet access, it means your device successfully completed the 802.11 WiFi association and received (or failed to receive) an IP address from your ATT gateway's DHCP server — but actual routed traffic to the public internet is not flowing. This is a distinct failure from not being able to connect to WiFi at all.

Windows will display the yellow exclamation mark on the network tray icon with the message 'No Internet Access' or 'No network access.' macOS shows a globe icon with an exclamation mark. Android displays 'Connected, no internet' directly under the SSID name.

Identifying Which Layer Is Broken

The OSI model helps isolate the fault:

Layer 1–2 (Physical/Data Link): WiFi association is fine — you are connected to the ATT gateway.
Layer 3 (Network/IP): DHCP may have failed, giving you an APIPA address (169.254.x.x) or the gateway's WAN IP is missing.
Layer 4–7 (Transport/Application): DNS resolution fails, or the ATT upstream PPPoE/DHCP WAN session is dropped.

Step 1: Diagnose the Problem

1a. Check your device's IP address

On Windows, open Command Prompt and run:

ipconfig /all

Look at the 'IPv4 Address' field under your WiFi adapter. A valid ATT network address is typically in the range 192.168.1.x (default ATT gateway subnet). If you see 169.254.x.x, your device obtained an APIPA address — DHCP from the gateway failed. If you see 0.0.0.0, DHCP timed out entirely.

On macOS/Linux:

ifconfig en0   # macOS
ip addr show wlan0  # Linux

1b. Ping the gateway

The default ATT gateway IP is 192.168.1.254 (BGW320/BGW210) or 192.168.1.1 (older 2Wire/Pace gateways).

ping 192.168.1.254

If this fails, the problem is between your device and the gateway (WiFi layer or DHCP). If it succeeds, move to step 1c.

1c. Ping a public IP address (bypass DNS)

ping 8.8.8.8

If pinging 8.8.8.8 fails but pinging the gateway succeeds, the ATT gateway has lost its WAN (upstream) connection to ATT's network. Confirm by checking the ATT gateway's status LED: a solid green 'Broadband' or 'Service' LED means the WAN is up. An amber or red LED means the WAN connection is down.

1d. Test DNS resolution

nslookup google.com 8.8.8.8

If this resolves but nslookup google.com (without specifying a DNS server) fails, the ATT gateway's DNS relay is broken. You can work around this by setting your DNS manually to 8.8.8.8.

1e. Check ATT gateway status page

Open a browser and navigate to http://192.168.1.254 — log in with your gateway credentials (printed on the device label). Navigate to Home Network > Diagnostics or Broadband > Status. Check:

Broadband IPv4 Address: Should show a public or ATT-assigned IP (not 0.0.0.0)
DSL/Fiber Status: Should show 'Connected'
DNS Servers: Should show ATT DNS IPs (e.g., 68.94.156.1, 68.94.157.1)

Step 2: Fix the Problem

Fix A: Power-cycle the ATT gateway

This is the most effective first step and resolves approximately 60% of 'ATT connected without internet' cases by clearing the gateway's WAN DHCP/PPPoE session and NAT table.

Unplug the power cable from the ATT gateway (BGW320, BGW210, or similar).
Wait a full 60 seconds — not 10 seconds. The capacitors need time to fully discharge so the session state is cleared upstream.
Reconnect power. Wait for all LEDs to stabilize (typically 2–3 minutes).
Reconnect your device to WiFi and retest.

Fix B: Release and renew IP address on your device

If your device obtained an APIPA (169.254.x.x) address or you suspect a stale DHCP lease:

Windows:

ipconfig /release
ipconfig /renew

macOS:

sudo ipconfig set en0 DHCP

Or: System Preferences → Network → Advanced → TCP/IP → Renew DHCP Lease.

Linux:

sudo dhclient -r wlan0
sudo dhclient wlan0

Fix C: Flush DNS cache and change DNS servers

Windows:

ipconfig /flushdns
netsh interface ip set dns "Wi-Fi" static 8.8.8.8
netsh interface ip add dns "Wi-Fi" 8.8.4.4 index=2

macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Then: System Preferences → Network → Advanced → DNS → Add 8.8.8.8 and 8.8.4.4.

Linux:

sudo systemd-resolve --flush-caches

Fix D: Reset Winsock and TCP/IP stack (Windows only)

This is necessary when a VPN client, third-party firewall, or Windows update has corrupted the network stack:

netsh winsock reset
netsh int ip reset resetlog.txt
ipconfig /release
ipconfig /flushdns
ipconfig /renew

Reboot after running these commands. Windows will rebuild the Winsock catalog on next boot.

Fix E: Forget and rejoin the WiFi network

A corrupted 802.11 security association can cause a 'connected but no internet' state:

On Windows: Settings → Network & Internet → Wi-Fi → Manage known networks → Select ATT network → Forget.
Reconnect by selecting the SSID and entering your WiFi password.

Fix F: ATT gateway factory reset

Use this only after all other fixes fail. Locate the reset pinhole on the back of the ATT gateway. Insert a paperclip and hold for 10–15 seconds until the LEDs flash. The gateway will reboot with factory defaults. You will need to reconfigure your WiFi name and password.

Fix G: Check for ATT service outages

Visit https://www.att.com/internet/outage/ or check ATT's outage map. If there is a known outage in your area, no local fix will restore internet — wait for ATT to resolve the network issue.

Step 3: Prevent Recurrence

Enable auto-reboot schedule: Log into the ATT gateway UI at http://192.168.1.254 → Home Network → Configure → Enable scheduled reboot (weekly at low-traffic hours).
Use static DNS: Set 8.8.8.8/8.8.4.4 or 1.1.1.1/1.0.0.1 on your devices so DNS failures on the ATT gateway do not affect you.
Monitor gateway firmware: ATT Smart Home Manager app alerts you to available firmware updates for the BGW320/BGW210.
Check cable/fiber connections: Ensure the ONT (fiber box) or DSL line at the wall is firmly connected. A loose coax or Ethernet cable between the ONT and gateway is a common cause of intermittent WAN drops.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# =============================================================
# ATT Connected Without Internet - Full Diagnostic & Fix Script
# Run on: Linux / macOS (run PowerShell version on Windows)
# Usage: sudo bash att_no_internet_fix.sh
# =============================================================

ATT_GATEWAY_IP="192.168.1.254"
TEST_PUBLIC_IP="8.8.8.8"
TEST_DNS_HOST="google.com"
WIFI_IFACE=$(ip route | grep default | awk '{print $5}' 2>/dev/null || echo "wlan0")

echo "===== ATT Internet Diagnostic ====="
echo "Interface: $WIFI_IFACE"
echo ""

# Step 1: Show current IP assignment
echo "--- Current IP Configuration ---"
ip addr show "$WIFI_IFACE" | grep -E 'inet |link/ether'
echo ""

# Step 2: Check for APIPA address (169.254.x.x = DHCP failure)
CURRENT_IP=$(ip addr show "$WIFI_IFACE" | grep 'inet ' | awk '{print $2}' | cut -d'/' -f1)
if echo "$CURRENT_IP" | grep -q '^169\.254\.'; then
  echo "[WARN] APIPA address detected ($CURRENT_IP) - DHCP failed!"
elif [ -z "$CURRENT_IP" ]; then
  echo "[ERROR] No IP address assigned on $WIFI_IFACE"
else
  echo "[OK] IP address: $CURRENT_IP"
fi
echo ""

# Step 3: Ping the ATT gateway
echo "--- Pinging ATT Gateway ($ATT_GATEWAY_IP) ---"
if ping -c 3 -W 2 "$ATT_GATEWAY_IP" > /dev/null 2>&1; then
  echo "[OK] Gateway is reachable"
else
  echo "[FAIL] Cannot reach ATT gateway at $ATT_GATEWAY_IP"
  echo "       -> Check WiFi connection and gateway power"
fi
echo ""

# Step 4: Ping public internet (bypass DNS)
echo "--- Pinging Public IP ($TEST_PUBLIC_IP) ---"
if ping -c 3 -W 3 "$TEST_PUBLIC_IP" > /dev/null 2>&1; then
  echo "[OK] Public internet reachable via IP"
else
  echo "[FAIL] Cannot reach $TEST_PUBLIC_IP - ATT WAN connection may be down"
  echo "       -> Power-cycle the ATT gateway (unplug 60 seconds)"
fi
echo ""

# Step 5: DNS resolution test
echo "--- DNS Resolution Test ---"
if host "$TEST_DNS_HOST" > /dev/null 2>&1; then
  echo "[OK] DNS resolution working"
else
  echo "[FAIL] DNS resolution failed for $TEST_DNS_HOST"
  echo "       -> Attempting to use Google DNS (8.8.8.8) as workaround:"
  if host "$TEST_DNS_HOST" 8.8.8.8 > /dev/null 2>&1; then
    echo "       -> Google DNS works. ATT gateway DNS is broken."
    echo "       -> Applying fix: setting DNS to 8.8.8.8 via resolvconf..."
    # Add fallback DNS (systemd-resolved)
    if command -v systemd-resolve &> /dev/null; then
      sudo resolvectl dns "$WIFI_IFACE" 8.8.8.8 8.8.4.4
      sudo resolvectl domain "$WIFI_IFACE" '~.'
      echo "       -> DNS updated via systemd-resolved"
    fi
  else
    echo "       -> DNS completely unreachable. Likely ATT WAN outage."
  fi
fi
echo ""

# Step 6: Attempt DHCP renewal
echo "--- Renewing DHCP Lease on $WIFI_IFACE ---"
if command -v dhclient &> /dev/null; then
  sudo dhclient -r "$WIFI_IFACE" 2>/dev/null
  sleep 2
  sudo dhclient "$WIFI_IFACE" 2>/dev/null
  echo "[OK] DHCP lease renewal attempted"
elif command -v dhcpcd &> /dev/null; then
  sudo dhcpcd -k "$WIFI_IFACE" 2>/dev/null
  sleep 2
  sudo dhcpcd "$WIFI_IFACE" 2>/dev/null
  echo "[OK] DHCP renewal via dhcpcd"
else
  echo "[SKIP] No DHCP client found (dhclient/dhcpcd)"
fi
echo ""

# Step 7: Flush DNS cache
echo "--- Flushing DNS Cache ---"
if command -v systemd-resolve &> /dev/null; then
  sudo systemd-resolve --flush-caches && echo "[OK] systemd-resolved cache flushed"
elif command -v dscacheutil &> /dev/null; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder && echo "[OK] macOS DNS cache flushed"
else
  echo "[SKIP] Cannot flush DNS cache - manual method required"
fi
echo ""

# Step 8: Final connectivity check
echo "--- Final Connectivity Check ---"
if ping -c 3 -W 3 "$TEST_PUBLIC_IP" > /dev/null 2>&1; then
  echo "[SUCCESS] Internet connectivity restored!"
else
  echo "[FAIL] Internet still not available. Next steps:"
  echo "  1. Power-cycle ATT gateway: unplug power for 60 seconds"
  echo "  2. Check ATT outage map: https://www.att.com/internet/outage/"
  echo "  3. Check gateway status at http://192.168.1.254"
  echo "  4. Call ATT support: 800-288-2020"
fi
echo ""
echo "===== Diagnostic Complete ====="

# --- WINDOWS POWERSHELL EQUIVALENT (copy to fix_att_no_internet.ps1) ---
# # Run as Administrator in PowerShell:
# ipconfig /release
# ipconfig /flushdns
# ipconfig /renew
# netsh winsock reset
# netsh int ip reset C:\resetlog.txt
# netsh interface ip set dns "Wi-Fi" static 8.8.8.8
# netsh interface ip add dns "Wi-Fi" 8.8.4.4 index=2
# Write-Host "Reboot your computer to complete Winsock reset."
# Restart-Computer -Confirm

Error Medic Editorial

Error Medic Editorial is a team of senior DevOps engineers, SREs, and network specialists with 10+ years of experience diagnosing infrastructure failures, consumer networking issues, and ISP-level connectivity problems. Our guides are built from real incident post-mortems, tier-3 support escalations, and hands-on lab testing with consumer and enterprise networking equipment from ATT, Cisco, Ubiquiti, and more.

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.