Why does my AT&T WiFi say 'connected' but I have no internet on only one device?

When only one device is affected, the problem is almost always device-side: a stale DHCP lease (the device held onto an expired IP), a corrupted DNS cache, or a software-level network stack issue. Start with 'ipconfig /release && ipconfig /renew' on Windows or 'Renew DHCP Lease' on macOS. Then flush the DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS). If the device received a 169.254.x.x address, the DHCP request failed entirely — disable and re-enable the WiFi adapter to force a fresh DHCP discovery.

My AT&T BGW320 (or BGW210) is connected but shows no internet — what should I check first?

Log into the gateway at http://192.168.1.254 and check the Broadband status under the Home Network or Diagnostics section. If it shows 'Disconnected' or 'Authenticating', the WAN PPPoE session has dropped. Power-cycle the gateway (unplug 60 seconds) as the first fix. Also check whether a firmware update is pending under Settings > Diagnostics — AT&T has pushed firmware updates that inadvertently broke WAN sessions on BGW320 units, and a manual reboot after the update completes usually resolves it.

I get ERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_NXDOMAIN on AT&T WiFi — is this the same problem?

Yes, this is a DNS-layer failure that presents as 'connected without internet'. Your device has a valid IP and can route packets, but AT&T's DNS servers (68.94.156.1 and 68.94.157.1) are unreachable or returning errors. Quick fix: change your DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) in your network adapter settings, then flush the DNS cache with 'ipconfig /flushdns' (Windows) or 'sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder' (macOS). If the error clears, AT&T's DNS was the issue — you can leave the alternate DNS in place permanently.

AT&T internet keeps disconnecting every few hours then reconnects — what causes this?

Intermittent drops every few hours typically point to one of three causes: (1) The AT&T gateway's PPPoE session timer — some firmware versions have a session timeout bug; update firmware via the admin page. (2) DSL line quality issues (SNR margin too low, line attenuation too high) — AT&T support can run a remote line test and check signal levels. (3) Overheating of the BGW320/BGW210 — these units run hot; ensure they have 6+ inches of clearance and aren't stacked on other equipment. Check the gateway's uptime under Diagnostics; if it resets to 0 frequently, the device is crashing and rebooting.

After AT&T fiber installation, WiFi is connected but nothing loads — what's wrong?

After a new AT&T fiber installation, 'connected no internet' is most commonly caused by an ONT provisioning issue (the fiber box hasn't been fully activated on AT&T's network yet), or the BGW320 hasn't received its WAN IP via DHCP from the ONT. Wait 15-20 minutes after installation for provisioning to complete. If it still fails: power-cycle both the ONT and gateway in sequence (ONT first, then gateway after 60 seconds). Also verify the WAN light on the ONT is solid green. If activation still fails, call AT&T provisioning at 800-288-2020 — the technician may need to push the activation from their end.

AT&T Connected Without Internet: Full Troubleshooting Guide (WiFi Shows Connected But No Access)

Fix AT&T WiFi connected without internet in minutes. Step-by-step diagnosis: restart gateway, flush DNS, release/renew IP, reset network stack. Works for all AT

Last updated: February 27, 2026

Last verified: February 27, 2026

2,603 words

Key Takeaways

Root cause 1: IP address conflict or DHCP lease failure — your device received an invalid or duplicate IP (often 169.254.x.x APIPA address), preventing actual internet routing even though the WiFi handshake succeeded.
Root cause 2: DNS resolver failure — AT&T's default DNS servers (68.94.156.1 / 68.94.157.1) become unreachable or return NXDOMAIN for all queries, making the internet appear broken while the connection is technically active.
Root cause 3: AT&T BGW320/BGW210/NVG599 gateway firmware bug or session table overflow — the modem-router combo device loses its PPPoE/WAN session or exhausts NAT connection tracking, dropping all outbound traffic while local WiFi associations remain intact.
Quick fix summary: Power-cycle the AT&T gateway (unplug 60 seconds), release and renew your device IP (ipconfig /release && ipconfig /renew on Windows; sudo dhclient -r && sudo dhclient on Linux/Mac), flush DNS cache, and if the problem persists, factory-reset the gateway using the reset pinhole or the Smart Home Manager app.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle AT&T gateway	First step for any 'connected no internet' symptom; clears WAN session drops and firmware hangs	2-3 min	None — no settings lost
Release/Renew IP on device	Device shows 169.254.x.x (APIPA) or 0.0.0.0 IP; DHCP lease failure on single device	< 1 min	None — temporary disconnection only
Flush DNS cache	Websites fail but ping to raw IPs succeeds; browser shows DNS_PROBE_FINISHED_NXDOMAIN	< 30 sec	None — forces fresh DNS lookups
Change DNS servers (8.8.8.8 / 1.1.1.1)	AT&T DNS servers consistently unreachable; ping 68.94.156.1 times out	2 min	Low — reverts AT&T DNS; may expose to public resolvers
Disable/re-enable network adapter	Single device issue; driver or software-level WiFi stack corruption	1 min	Low — brief disconnection
Reset TCP/IP and Winsock stack (Windows)	All other device-side fixes fail; netsh diag shows stack errors	3-5 min + reboot	Low — restores factory network stack
Factory reset AT&T gateway	Gateway config corrupted; all devices affected and power-cycle doesn't help	10-15 min	High — all custom settings (port forwards, SSIDs, passwords) erased
Contact AT&T support / line test	Outage in area; modem light patterns indicate WAN signal loss (red Broadband light)	30+ min	None — diagnostic only

Understanding 'AT&T Connected Without Internet'

When your device shows the WiFi icon as connected — or Windows displays 'Connected, no Internet' / macOS shows the WiFi symbol with an exclamation mark — the 802.11 association with your AT&T gateway is successful, but IP-layer routing to the public internet has failed. These are two distinct layers of networking, and the symptom means the problem lives at Layer 3 (IP) or above, not Layer 2 (WiFi radio).

AT&T residential service uses a combination of a DSL/fiber ONT and a gateway device (commonly the BGW320-500, BGW210-700, NVG599, or NVG589). The gateway handles PPPoE or DHCP authentication with AT&T's network, NAT for your home devices, and the WiFi access point. Any failure in the chain between your device and AT&T's WAN edge will produce this symptom.

Common Error Messages You May See

Windows: "Connected, no Internet access" (yellow triangle on WiFi icon)
Windows 11: "No internet" label beneath the SSID in the network flyout
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" or "Connected (limited)"
Browser: ERR_NAME_NOT_RESOLVED, DNS_PROBE_FINISHED_NXDOMAIN, or ERR_INTERNET_DISCONNECTED
AT&T gateway admin page (192.168.1.254): Broadband status: Disconnected

Step 1: Identify the Scope (Gateway vs. Device)

Before touching any settings, determine whether the problem affects all devices or just one.

Test with a second device: Connect a phone to the same WiFi. If the phone has internet, the issue is device-specific (proceed to Step 4). If the phone also has no internet, the gateway or AT&T WAN is the problem (proceed to Step 2).

Check the gateway's status lights:

BGW320/BGW210: The "Broadband" light should be solid green. Red or amber means no WAN signal — AT&T line issue.
NVG599: The "Broadband" and "Service" lights should both be solid green.
All models: A solid amber/yellow "Service" light often indicates authenticated but degraded service.

Access the gateway admin page: Open a browser and navigate to http://192.168.1.254. Log in (default credentials are printed on the gateway label). Go to Home Network > IP Allocation or Diagnostics > Ping Test and ping 8.8.8.8. If the gateway itself cannot ping 8.8.8.8, the WAN connection is broken.

Step 2: Fix Gateway-Level Issues

Power-cycle the AT&T gateway (most effective first step):

Unplug the power cable from the back of the gateway.
If you have a separate ONT (fiber box, usually on an exterior wall), unplug that too.
Wait a full 60 seconds — this clears the NAT session table, drops the stale PPPoE session, and forces firmware reinitialization.
Plug the ONT back in first. Wait for its lights to stabilize (30-60 sec).
Plug the gateway back in. Wait up to 3 minutes for the Broadband light to turn solid green.

Check for AT&T outages: Visit https://www.att.com/support/article/u-verse/KM1010059 or text myATT to check service status. You can also check https://downdetector.com/status/att for real-time crowd-sourced outage reports.

Update gateway firmware: Log into http://192.168.1.254, navigate to Settings > Diagnostics > Update, and check for pending firmware updates. Firmware bugs in BGW320 versions prior to 3.18.x caused intermittent WAN drops.

Step 3: Fix DHCP / IP Address Issues (All Devices)

If the gateway is online but devices are getting APIPA addresses (169.254.x.x), the DHCP server on the gateway may have exhausted its lease pool or crashed.

On the gateway admin page: Go to Home Network > IP Allocation and check how many leases are active. The default pool on AT&T gateways is 192.168.1.64 to 192.168.1.253 (190 addresses). If you have many IoT devices, you may hit this limit.

Clear DHCP leases: In the gateway admin page, look for Home Network > Subnets & DHCP and click Reboot or temporarily reduce/expand the lease range. Power-cycling the gateway also clears all active leases and forces renegotiation.

Step 4: Fix Device-Level Issues (Single Device Only)

Windows — Release and Renew IP: Open Command Prompt as Administrator and run the commands shown in the code block section below.

macOS — Renew DHCP Lease: Go to System Settings > Network > Wi-Fi > Details > TCP/IP and click Renew DHCP Lease. Or use the terminal command in the code block.

Linux — Restart DHCP client: Use sudo dhclient -r && sudo dhclient or for NetworkManager: sudo nmcli networking off && sudo nmcli networking on.

Flush DNS Cache: Stale DNS cache can cause DNS_PROBE_FINISHED_NXDOMAIN errors even after the connection is restored. See the code block for OS-specific commands.

Change DNS Servers: If AT&T's DNS (68.94.156.1) is the problem, switch to Google DNS (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1) in your network adapter settings.

Windows — Reset TCP/IP and Winsock: If all else fails on a Windows machine, the network stack itself may be corrupted. Run the full reset sequence in the code block (requires administrator privileges and a reboot).

Step 5: Advanced — Packet-Level Diagnosis

If basic fixes don't resolve the issue, use diagnostic commands to pinpoint where routing breaks:

Confirm local gateway reachability: ping 192.168.1.254 — if this fails, you have a local network problem (wrong VLAN, driver issue).
Test WAN hop: Run a traceroute (tracert 8.8.8.8 on Windows, traceroute 8.8.8.8 on Linux/Mac). If the trace stops at the first hop (your gateway) with * * * or timeouts, the WAN is down on the gateway side.
Test DNS separately from routing: nslookup google.com 8.8.8.8 — bypasses AT&T DNS. If this works but normal browsing fails, AT&T's DNS servers are the issue.
Check for IP conflicts: On Windows, run arp -a and look for duplicate MAC addresses on the same IP. On Linux, use arp-scan -l (requires installation).

Step 6: When to Call AT&T Support

Call AT&T (800-288-2020) or use the myAT&T app if:

The gateway Broadband light is red or amber and doesn't recover after a full power-cycle.
traceroute stops at the first external hop (AT&T's equipment).
The AT&T gateway admin page shows Broadband: Disconnected or Authentication Failed.
The issue is intermittent and tied to specific times of day (congestion or scheduled maintenance).
You suspect a line quality issue — AT&T can run a remote line diagnostic and dispatch a technician if signal levels are out of spec.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# AT&T Connected Without Internet - Diagnostic & Fix Script
# Run on the affected device. Windows users: use the
# Windows CMD/PowerShell equivalents provided in comments.
# ============================================================

echo "=== Step 1: Check current IP address ==="
# Linux/macOS:
ip addr show       # Look for 169.254.x.x (APIPA) = DHCP failure
# macOS alternative:
# ifconfig en0 | grep inet
# Windows CMD equivalent:
# ipconfig /all

echo ""
echo "=== Step 2: Ping default gateway ==="
# Linux/macOS - detect gateway automatically:
GATEWAY=$(ip route | grep default | awk '{print $3}' | head -1)
echo "Gateway detected: $GATEWAY"
ping -c 4 "$GATEWAY"
# Windows CMD: ping 192.168.1.254

echo ""
echo "=== Step 3: Ping AT&T DNS servers ==="
ping -c 4 68.94.156.1    # AT&T primary DNS
ping -c 4 68.94.157.1    # AT&T secondary DNS
# Windows CMD: ping 68.94.156.1

echo ""
echo "=== Step 4: Bypass AT&T DNS - test with Google DNS ==="
nslookup google.com 8.8.8.8
# Windows CMD: nslookup google.com 8.8.8.8

echo ""
echo "=== Step 5: Traceroute to public internet ==="
# Linux:
traceroute -n 8.8.8.8 2>/dev/null || tracepath -n 8.8.8.8
# macOS:
# traceroute -n 8.8.8.8
# Windows CMD:
# tracert 8.8.8.8

echo ""
echo "=== Step 6: Check for IP conflicts ==="
arp -n | grep -v incomplete
# Linux (requires arp-scan): sudo arp-scan -l
# Windows CMD: arp -a

echo ""
echo "=== Fix A: Release and Renew DHCP Lease ==="
# Linux (NetworkManager):
sudo nmcli networking off
sleep 3
sudo nmcli networking on
# Linux (dhclient - older systems):
# sudo dhclient -r eth0 && sudo dhclient eth0
# macOS Terminal (replace en0 with your interface - check with: networksetup -listallnetworkservices):
# sudo ipconfig set en0 DHCP
# Windows CMD (run as Administrator):
# ipconfig /release
# ipconfig /renew

echo ""
echo "=== Fix B: Flush DNS Cache ==="
# Linux (systemd-resolved):
sudo systemd-resolve --flush-caches
sudo systemd-resolve --statistics | grep -i cache
# macOS:
# sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
# Windows CMD (run as Administrator):
# ipconfig /flushdns

echo ""
echo "=== Fix C: Set alternate DNS (Cloudflare) ==="
# Linux - edit /etc/resolv.conf (temporary, overwritten by NetworkManager):
# For permanent change via NetworkManager:
# nmcli connection modify "YOUR_WIFI_SSID" ipv4.dns "1.1.1.1 8.8.8.8"
# nmcli connection up "YOUR_WIFI_SSID"
# macOS:
# sudo networksetup -setdnsservers Wi-Fi 1.1.1.1 8.8.8.8
# Windows PowerShell (run as Administrator):
# $adapter = Get-NetAdapter -Name 'Wi-Fi'
# Set-DnsClientServerAddress -InterfaceIndex $adapter.ifIndex -ServerAddresses ('1.1.1.1','8.8.8.8')

echo ""
echo "=== Fix D: Windows TCP/IP and Winsock Reset (run in elevated CMD) ==="
# WINDOWS ONLY - copy and run in Administrator Command Prompt:
# netsh winsock reset
# netsh int ip reset resetlog.txt
# netsh int ipv4 reset
# netsh int ipv6 reset
# ipconfig /flushdns
# ipconfig /registerdns
# ipconfig /release
# ipconfig /renew
# shutdown /r /t 5 /c "Rebooting after network stack reset"

echo ""
echo "=== Verification: Confirm internet access ==="
curl -s --max-time 10 -o /dev/null -w "HTTP Status: %{http_code}\nDNS Time: %{time_namelookup}s\nConnect Time: %{time_connect}s\nTotal Time: %{time_total}s\n" https://www.google.com
# Expected output: HTTP Status: 200
# If you see: curl: (6) Could not resolve host -> DNS issue
# If you see: curl: (7) Failed to connect -> Routing/WAN issue

echo ""
echo "=== Gateway Admin Check ==="
echo "Open http://192.168.1.254 in browser"
echo "Default login - Username: admin, Password: printed on gateway label"
echo "Check: Home Network > Broadband Status (should show Connected)"
echo "Check: Diagnostics > Ping > Target: 8.8.8.8 from gateway"
# AT&T BGW320 specific: also check Settings > LAN > DHCP to verify lease pool isn't exhausted

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SRE specialists, and network architects with 10+ years of experience diagnosing connectivity failures across residential ISPs, enterprise networks, and cloud infrastructure. Our guides are tested on real hardware with actual error conditions before publication. We focus on actionable, command-level troubleshooting that gets you back online fast — no vague 'restart your router' 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.