Why does my AT&T WiFi show 'Connected' but I have no internet access?

This happens because WiFi connection and internet access are two separate layers. Your device successfully connected to the AT&T gateway's local network (WiFi signal), but the gateway itself has lost its connection to AT&T's upstream network — or your device failed to get a valid IP address via DHCP. Start by checking if other devices on the same network also lack internet. If yes, power-cycle the gateway. If no, run 'ipconfig /release && ipconfig /renew' on Windows or renew DHCP on your device.

My AT&T gateway Broadband light is red or blinking — what does that mean?

A red or blinking amber/orange Broadband LED on AT&T gateways (BGW320, BGW210, NVG589) indicates the WAN uplink has failed. This is typically caused by: (1) an AT&T network outage in your area, (2) a failed EAPOL/802.1X authentication with AT&T's ONT or DSLAM, (3) a loose or damaged fiber/DSL cable, or (4) unpaid account suspension. Check your fiber or DSL cable connections first, then visit att.com/outages. If the light remains red after a gateway reboot, call AT&T at 1-800-288-2020.

How do I fix 'att no internet connection' on an iPhone or Android phone?

On iPhone: Go to Settings → WiFi → tap the (i) next to your AT&T network → tap 'Renew Lease' → wait 30 seconds. If that fails, toggle WiFi off and back on, or go to Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings (note: this forgets all saved WiFi passwords). On Android: Go to Settings → Network & Internet → WiFi → long-press your AT&T network → tap 'Forget' → reconnect. Also try toggling Airplane Mode on for 10 seconds then off, which forces a full network re-registration.

Can AT&T throttle my connection to the point of appearing to have no internet?

Yes, but it's uncommon to cause a complete blackout. AT&T may deprioritize or throttle speeds if you exceed data thresholds on certain plans. However, true throttling typically results in very slow speeds rather than zero connectivity. If you see error messages like 'Connected, no internet' or 'No network access', that is not throttling — that is a connectivity failure. To test throttling: run a speed test at fast.com (Netflix's test avoids most ISP throttle exemptions) and compare to your plan speed. Genuine throttling will show reduced Mbps, not zero.

What IP address and login do I use for the AT&T router admin page?

The AT&T gateway admin page is accessed at http://192.168.1.254 (not 192.168.0.1 like many other routers). The username is typically 'admin' and the password is the Device Access Code printed on the label on the side or bottom of your gateway. On newer BGW320 gateways, the label shows a QR code and the access code explicitly. Do not confuse this with your AT&T account password — it is a local device password. If you have changed and forgotten the password, a factory reset is required to restore default credentials.

AT&T No Internet Connection: Fix 'Connected to WiFi But No Internet Access' (2024 Guide)

Fix AT&T no internet connection errors fast. Step-by-step guide covering router resets, DNS fixes, IP conflicts, and AT&T gateway troubleshooting commands.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,246 words

Key Takeaways

Root Cause 1: AT&T gateway or BGW320/BGW210 router firmware glitch causing DHCP lease failure — device shows 'connected' but IP assignment fails or returns 169.254.x.x (APIPA address)
Root Cause 2: DNS resolution failure — AT&T DNS servers (68.94.156.1, 68.94.157.1) become unreachable or return SERVFAIL, causing no internet access despite active WiFi signal
Root Cause 3: WAN port authentication failure on AT&T fiber (EAPOL/802.1X handshake drops), losing upstream connectivity without dropping local WiFi SSID
Root Cause 4: IP address conflict or stale ARP cache causing routing loops on the local network segment
Quick Fix Summary: Power-cycle the AT&T gateway (unplug 60 seconds), flush DNS cache, release/renew DHCP lease, and verify WAN status at 192.168.1.254 — resolves 80%+ of cases within 5 minutes

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle AT&T gateway	First step for any AT&T no internet connection; clears firmware glitches, renews WAN DHCP	2-5 min	None — safe for all users
Release/Renew DHCP on client device	Device shows 169.254.x.x IP or 'no internet access' despite gateway being online	1-2 min	None — temporary disconnect only
Flush DNS cache (ipconfig /flushdns or systemd-resolved)	Websites fail to load but ping to IP (e.g., 8.8.8.8) succeeds; stale DNS entries	30 sec	Very Low — clears cached records
Change DNS servers to 8.8.8.8 / 1.1.1.1	AT&T DNS servers are down or returning SERVFAIL errors persistently	2-3 min	Low — may slightly change routing behavior
Factory reset AT&T BGW320/BGW210 gateway	All other fixes fail, gateway admin page unreachable, persistent WAN auth failure	15-30 min	High — erases all custom config, requires reconfiguration
AT&T Smart Home Manager / Restart via app	Remote restart needed without physical access to gateway device	3-5 min	None — equivalent to soft reboot
Check for AT&T network outage (att.com/outages)	Multiple devices on same network all lack internet simultaneously	2 min	None — diagnostic only, no changes made
Re-authenticate WAN / call AT&T support	Gateway shows 'Broadband: Down' or 'Authorization Failure' in admin console	20-60 min	None for user; AT&T provisions from backend

Understanding the AT&T No Internet Connection Error

When your device shows 'Connected' or 'No Internet Access' on an AT&T WiFi network, it means the local WiFi association succeeded (Layer 2 is up), but either Layer 3 (IP/routing) or the WAN uplink itself has failed. This is one of the most common and confusing error states because the WiFi bars appear full while no actual traffic flows.

Common error messages you may see:

Windows: "No Internet Access" or "No network access" in the system tray
macOS: "Wi-Fi has the self-assigned IP address 169.254.x.x and will not be able to connect to the Internet"
Android: "Connected, no internet" badge under the WiFi SSID
iOS: "Privacy Warning" or silent inability to load pages
AT&T Gateway Admin (192.168.1.254): "Broadband: Down", "Authorization: Failure", or "WAN IP: 0.0.0.0"

Step 1: Confirm the Scope of the Problem

Before touching any settings, determine if the problem is:

One device only — points to client-side DHCP/DNS/driver issue
All devices on WiFi — points to gateway WiFi config or WAN uplink
WiFi and Ethernet both down — almost certainly WAN or AT&T backend issue

Test on the affected device:

ping 192.168.1.254       # Can you reach the gateway?
ping 8.8.8.8             # Can you reach the internet by IP?
nslookup google.com      # Does DNS resolve?

If ping 192.168.1.254 fails → DHCP/local network issue. If ping 8.8.8.8 works but nslookup google.com fails → DNS-only issue. If both fail → gateway WAN or AT&T upstream issue.

Step 2: Power-Cycle the AT&T Gateway (Most Effective First Step)

The AT&T BGW320, BGW210, and older NVG589/NVG599 gateways can enter a state where the WAN DHCP lease expires or the EAPOL authentication token drops without rebooting the device automatically.

Unplug the power cord from the AT&T gateway (do NOT use the reset pinhole — that factory resets).
Wait a full 60 seconds (not 10 — capacitors need to drain).
Plug power back in and wait up to 3 minutes for full boot.
Watch the Broadband light: Green = WAN connected. Blinking amber/red = still negotiating or failed.
On BGW320: Check the front LED — solid green means fully operational.

If the Broadband light never turns green after 5 minutes, proceed to Step 4.

Step 3: Fix Client-Side DHCP and DNS Issues

If the gateway is online (Broadband light green) but one or more devices still show no internet:

On Windows:

ipconfig /release
ipconfig /flushdns
ipconfig /renew
nbtstat -R
netsh winsock reset
netsh int ip reset

Restart the computer after running these commands.

On macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
# Renew DHCP via System Settings > Network > WiFi > Details > Renew DHCP Lease

On Linux (Ubuntu/Debian with systemd-resolved):

sudo systemd-resolve --flush-caches
sudo dhclient -r wlan0 && sudo dhclient wlan0

Verify your IP is valid (not 169.254.x.x):

Windows: ipconfig — look for IPv4 Address under your WiFi adapter
macOS/Linux: ifconfig or ip addr show
A 169.254.x.x address means DHCP failed; the device self-assigned an APIPA address

Step 4: Check and Change DNS Servers

AT&T's default DNS servers are 68.94.156.1 and 68.94.157.1. These occasionally experience outages. You can test and switch:

# Test if AT&T DNS responds
nslookup google.com 68.94.156.1

# Test Google DNS as alternative
nslookup google.com 8.8.8.8

If AT&T DNS times out but Google DNS works, change your DNS:

Windows: Control Panel → Network Adapter → IPv4 Properties → Set DNS to 8.8.8.8 and 1.1.1.1
macOS: System Settings → Network → WiFi → Details → DNS → Add 8.8.8.8
AT&T Gateway Level: Log in to http://192.168.1.254 → Settings → LAN → DHCP → Override DNS servers

Step 5: Access the AT&T Gateway Admin Console

Navigate to http://192.168.1.254 in your browser (default for most AT&T gateways). The default admin credentials are printed on the gateway label (usually Device Access Code).

Check:

Broadband > Status — Should show 'Connected' with a valid WAN IP
Home Network > WiFi — Confirm SSID is broadcasting on correct band
Diagnostics > Ping Test — Run a ping to 8.8.8.8 from the gateway itself

If the gateway-level ping fails, the problem is definitively upstream (AT&T WAN or their network).

Step 6: Check for AT&T Outages

Visit https://www.att.com/support/article/u-verse/KM1010453 or use the AT&T Smart Home Manager app to check for reported outages in your area. You can also check:

curl -s https://downdetector.com/status/att/ | grep -i 'outage\|down'

Or call AT&T at 1-800-288-2020 and follow prompts for internet support — the automated system will tell you if there is a known outage at your address.

Step 7: Factory Reset (Last Resort)

Only do this if all other steps fail AND you have your AT&T account credentials and WiFi configuration documented.

Locate the Reset pinhole on the back of the gateway.
With the gateway powered on, use a paperclip to press and hold for 10 seconds.
The gateway will reboot. Wait 5 minutes.
Reconnect using credentials on the gateway label.
Reconfigure any custom settings (port forwarding, IP passthrough, etc.).

After factory reset, if WAN still shows 'Authorization Failure', AT&T must re-provision your line from the backend — call support.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# AT&T No Internet Connection - Diagnostic & Fix Script
# Run on the affected client machine (macOS/Linux)
# For Windows equivalents, see comments marked [WIN]

echo "============================="
echo " AT&T Network Diagnostic Tool"
echo "============================="

# 1. Show current IP configuration
echo "\n[1] Current IP Configuration:"
ip addr show 2>/dev/null || ifconfig  # Linux / macOS
# [WIN] ipconfig /all

# 2. Check for APIPA address (169.254.x.x = DHCP failure)
APIPA=$(ip addr show | grep '169.254' | awk '{print $2}')
if [ -n "$APIPA" ]; then
  echo "WARNING: APIPA address detected ($APIPA) -- DHCP has failed!"
  echo "ACTION: Releasing and renewing DHCP lease..."
  IFACE=$(ip route | grep default | awk '{print $5}' | head -n1)
  sudo dhclient -r "$IFACE" 2>/dev/null
  sleep 2
  sudo dhclient "$IFACE" 2>/dev/null
else
  echo "OK: Valid IP address assigned."
fi

# 3. Ping the AT&T gateway
echo "\n[2] Pinging AT&T Gateway (192.168.1.254):"
ping -c 4 192.168.1.254
# [WIN] ping 192.168.1.254

# 4. Ping internet by IP (bypasses DNS)
echo "\n[3] Pinging Google DNS by IP (8.8.8.8) -- no DNS needed:"
ping -c 4 8.8.8.8
# [WIN] ping 8.8.8.8

# 5. DNS resolution test using AT&T DNS
echo "\n[4] DNS Test using AT&T DNS server (68.94.156.1):"
nslookup google.com 68.94.156.1
# [WIN] nslookup google.com 68.94.156.1

# 6. DNS resolution test using Google DNS
echo "\n[5] DNS Test using Google DNS (8.8.8.8):"
nslookup google.com 8.8.8.8
# [WIN] nslookup google.com 8.8.8.8

# 7. Flush DNS cache (Linux systemd)
echo "\n[6] Flushing DNS Cache:"
if command -v systemd-resolve &> /dev/null; then
  sudo systemd-resolve --flush-caches
  echo "systemd-resolved cache flushed."
elif command -v dscacheutil &> /dev/null; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
  echo "macOS DNS cache flushed."
fi
# [WIN] ipconfig /flushdns

# 8. Traceroute to check where traffic dies
echo "\n[7] Traceroute to 8.8.8.8 (where does the connection drop?):"
traceroute -m 15 8.8.8.8 2>/dev/null || tracepath 8.8.8.8
# [WIN] tracert 8.8.8.8

# 9. Check current default route
echo "\n[8] Default Route (should point to 192.168.1.254):"
ip route show default 2>/dev/null || netstat -rn | grep default
# [WIN] route print

# 10. Check AT&T outage status via curl
echo "\n[9] Checking ATT outage reports (downdetector):"
curl -s --max-time 5 -o /dev/null -w "HTTP Status: %{http_code}\n" https://downdetector.com/status/att/

# 11. Try setting DNS temporarily to 8.8.8.8 for testing
echo "\n[10] Testing connectivity with Google DNS override:"
curl --dns-servers 8.8.8.8 -s -o /dev/null -w "HTTP Status via Google DNS: %{http_code}\n" https://www.google.com 2>/dev/null \
  || curl -s --max-time 5 -o /dev/null -w "HTTP Status: %{http_code}\n" https://www.google.com

echo "\n============================"
echo " Diagnostic Complete"
echo "============================"
echo "If gateway ping fails: power-cycle the AT&T gateway."
echo "If IP ping works but DNS fails: change DNS to 8.8.8.8 / 1.1.1.1."
echo "If both fail: check att.com/outages or call 1-800-288-2020."

Error Medic Editorial

Error Medic Editorial is a team of senior DevOps engineers, SREs, and network administrators with 10+ years of experience troubleshooting ISP connectivity issues, home networking, and enterprise infrastructure. Our guides are written and peer-reviewed by practitioners who have diagnosed thousands of real-world connectivity failures across AT&T, Comcast, Verizon, and other major carriers. We prioritize actionable, command-level guidance over generic advice.

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.