Why does my ATT WiFi show 'Connected' but have no internet access?

This is the classic 'ATT connected but no internet' or 'ATT router connected but no internet' problem. Your device successfully associated with the WiFi radio, but the gateway's WAN link to ATT's network is down or DNS is failing. First, verify other devices have the same issue (if only one device, it's a local DNS or proxy setting). Then power cycle the gateway (unplug 60 seconds). If that fails, try setting DNS manually to 8.8.8.8 on your device. On Windows you may see 'ERR_NAME_NOT_RESOLVED' in Chrome or 'DNS_PROBE_FINISHED_NO_INTERNET' — these confirm DNS failure. Check att.com/outages for area-wide issues before escalating.

Why is my ATT fiber internet suddenly slow?

ATT fiber slow all of a sudden is most commonly caused by: (1) WiFi congestion — switch from 2.4 GHz to 5 GHz and change your wireless channel; (2) Background updates on connected devices consuming bandwidth; (3) ATT network congestion during peak hours (evenings 7-10 PM) — check att.com/outages; (4) A failing or partially damaged fiber cable or ONT; (5) Outdated gateway firmware. Run a wired speed test first — if wired speed is normal but WiFi is slow, the fix is wireless optimization. If wired is also slow, power cycle the gateway and ONT, then call ATT if the problem persists.

How do I restart my ATT router or gateway?

To perform an ATT restart router procedure: Method 1 (Soft restart) — Open a browser, go to http://192.168.1.254, login, and select Restart under the Settings or Diagnostics menu. Method 2 (Power cycle) — Unplug the power cable from the gateway, wait 60 seconds, plug it back in. Wait up to 3 minutes for the Broadband LED to turn solid green. Method 3 (myATT app) — Open the app, go to Internet > Restart Router. Never use the Reset pinhole for a routine restart — that performs a factory reset and erases your settings.

Why is my ATT mobile hotspot not working or connecting?

ATT mobile hotspot not working has several common causes: (1) Data plan exhausted or hotspot feature not included in your plan — check myATT app under Data Usage; (2) Hotspot disabled in device settings — go to Settings > Connections > Mobile Hotspot and enable it; (3) Wrong APN setting — ATT APN should be 'phone' for consumer accounts; (4) SIM card issue — remove and reinsert the SIM; (5) Network registration problem — toggle Airplane Mode on for 30 seconds then off to force fresh registration; (6) Carrier throttling after hitting hotspot data cap. Contact ATT at 611 from your ATT device if the plan appears active but hotspot still fails.

What do I do if ATT has no broadband connection after all troubleshooting steps?

If the Broadband LED on your ATT gateway remains red after a full power cycle and there is no area outage reported, the issue is likely physical: a damaged fiber line, faulty ONT, or a provisioning error on ATT's side. Steps to take: (1) Check all physical connections — the fiber cable from the ONT to the gateway must be firmly seated; (2) Check the ONT's own LED — if it shows red or no signal, the fiber line itself is the problem; (3) Call ATT technical support at 800-288-2020 and request a line test; (4) Ask the agent to re-provision your gateway (a remote fix for provisioning errors); (5) Schedule a technician visit if remote steps fail. Line problems and ONT replacements require an ATT field technician.

ATT WiFi Not Working: Complete Troubleshooting Guide for Slow, Disconnected, or No Internet Issues

Fix ATT WiFi not working, slow internet, or no connection issues fast. Step-by-step guide covering fiber, U-verse, hotspot, and router resets.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,798 words

Key Takeaways

Root Cause 1: Router or gateway firmware glitches, IP lease conflicts, or hardware faults cause 'ATT WiFi connected but no internet' and 'ATT no broadband connection' errors — a full power cycle resolves 80% of these cases.
Root Cause 2: Network congestion, incorrect DNS settings, outdated router firmware, or ISP-side outages cause ATT fiber slow download speed and ATT internet very slow symptoms — checking ATT outage status and updating DNS to 8.8.8.8 often restores full speed.
Root Cause 3: Channel interference, bandwidth saturation, and incorrect WiFi band (2.4 GHz vs 5 GHz) selection cause ATT WiFi slow all of a sudden issues — switching bands and changing channels in the gateway settings can double throughput immediately.
Quick Fix Summary: Power cycle your ATT gateway (unplug 60 seconds), run a speed test at speedtest.net, check ATT outage map at att.com/outages, update DNS to 8.8.8.8/8.8.4.4, reposition your router, and call ATT support at 800-288-2020 if the issue persists.

ATT WiFi Fix Approaches Compared
Method	When to Use	Time	Risk
Power cycle gateway/router	ATT no broadband connection, ATT lost internet connection, ATT modem not working	2-5 min	None — safe first step
Check ATT outage map	ATT internet slow today, ATT no network connection affecting whole area	1-2 min	None — informational only
Change DNS to 8.8.8.8	ATT connected but no internet, slow DNS resolution, ATT WiFi connected but no internet	5 min	Low — reversible anytime
Switch WiFi band (2.4 vs 5 GHz)	ATT WiFi slow all of a sudden, ATT fiber slow wifi, ATT wireless slow	3-5 min	Low — may drop some devices temporarily
Change WiFi channel	ATT WiFi slow in dense apartment/office, ATT upload speed slow	5-10 min	Low — brief disconnection during change
Update gateway firmware	ATT WiFi problems persisting after reboot, ATT modem not working fully	10-20 min	Medium — device reboots, brief outage
Factory reset gateway	All software fixes failed, ATT can't connect to network	15-30 min	High — erases all custom settings
Replace Ethernet cable	ATT U-verse ethernet not working, ATT fiber slow download speed on wired connection	5-10 min	None
Contact ATT support	ATT no broadband connection after all steps, ISP-side provisioning issue	30-60 min	None

Understanding ATT WiFi Not Working

ATT internet issues span a wide spectrum — from a complete 'ATT no broadband connection' error where all lights on your gateway are red, to subtle ATT fiber slow download speeds that only surface during peak hours. Understanding which failure mode you are dealing with determines which fix path to take.

The ATT gateway (BGW320, BGW210, NVG589, or similar models) handles DHCP, NAT, DNS forwarding, and WiFi radio management simultaneously. Any one of these subsystems can fail independently, producing misleading symptoms. A device showing 'Connected' in Windows or macOS network settings while displaying 'No Internet Access' means the WiFi association succeeded but the gateway's WAN uplink or DNS is failing — not the radio.

Step 1: Identify Your Symptom

Before touching any hardware, classify your problem:

Complete outage: All devices fail, gateway shows solid red Broadband LED or flashing red Service LED. Error seen: 'ATT no broadband connection' or 'Limited connectivity' in Windows.
Partial connectivity: Devices connect to WiFi but browsers show 'ERR_NAME_NOT_RESOLVED' or 'DNS_PROBE_FINISHED_NO_INTERNET' — classic 'ATT connected but no internet' scenario.
Speed degradation: Connection works but ATT fiber not getting full speed, ATT internet speed slow, or ATT upload speed slow. Speedtest.net shows far below your plan tier.
Intermittent drops: ATT WiFi not connecting randomly, sessions drop every few hours — usually a signal or interference issue.
Single device: Only one laptop or phone has ATT WiFi problems — isolates the issue to the client device, not the gateway.

Step 2: Check for ATT Service Outages

Always rule out an ISP-side problem before spending time on hardware. Visit att.com/outages or use the myATT app:

Navigate to att.com/internet/outages and enter your ZIP code.
In the myATT app: Home > Internet > Troubleshoot & Resolve.
Call the automated outage line: 1-800-288-2020 and say 'Outage'.

If ATT internet slow today is reported for your area, no local action will help. Monitor the outage and wait for resolution.

Step 3: Power Cycle Your ATT Gateway

This resolves the majority of ATT WiFi not working and ATT modem not working cases:

Unplug the power cord from the back of your ATT gateway (BGW320, BGW210, NVG589, etc.).
If you have a separate ONT (optical network terminal — a white box near where fiber enters), unplug its power too.
Wait 60 full seconds. This clears RAM, forces DHCP lease renewal, and resets the WAN session.
Plug the ONT back in first (if present). Wait for its lights to stabilize (30-60 seconds).
Plug the gateway back in. Wait up to 3 minutes for the Broadband LED to turn solid green.
Reconnect your devices.

If the Broadband LED remains red after 3 minutes, the issue is upstream (fiber line, ONT, or ATT network). Proceed to Step 2 to check outages and then call support.

Step 4: Run Diagnostic Commands

From a Windows, macOS, or Linux machine connected to your ATT network (even via Ethernet), run the diagnostics in the code section below. These commands reveal IP assignment failures, DNS issues, packet loss, and routing problems.

Key things to look for:

ipconfig (Windows) or ifconfig/ip addr (Linux/macOS): Confirm you have a valid IP in the 192.168.1.x range. An IP beginning with 169.254.x.x means APIPA/DHCP failure — your device never got an address from the gateway.
ping 192.168.1.254: Pings the ATT gateway LAN interface. If this fails on a wired connection, the gateway is unresponsive.
ping 8.8.8.8: Bypasses DNS and pings Google's IP directly. Success here with failed domain lookups = pure DNS problem.
ping google.com: If this fails but the IP ping above works, DNS is the issue.
tracert / traceroute: Shows where packets stop — inside your LAN, at the gateway WAN hop, or further upstream.

Step 5: Fix DNS Issues (ATT Connected But No Internet)

The most common cause of 'ATT WiFi connected but no internet' is a stale or failing DNS configuration:

Windows:

Open Network Settings > Change Adapter Options.
Right-click your WiFi adapter > Properties.
Select IPv4 > Properties.
Set DNS to 8.8.8.8 (Primary) and 8.8.4.4 (Secondary).
Click OK and test.

macOS:

System Preferences > Network > WiFi > Advanced > DNS.
Remove existing DNS entries. Add 8.8.8.8 and 1.1.1.1.
Apply and test.

On the ATT Gateway itself (affects all devices):

Open a browser and go to http://192.168.1.254.
Login with your gateway password (printed on the device label).
Navigate to Home Network > Subnets & DHCP.
Change the Primary DNS field to 8.8.8.8 and Secondary to 8.8.4.4.
Save and reboot the gateway.

Step 6: Fix ATT WiFi Slow Issues

Switch WiFi Bands: ATT gateways broadcast both 2.4 GHz and 5 GHz bands. If your device auto-connects to 2.4 GHz in a congested area, you'll experience ATT WiFi slow all of a sudden. Connect to the 5 GHz SSID (usually labeled with '5G' suffix) for faster speeds at shorter range.

Change WiFi Channel:

Login to your gateway at http://192.168.1.254.
Go to Home Network > Wireless.
For 2.4 GHz, change the channel to 1, 6, or 11 (non-overlapping).
For 5 GHz, try channels 36, 40, 44, or 48.
Use a WiFi analyzer app (Android: WiFi Analyzer; macOS: Wireless Diagnostics) to find the least congested channel in your environment.

Check for Bandwidth Hogs: Log into the gateway at 192.168.1.254 > Home Network > IP Allocation to see connected devices. Unknown devices consuming bandwidth could explain ATT internet very slow symptoms.

Step 7: ATT U-Verse Ethernet Not Working

If wired connections fail while WiFi works:

Swap the Ethernet cable — damaged cables cause ATT U-verse ethernet not working in most cases.
Try a different port on the gateway.
Test on another device to isolate whether it's the cable, the port, or the NIC.
Check the NIC driver in Device Manager (Windows) and update if needed.

Step 8: ATT Mobile Hotspot Not Working

For ATT hotspot not working or ATT mobile hotspot not working:

Toggle Airplane Mode on/off to force a fresh cell registration.
Check your data plan — hotspot may be throttled or exhausted.
Go to Settings > Mobile Hotspot and verify the hotspot is enabled with correct credentials.
If ATT cell service slow: Check att.com/maps for coverage in your area.
APN Settings: Settings > Cellular > Cellular Data Options > Cellular Network > APN should be phone for ATT consumer plans.

Step 9: Factory Reset as Last Resort

If all else fails and ATT can't connect to network:

Locate the reset pinhole on the back of your ATT gateway.
Use a paperclip to press and hold for 10 seconds until the Power LED flashes.
Wait 3-5 minutes for the gateway to fully restart.
Reconnect using the default WiFi credentials on the gateway label.
Re-enter any custom settings (DNS, port forwarding, static IPs).

Warning: A factory reset deletes all custom configurations. Document your settings before proceeding.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ATT WiFi / Internet Diagnostic Script
# Works on macOS and Linux. For Windows, see inline comments.
# Run with: bash att_diag.sh

echo "========================================="
echo " ATT Internet Diagnostic Tool"
echo "========================================="
echo ""

# --- 1. Show Current Network Interface and IP Address ---
echo "[1] Network Interfaces & IP Addresses:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  ifconfig | grep -E 'inet |ether|status|flags' | head -30
else
  ip addr show | grep -E 'inet |ether|link'
fi
# Windows equivalent: ipconfig /all
echo ""

# --- 2. Check Default Gateway (ATT Router IP) ---
echo "[2] Default Gateway:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  netstat -rn | grep default | head -5
else
  ip route show default
fi
# Windows equivalent: route print | findstr "0.0.0.0"
echo ""

# --- 3. Ping ATT Gateway (LAN) ---
GATEWAY_IP="192.168.1.254"
echo "[3] Pinging ATT Gateway at $GATEWAY_IP (5 packets):"
ping -c 5 $GATEWAY_IP 2>&1
# Windows: ping 192.168.1.254 -n 5
echo ""

# --- 4. Ping Google DNS by IP (bypasses DNS, tests WAN) ---
echo "[4] Pinging Google DNS 8.8.8.8 (WAN connectivity test, 5 packets):"
ping -c 5 8.8.8.8 2>&1
# Windows: ping 8.8.8.8 -n 5
echo ""

# --- 5. Ping Cloudflare DNS by IP ---
echo "[5] Pinging Cloudflare DNS 1.1.1.1 (5 packets):"
ping -c 5 1.1.1.1 2>&1
echo ""

# --- 6. DNS Resolution Test ---
echo "[6] DNS Resolution Test (nslookup google.com):"
nslookup google.com 2>&1
# Windows: nslookup google.com
echo ""

# --- 7. DNS Test with Specific Servers ---
echo "[7] Direct DNS query to 8.8.8.8:"
nslookup google.com 8.8.8.8 2>&1
echo ""

# --- 8. Traceroute to ATT DNS and Google ---
echo "[8] Traceroute to 8.8.8.8 (first 15 hops):"
if [[ "$OSTYPE" == "darwin"* ]]; then
  traceroute -m 15 8.8.8.8 2>&1
else
  traceroute -m 15 8.8.8.8 2>&1 || tracepath -m 15 8.8.8.8 2>&1
fi
# Windows: tracert -h 15 8.8.8.8
echo ""

# --- 9. Check MTU (common cause of slow/broken HTTPS on fiber) ---
echo "[9] MTU Path Discovery Test (HTTPS often breaks if MTU too high):"
if [[ "$OSTYPE" == "darwin"* ]]; then
  ping -D -s 1464 8.8.8.8 -c 3 2>&1 || echo "MTU above 1464 may be causing issues. Check gateway MTU setting."
else
  ping -M do -s 1464 -c 3 8.8.8.8 2>&1 || echo "MTU above 1464 detected. Consider setting gateway MTU to 1500 or 1492 for PPPoE."
fi
echo ""

# --- 10. Speed Test via curl (rough throughput check) ---
echo "[10] Quick Download Speed Test (downloading 100MB test file from fast.com CDN):"
curl -o /dev/null -w "%{speed_download} bytes/sec\n" --max-time 15 https://speed.hetzner.de/100MB.bin 2>&1
# For more accurate results, use: speedtest-cli (install via pip install speedtest-cli)
# speedtest-cli --simple
echo ""

# --- 11. Flush DNS Cache ---
echo "[11] Flushing local DNS cache:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
  echo "macOS DNS cache flushed."
else
  sudo systemd-resolve --flush-caches 2>/dev/null || sudo /etc/init.d/nscd restart 2>/dev/null
  echo "Linux DNS cache flushed."
fi
# Windows: ipconfig /flushdns
echo ""

# --- 12. WiFi Channel and Signal Info (Linux) ---
if command -v iwconfig &> /dev/null; then
  echo "[12] WiFi Signal & Channel Info:"
  iwconfig 2>&1 | grep -E 'ESSID|Frequency|Signal|Bit Rate'
fi
echo ""

echo "========================================="
echo " Diagnostic Complete"
echo " If WAN pings fail but gateway ping works:"
echo " -> ATT upstream outage or ONT issue"
echo " If IP starts with 169.254:"
echo " -> DHCP failure. Power cycle gateway."
echo " If DNS resolution fails but IP ping works:"
echo " -> Change DNS to 8.8.8.8 manually"
echo "========================================="

Error Medic Editorial

Error Medic Editorial is a team of senior DevOps engineers, SREs, and network specialists with 10+ years of experience diagnosing and resolving ISP, infrastructure, and connectivity issues across enterprise and consumer environments. Our guides are built from real incident postmortems, lab testing, and hands-on troubleshooting with major US carriers including ATT, Comcast, and Verizon.

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.