Why does my AT&T Wi-Fi say 'Connected, No Internet' even after restarting?

This usually means the gateway itself lost its WAN connection to AT&T's network even though your local Wi-Fi association is fine. After restarting, check the gateway admin page at http://192.168.1.254 and look at the Broadband status. If it shows 'Disconnected' or is stuck 'Authenticating', the issue is a line fault, a PPPoE authentication failure, or an AT&T outage. Run a line test by calling AT&T or using the Smart Home Manager app. If the broadband LED on the gateway is red or blinking amber after a full restart, an AT&T technician visit is likely required.

My AT&T Wi-Fi is connected but only some devices have no internet — why?

When only specific devices lose internet while others work, the problem is almost always device-specific: a bad DHCP lease (check for a 169.254.x.x IP), a corrupted DNS cache, or an incorrect static IP configured on the affected device. On the problematic device, run 'ipconfig /release && ipconfig /renew' (Windows) or 'sudo ipconfig set en0 DHCP' (macOS) to force a fresh DHCP lease. Also try setting DNS manually to 8.8.8.8. If one device consistently fails, check if its MAC address is blocked in the AT&T gateway's MAC filter settings under Firewall > Advanced.

Can a VPN or proxy cause the 'ATT connected without internet' symptom?

Yes. An active VPN client or proxy misconfiguration can cause your device to show a Wi-Fi connection but fail all internet tests because all traffic is being routed through the VPN tunnel and the VPN server is unreachable or refusing connections. Disable your VPN, proxy settings, or any 'Always-on VPN' profiles in your OS network settings and test again. On Windows, go to Settings > Network & Internet > VPN and disconnect. On macOS, check System Settings > VPN. On Android/iOS, check Settings > VPN.

How do I fix AT&T connected without internet on my iPhone or Android phone?

On iPhone: Go to Settings > Wi-Fi, tap the (i) next to your AT&T network, scroll down and tap 'Renew Lease', then tap 'Forget This Network' if the problem persists, and reconnect. Also try Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings (warning: this forgets all Wi-Fi passwords). On Android: Go to Settings > Wi-Fi, long-press your network, select 'Forget', reconnect, and use 'Modify Network' to set DNS to 8.8.8.8 under Advanced options. You can also toggle Airplane Mode on for 10 seconds then off to force a fresh network connection.

The AT&T gateway admin page (192.168.1.254) shows broadband is connected, but I still have no internet — what now?

If the gateway reports WAN connectivity but you still cannot reach the internet, run the built-in Diagnostics Ping test from the gateway admin page targeting 8.8.8.8. If that fails, there may be a routing or NAT table corruption on the gateway itself requiring a factory reset. If the gateway ping succeeds, the issue is isolated to your device: flush DNS with 'ipconfig /flushdns' (Windows) or 'sudo dscacheutil -flushcache' (macOS), change DNS to 1.1.1.1, and check that no firewall software on your device is blocking outbound traffic. Also check if your browser has a misconfigured proxy under its network/connection settings.

ATT Connected Without Internet: Why Your AT&T Wi-Fi Shows Connected But Has No Internet Access

Fix AT&T Wi-Fi connected without internet errors. Step-by-step guide covering gateway resets, DNS fixes, IP conflicts, and firmware issues. Restore access fast.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,575 words

Key Takeaways

Root cause 1: DHCP lease failure or IP address conflict — your device receives a private IP but the AT&T gateway cannot route traffic to the WAN, often shown as '169.254.x.x' (APIPA) or a stale lease from a previous session.
Root cause 2: AT&T gateway firmware bug or stuck NAT/firewall state — the BGW320, BGW210, or NVG5x9 series can enter a half-open state where the LAN side appears healthy but the WAN PPPoE/DSL session has silently dropped, returning no upstream connectivity.
Quick fix summary: Power-cycle the AT&T gateway (unplug for 60 seconds), flush DNS and renew IP on your device, verify WAN status at 192.168.1.254, and if the problem persists perform a factory reset or contact AT&T to check for line issues or provisioning errors on their end.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle the AT&T gateway	First step for any 'connected without internet' symptom; clears stuck NAT/PPPoE state	2-5 min	None — safest first option
Renew IP / flush DNS on client device	Device shows 169.254.x.x or wrong subnet; DNS errors in browser	1-2 min	None
Change DNS servers to 8.8.8.8 / 1.1.1.1	Pages fail to load but ping to IP works; ISP DNS is down or slow	2 min	Low — may bypass parental controls
Check and reassign DHCP range in gateway settings	Multiple devices affected; DHCP pool exhausted	5-10 min	Low — requires gateway admin access
Update AT&T gateway firmware via Smart Home Manager	Recurring issue after firmware update notification; known bugs in release notes	10-20 min	Low — gateway reboots during update
Factory reset the AT&T gateway	All other fixes fail; gateway settings corrupted	15-30 min	Medium — wipes Wi-Fi passwords and custom settings
Contact AT&T support / technician visit	WAN light is red/off; outage confirmed; provisioning issue on AT&T side	1-48 hrs	None on your end

Understanding the 'ATT Connected Without Internet' Error

When your device shows a Wi-Fi connection to your AT&T network but browsers display errors like 'No internet access', 'ERR_NAME_NOT_RESOLVED', 'DNS_PROBE_FINISHED_NO_INTERNET', or simply a yellow exclamation triangle on Windows, it means your device successfully associated with the AT&T gateway's wireless radio — but somewhere between your device and the public internet, traffic is being dropped.

This is a fundamentally different problem from not being able to connect to Wi-Fi at all. The local network (LAN) is working; the failure is in the path from the gateway to AT&T's network (WAN) or in how your device resolves names and routes packets.

Layer-by-Layer Diagnosis Framework

Think of internet connectivity as a stack of layers. To fix the problem efficiently, confirm each layer from the bottom up:

Physical layer — Is the gateway powered on? Are the correct LEDs lit? AT&T BGW320/BGW210 should show a solid green or white broadband light.
IP/DHCP layer — Did your device receive a valid private IP (e.g., 192.168.1.x)? A 169.254.x.x address means DHCP failed.
Gateway reachability — Can you ping the default gateway (192.168.1.254)?
WAN/upstream layer — Is the gateway itself reaching AT&T's network? Check the gateway's status page.
DNS layer — Can your device resolve domain names? DNS failure shows as connectivity even when pings to IPs work.
Firewall/routing layer — Are custom firewall rules or IP Passthrough settings blocking traffic?

Step 1: Check Your Device's IP Address

Open a terminal or command prompt and run the appropriate command for your OS (see the code block section). You are looking for:

Valid IP: 192.168.1.x or 192.168.0.x — DHCP is working on the LAN side.
APIPA IP (169.254.x.x): Your device could not get a DHCP lease. The gateway may be overloaded, the DHCP pool may be exhausted, or there is a firmware issue.
Wrong subnet: If you have a secondary router or mesh node, you may have a double-NAT situation.

If you see 169.254.x.x, first try releasing and renewing your IP (commands in the code block). If the problem persists across multiple devices, the gateway's DHCP server is the culprit.

Step 2: Check the AT&T Gateway Status Page

Open a browser on any device connected to the AT&T network and navigate to http://192.168.1.254 (the default gateway admin page for most AT&T residential gateways including BGW320, BGW210, NVG589, NVG599).

Home > Broadband > Status: Look for 'Connected' under the broadband/DSL line. If it shows 'Disconnected', 'Authenticating', or 'Syncing', the problem is on the WAN side — likely a line issue, a PPPoE credential problem, or an AT&T outage.
Home > Wi-Fi: Confirm your SSID is listed and enabled.
Home > Diagnostics > Ping Test: Use the built-in ping tool to test 8.8.8.8. If pings from the gateway itself fail, the WAN connection is down regardless of what your devices show.

Important gateway LED indicators:

BGW320: Solid white/green = normal. Blinking amber = no broadband sync. Solid red = hardware fault.
BGW210: Solid green broadband LED = WAN up. Blinking green = syncing. Off = no signal.
NVG5x9 series: Green 'Broadband' LED = WAN up. Red = no WAN connection.

Step 3: Power-Cycle the AT&T Gateway

This is the most effective single action for resolving stuck PPPoE sessions, stale NAT tables, or frozen firmware states.

Unplug the gateway's power cable from the wall (do not use the power button — a full power removal clears capacitors).
Wait 60 full seconds.
Plug the power cable back in.
Wait 3-5 minutes for the gateway to fully boot and re-establish the WAN connection.
Reconnect your device to Wi-Fi and retest.

If you have an Optical Network Terminal (ONT) for AT&T Fiber (a white box usually near where fiber enters the home), power-cycle it before the gateway — unplug ONT, wait 30 seconds, plug ONT back in, wait 60 seconds, then power-cycle the gateway.

Step 4: Flush DNS Cache and Renew IP on Your Device

Even after the gateway is healthy, your device may cache bad DNS responses or hold a stale IP lease. See the code block for the exact commands for Windows, macOS, and Linux.

After flushing, test by opening a terminal and running:

nslookup google.com 8.8.8.8

If this resolves successfully but your browser still fails, the issue is with your system's default DNS server. Change your DNS settings to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) in your network adapter settings.

Step 5: Check for IP Passthrough or DMZ Conflicts

If you have a third-party router (Eero, Netgear, Asus, etc.) connected to the AT&T gateway, and you have configured IP Passthrough (also called DMZ or Cascaded Router mode) in the AT&T gateway settings, a misconfiguration can cause the gateway to pass the WAN IP to the wrong device or to no device, breaking internet access.

Navigate to http://192.168.1.254 > Firewall > IP Passthrough and verify:

The allocation mode is set to the correct device's MAC address.
If you don't use a separate router, IP Passthrough should be disabled.
After any change, save and reboot the gateway.

Step 6: Check for an AT&T Outage

If all device-side and gateway-side checks pass (valid IP, gateway reachable, WAN status shows 'Connected' at the gateway admin page) but you still have no internet, the issue may be upstream at AT&T.

Visit downdetector.com/status/at-t from a mobile data connection to check for reported outages.
Log into the AT&T Smart Home Manager app (available on iOS and Android) — it will flag known outages in your area.
Call AT&T at 1-800-288-2020 and ask for a line test.

Step 7: Factory Reset as Last Resort

If firmware corruption or a deeply misconfigured gateway is suspected and all else fails:

Locate the red Reset button on the back of your AT&T gateway.
Use a pin or paperclip to hold it down for 10-15 seconds until all lights flash.
Wait 5-10 minutes for the gateway to fully restore factory settings and re-provision.
Reconnect using the Wi-Fi credentials printed on the gateway label.
Reconfigure any custom settings (port forwarding, IP Passthrough, DNS overrides).

Warning: A factory reset will erase all custom Wi-Fi network names (SSIDs), passwords, and firewall rules. Note these down before proceeding.

Frequently Asked Questions

bash

# ============================================================
# AT&T Connected Without Internet - Diagnostic & Fix Commands
# ============================================================

# --- WINDOWS (Run Command Prompt as Administrator) ---

# 1. Check current IP address and gateway
ipconfig /all
# Look for: IPv4 Address (should be 192.168.1.x), Default Gateway (192.168.1.254)
# If IP is 169.254.x.x, DHCP has failed - run steps below

# 2. Release and renew IP address
ipconfig /release
ipconfig /renew

# 3. Flush DNS cache
ipconfig /flushdns

# 4. Reset TCP/IP stack (for stubborn issues)
netsh int ip reset
netsh winsock reset
# Reboot after running these two commands

# 5. Set DNS to Google (replace 'Wi-Fi' with your adapter name if different)
netsh interface ip set dns name="Wi-Fi" static 8.8.8.8
netsh interface ip add dns name="Wi-Fi" 8.8.8.8 index=2

# 6. Ping tests (run in order)
ping 192.168.1.254        # Can you reach the AT&T gateway?
ping 8.8.8.8              # Can you reach internet by IP? (bypasses DNS)
ping google.com           # Can DNS resolve correctly?

# 7. Trace route to identify where packets are dropped
tracert 8.8.8.8
# Packets should pass 192.168.1.254 (gateway) then AT&T hops
# If it stops at 192.168.1.254, the gateway has no WAN connection

# 8. Check DNS resolution directly
nslookup google.com
nslookup google.com 8.8.8.8
nslookup google.com 1.1.1.1

# --- macOS / Linux ---

# 1. Check current IP and routing table
ifconfig           # macOS - look for en0 (Wi-Fi) inet address
ip addr show       # Linux - look for wlan0 or wlp2s0 inet address

# 2. View routing table
netstat -rn        # Both macOS and Linux
# Confirm a default route (0.0.0.0) points to 192.168.1.254

# 3. Release and renew DHCP lease
# macOS:
sudo ipconfig set en0 DHCP
# Or: System Settings > Network > Wi-Fi > Details > TCP/IP > Renew DHCP Lease

# Linux (replace wlan0 with your interface):
sudo dhclient -r wlan0 && sudo dhclient wlan0

# 4. Flush DNS cache
# macOS Ventura/Sonoma/Sequoia:
sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
# macOS Big Sur / Monterey:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
# Linux (systemd-resolved):
sudo systemd-resolve --flush-caches
# Linux (nscd):
sudo service nscd restart

# 5. Set DNS to Cloudflare (macOS example - adapt for your interface)
sudo networksetup -setdnsservers Wi-Fi 1.1.1.1 8.8.8.8
# Verify:
scutil --dns

# 6. Ping tests
ping -c 4 192.168.1.254   # Gateway reachable?
ping -c 4 8.8.8.8         # Internet by IP?
ping -c 4 google.com      # DNS resolution?

# 7. Traceroute
traceroute 8.8.8.8        # macOS/Linux
# Windows equivalent: tracert 8.8.8.8

# --- GATEWAY QUICK CHECK (any OS with a browser) ---
# Navigate to: http://192.168.1.254
# Login with AT&T credentials (printed on gateway label)
# Check: Home > Broadband > Status for WAN connectivity
# Check: Home > Diagnostics > Ping > target 8.8.8.8

# --- ADVANCED: Check if DNS is the only issue ---
# If pinging 8.8.8.8 works but google.com does NOT, DNS is broken
# Temporary fix - edit /etc/hosts (Linux/macOS) or C:\Windows\System32\drivers\etc\hosts
# OR change adapter DNS settings as shown above

# --- ADVANCED: Check for APIPA (self-assigned) IP ---
# APIPA range: 169.254.0.0/16 means DHCP failed
# Steps: power-cycle gateway, rejoin Wi-Fi, run ipconfig /renew or dhclient

# --- AT&T GATEWAY FACTORY RESET (last resort) ---
# Physical reset:
# 1. Press and hold the red Reset button on the gateway for 10-15 seconds
# 2. All LEDs will flash - release the button
# 3. Wait 5-10 minutes for full reboot and re-provisioning
# 4. Reconnect using Wi-Fi credentials on the gateway label
echo "After factory reset, reconnect using credentials on the gateway label"
echo "Gateway admin page: http://192.168.1.254"

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps and SRE engineers with 10+ years of experience diagnosing network, infrastructure, and connectivity issues across enterprise and residential environments. We specialize in translating cryptic error messages into clear, actionable troubleshooting steps for both technical and non-technical audiences. 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.