Why does my Arris router say 'connected' but I have no internet access?

This is almost always one of three things: (1) your client device has a stale DHCP lease — run ipconfig /release && ipconfig /renew on Windows or sudo dhclient -r && sudo dhclient on Linux; (2) the Arris modem itself has not finished provisioning with the ISP — check that the Online light is solid, not blinking; (3) DNS resolution is broken — try pinging 8.8.8.8 directly. If that works but pinging google.com fails, set your DNS to 1.1.1.1 manually. Power cycling the modem for 60 seconds resolves this in most cases.

How do I fix my Arris modem when the WiFi is not working or the SSID has disappeared?

Log into the Arris admin panel (usually 192.168.0.1 or 192.168.1.254) and verify that the 2.4 GHz and 5 GHz radios are enabled under the Wireless section. If they are enabled but the SSID is still not broadcasting, change the wireless channel (use channel 1, 6, or 11 for 2.4 GHz) and save. If the radio still won't come up, perform a factory reset using the pinhole on the back of the device. Firmware corruption after a failed OTA update from your ISP can permanently disable the radio — in that case, contact your ISP for a replacement unit.

My Arris Surfboard shows all green lights but still won't connect to the internet — what do I do?

Green lights on a Surfboard (including the Online light) confirm the modem has provisioned with the ISP, so the problem is likely downstream of the modem. Check: (1) Is your router properly connected to the Surfboard via ethernet? (2) Has your router received a valid WAN IP from the modem? Log into your router's WAN status page. (3) Try connecting a laptop directly to the Surfboard via ethernet — if you get internet that way, the issue is with your router, not the Surfboard. If no internet even when directly connected, power cycle the Surfboard for 60 seconds and check the event log at 192.168.100.1 for T3/T4 errors.

How do I troubleshoot the Arris NVG443B or NVG468MQ when it loses internet randomly?

Random internet drops on NVG443B and NVG468MQ are most often caused by NAT table overflow after extended uptime, a firmware bug, or DSL line quality issues. First, check your firmware version at System > About in the admin UI and compare against the latest version from AT&T or Frontier. Second, enable a weekly scheduled reboot to clear the NAT table. Third, log into the admin UI at 192.168.1.254, go to Broadband > Status, and check DSL SNR margin — it should be above 6 dB. Values below 6 dB mean your DSL line is marginal and needs ISP attention. Also check for IP Passthrough misconfiguration if you run a router behind the gateway.

What do T3 and T4 timeout errors in the Arris event log mean?

T3 timeout means the modem sent a Ranging Request upstream but received no response from the CMTS (Cable Modem Termination System) at the ISP headend. T4 timeout means the modem lost contact with the CMTS entirely and went offline. Both errors point to upstream signal problems: loose or corroded coax connectors, too many splitters degrading signal, water ingress in outdoor cables, or an actual fault at the ISP's node or headend. Check coax connections first — finger-tighten all F-connectors. If T3/T4 errors persist after checking cables, call your ISP and provide the specific error counts from the event log at 192.168.100.1/EventLog.asp to accelerate the support ticket.

Arris Router Issues: Connected But No Internet, WiFi Not Working & Full Troubleshooting Guide

Fix Arris router issues including 'connected but no internet', WiFi not working, and modem not connecting. Step-by-step guide for NVG443B, NVG468MQ & Surfboard.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,945 words

Key Takeaways

Root cause 1: IP address conflicts or DHCP lease failures — your Arris modem/router assigns or receives a bad IP, causing 'connected but no internet' symptoms even though the WiFi link shows active.
Root cause 2: ISP signal issues or provisioning failures — the cable plant (coax or DSL line) loses lock or the CMTS/DSLAM fails to provision the modem, displaying solid power lights but no downstream internet traffic.
Root cause 3: Firmware bugs or corrupted config — Arris NVG443B and NVG468MQ devices are known to exhibit WiFi dropout and NAT table corruption after extended uptime or failed OTA firmware pushes from AT&T/Frontier.
Quick fix summary: Power-cycle the modem (unplug 60 seconds), run ipconfig /release + /renew or ip addr flush on connected clients, check signal levels in the admin UI at 192.168.0.1 or 192.168.1.1, and factory-reset as a last resort before calling your ISP.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power cycle (unplug 60 sec)	First step for any Arris connectivity issue	2 min	None
DHCP release/renew on client	Client shows 'connected, no internet' or 169.254.x.x IP	1 min	None — drops network briefly
Arris admin UI signal check (192.168.0.1)	Modem shows online but internet is slow or intermittent	5 min	None — read-only diagnostic
Change DNS to 8.8.8.8 / 1.1.1.1	Pages won't load but ping by IP works	3 min	Low — overrides ISP DNS
WiFi channel change (2.4 GHz → Ch 1/6/11)	WiFi drops frequently or shows 'connected, no internet'	5 min	Low — may affect neighbor devices
Firmware manual update via admin UI	Known firmware bug after ISP OTA push fails	15 min	Medium — wrong file can brick
Factory reset (pinhole reset)	All else fails, corrupted config suspected	10 min + reconfigure	High — wipes all settings
ISP line test / tech dispatch	Signal levels out of spec (SNR < 30 dB, power < -7 dBmV)	1–3 days	None — ISP handles

Understanding Arris Router & Modem Issues

Arris manufactures a broad range of consumer and ISP-provisioned networking devices — from the popular Surfboard SB8200 DOCSIS 3.1 cable modem to AT&T gateway combos like the NVG443B and NVG468MQ. Despite their prevalence, these devices share a common set of failure modes that produce the same maddening symptom: your device shows 'Connected' or full WiFi bars, yet no websites load and ping to 8.8.8.8 times out.

Understanding why this happens is the fastest path to a fix.

How an Arris Cable/DSL Modem Gets You Online

When the modem powers on, it performs a multi-stage initialization:

Downstream lock — scans for and locks onto a valid DOCSIS downstream channel.
Upstream ranging — negotiates TX power with the CMTS (Cable Modem Termination System) at your ISP's headend.
DHCP provisioning — receives a public IP, subnet mask, gateway, and DNS servers from the ISP.
TFTP config download — fetches its configuration file from the ISP's TFTP server.
BPI+ authorization — encrypts the upstream channel (security layer).

If any step fails silently, you get a modem that appears online locally but cannot pass traffic. The admin UI event log is the only way to see which step failed.

Step 1: Identify Your Exact Symptom

Before touching any settings, classify the failure:

No lights at all → Power adapter or hardware failure.
Power + Send/Receive blinking, Online light OFF → Modem not provisioned. ISP signal or account issue.
All lights solid, but WiFi box shows 'connected, no internet' → DHCP, DNS, or NAT issue.
WiFi not showing up at all → Radio disabled, firmware crash, or hardware fault.
WiFi connects but pages load slowly or drop → Signal quality or interference issue.

On NVG443B and NVG468MQ (AT&T/Frontier combo gateways), navigate to http://192.168.1.254 or http://192.168.0.1 and check the Broadband > Status page. Look for:

DSL Training State: SHOWTIME (good) vs TRAINING (syncing, problem)
Downstream SNR Margin: should be ≥ 6 dB for DSL
Downstream Receive Power: should be between -7 and +7 dBmV for DOCSIS

Step 2: Power Cycle Correctly

Most users unplug and immediately replug. This is wrong. The CMTS needs time to release the old session.

Power off any connected router (if modem and router are separate).
Unplug the Arris modem from power.
Wait 60 full seconds — not 10, not 30.
Plug the modem back in.
Wait for the Online light to turn solid (up to 5 minutes on DOCSIS 3.1).
Power on the router last.

If you have a combo gateway (modem + router in one unit, like the NVG443B), a single 60-second unplug handles both.

Step 3: Fix the Client-Side 'Connected But No Internet' Error

Sometimes the modem is fine and the problem is your PC or device holding a stale DHCP lease or a bad DNS entry.

On Windows:

ipconfig /release
ipconfig /flushdns
ipconfig /renew

On macOS:

sudo ipconfig set en0 DHCP
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

On Linux:

sudo ip addr flush dev eth0
sudo dhclient -r eth0 && sudo dhclient eth0

After renewing, check your assigned IP. If it starts with 169.254.x.x, your device is assigning itself an APIPA address — the DHCP server on the Arris unit is unreachable or has run out of leases.

Step 4: Check and Fix DNS

A common pattern on Arris routers: the device gets a valid IP and gateway but the ISP's DNS servers are unreachable. You'll see:

ping 8.8.8.8 → Reply from 8.8.8.8 (works)
ping google.com → Ping request could not find host (fails)

This confirms DNS failure. Fix it:

Log into the Arris admin panel (192.168.0.1 or 192.168.1.254).
Navigate to Basic Setup > WAN or Broadband > DNS.
Set Primary DNS to 1.1.1.1 and Secondary DNS to 8.8.8.8.
Save and reboot.

Alternatively, set DNS on each client device's network adapter directly.

Step 5: Arris WiFi Not Working — Radio Troubleshooting

If the Arris WiFi box shows no SSID or drops clients:

Check if WiFi is disabled: Log into admin UI → Wireless → ensure both 2.4 GHz and 5 GHz radios show Enabled.
Change the WiFi channel: Interference is the #1 cause of random drops on 2.4 GHz. Use only channels 1, 6, or 11 (non-overlapping). On 5 GHz, channels 36, 40, 44, 48 are safest.
Check transmit power: Set to High if range is an issue.
Disable 802.11b compatibility: Legacy 802.11b devices force the entire network to slow down. Disable if not needed.
Reboot the radio only: On NVG443B/NVG468MQ, SSH into the gateway (if accessible) and run restart wifi or use the admin UI's wireless restart option.

Step 6: Arris Surfboard Not Connecting to Internet

The Surfboard series (SB6183, SB8200, etc.) are cable modems only — they require a separate router. If your Surfboard won't connect:

Check coax connection — finger-tighten the F-connector at both the modem and the wall outlet. Loose coax is the #1 cause of intermittent signal.
Check downstream signal levels at 192.168.100.1 (Surfboard default):
- Downstream Power: -7 to +7 dBmV (ideal: 0 dBmV)
- SNR: ≥ 30 dB
- Upstream Power: 38–48 dBmV
Check the Event Log at 192.168.100.1/EventLog.asp for T3 or T4 timeout errors — these indicate upstream ranging failures caused by bad coax, splitters, or ISP line issues.
Remove splitters — every splitter adds 3.5 dB of signal loss. Remove all non-essential splitters between the wall and the modem.
Call your ISP with the specific T3/T4 error counts — this forces them to check line levels remotely and dispatch a tech if needed.

Step 7: NVG443B and NVG468MQ Specific Fixes

These AT&T/Frontier DSL/fiber gateways have known firmware issues:

NVG443B: Random WiFi dropout bug in firmware versions prior to 9.2.2h0d83. Check System > Firmware Version in the admin UI. If behind, contact AT&T to push an update or check the AT&T support portal.
NVG468MQ: NAT table overflow after 14–21 days uptime causing 'connected but no internet' on all clients. Workaround: set a weekly scheduled reboot via System > Scheduled Reboot in the admin UI, or use the following cron approach if SSH is enabled:
```
0 3 * * 0 /sbin/reboot
```
IP Passthrough mode: If you use your own router behind the gateway, enable IP Passthrough (Firewall > IP Passthrough) and enter your router's MAC address. Double-NAT is a common hidden cause of 'no internet' symptoms.

Step 8: Factory Reset as Last Resort

If nothing else works and you suspect a corrupted configuration:

Locate the Reset pinhole on the back of the device.
With the device powered on, insert a straightened paperclip and hold for 10–15 seconds until the lights flash.
Wait 2–3 minutes for the device to fully reinitialize.
Reconnect via ethernet to the admin UI and reconfigure your WiFi SSID, password, and any custom settings.

Warning: This erases all custom settings. Have your ISP credentials (PPPoE username/password for DSL) ready before resetting.

When to Call Your ISP

Escalate to your ISP immediately if you see:

T3 timeout errors in the Surfboard event log (upstream ranging failure)
Downstream SNR below 30 dB or power outside -7 to +7 dBmV range
DSL sync state stuck in TRAINING for more than 10 minutes after power cycle
Correct signal levels but provisioning fails (modem gets DHCP but no internet)
More than 3 uncorrectable codeword errors per minute on any downstream channel

Frequently Asked Questions

bash

#!/usr/bin/env bash
# =============================================================
# Arris Router/Modem Diagnostic Script
# Run on a client connected to the Arris network
# Compatible with Linux and macOS (Windows users: use WSL or
# run the individual commands in Command Prompt / PowerShell)
# =============================================================

set -euo pipefail

GATEWAY_DEFAULT="192.168.0.1"
GATEWAY_ATT="192.168.1.254"
SURFBOARD_UI="192.168.100.1"
DNS_TEST="8.8.8.8"
DOMAIN_TEST="google.com"

echo "====================================================="
echo " Arris Network Diagnostic Tool"
echo "====================================================="

# --- 1. Detect default gateway ---
echo ""
echo "[1] Detecting default gateway..."
if command -v ip &>/dev/null; then
  GW=$(ip route show default | awk '/default/ {print $3}' | head -1)
elif command -v netstat &>/dev/null; then
  GW=$(netstat -rn | awk '/^0\.0\.0\.0/ {print $2}' | head -1)
else
  GW="UNKNOWN"
fi
echo "    Default gateway: ${GW}"

# --- 2. Check local IP assignment ---
echo ""
echo "[2] Local IP addresses:"
if command -v ip &>/dev/null; then
  ip addr show | grep 'inet ' | awk '{print "    " $2}'
else
  ifconfig | grep 'inet ' | awk '{print "    " $2}'
fi

# APIPA check
APIPA=$(ip addr show 2>/dev/null | grep '169\.254' || true)
if [[ -n "$APIPA" ]]; then
  echo "    WARNING: APIPA address detected (169.254.x.x) -- DHCP has failed!"
  echo "    Fix: sudo dhclient -r && sudo dhclient"
fi

# --- 3. Ping default gateway ---
echo ""
echo "[3] Pinging default gateway (${GW})..."
if ping -c 3 -W 2 "${GW}" &>/dev/null; then
  echo "    Gateway reachable"
else
  echo "    FAIL: Cannot reach gateway ${GW} -- check ethernet/WiFi connection to Arris device"
fi

# --- 4. Ping ISP / internet by IP ---
echo ""
echo "[4] Pinging ${DNS_TEST} (Google DNS by IP)..."
if ping -c 3 -W 2 "${DNS_TEST}" &>/dev/null; then
  echo "    Internet reachable by IP -- routing is working"
else
  echo "    FAIL: Cannot reach ${DNS_TEST} -- modem may not be provisioned or ISP issue"
fi

# --- 5. DNS resolution test ---
echo ""
echo "[5] Testing DNS resolution for ${DOMAIN_TEST}..."
if command -v dig &>/dev/null; then
  DIG_OUT=$(dig +short "${DOMAIN_TEST}" 2>&1)
  if [[ -n "$DIG_OUT" ]]; then
    echo "    DNS OK: ${DOMAIN_TEST} resolves to ${DIG_OUT}"
  else
    echo "    FAIL: DNS resolution failed for ${DOMAIN_TEST}"
    echo "    Fix: Set DNS to 1.1.1.1 in adapter settings or Arris admin UI"
  fi
elif command -v nslookup &>/dev/null; then
  if nslookup "${DOMAIN_TEST}" &>/dev/null; then
    echo "    DNS OK via nslookup"
  else
    echo "    FAIL: nslookup failed for ${DOMAIN_TEST}"
  fi
fi

# --- 6. Check Arris admin UIs ---
echo ""
echo "[6] Checking Arris admin UI availability..."
for UI in "${GATEWAY_DEFAULT}" "${GATEWAY_ATT}" "${SURFBOARD_UI}"; do
  if curl -s --connect-timeout 3 "http://${UI}" -o /dev/null -w "%{http_code}" | grep -qE '^(200|301|302|401)'; then
    echo "    Admin UI responding at: http://${UI}"
  else
    echo "    No response at: http://${UI}"
  fi
done

# --- 7. Trace route to diagnose hop failures ---
echo ""
echo "[7] Traceroute to ${DNS_TEST} (first 10 hops)..."
if command -v traceroute &>/dev/null; then
  traceroute -m 10 -w 2 "${DNS_TEST}" 2>&1 | head -15 | sed 's/^/    /'
elif command -v tracepath &>/dev/null; then
  tracepath -m 10 "${DNS_TEST}" 2>&1 | head -15 | sed 's/^/    /'
fi

# --- 8. Check for T3/T4 errors (Surfboard only) ---
echo ""
echo "[8] Fetching Surfboard event log for T3/T4 errors..."
EVENT_URL="http://${SURFBOARD_UI}/EventLog.asp"
if curl -s --connect-timeout 5 "${EVENT_URL}" | grep -iE 'T3|T4|timeout' | head -5 | sed 's/<[^>]*>//g' | sed 's/^/    /'; then
  echo "    (T3/T4 errors above indicate upstream signal problems -- call ISP)"
else
  echo "    No T3/T4 errors found or Surfboard UI not reachable at ${SURFBOARD_UI}"
fi

# --- 9. Flush DNS cache ---
echo ""
echo "[9] Flushing local DNS cache..."
if [[ "$(uname)" == "Darwin" ]]; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
  echo "    macOS DNS cache flushed"
elif [[ "$(uname)" == "Linux" ]]; then
  if systemctl is-active --quiet systemd-resolved; then
    sudo systemd-resolve --flush-caches
    echo "    systemd-resolved cache flushed"
  elif command -v nscd &>/dev/null; then
    sudo service nscd restart
    echo "    nscd restarted"
  fi
fi

echo ""
echo "====================================================="
echo " Diagnostic complete."
echo " If issues persist:"
echo "   - Power cycle Arris device for 60 seconds"
echo "   - Check coax cable connections (Surfboard)"
echo "   - Check DSL SNR in admin UI (NVG443B/NVG468MQ)"
echo "   - Call ISP with T3/T4 error counts"
echo "====================================================="

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, network administrators, and SRE professionals with combined experience spanning ISP operations, enterprise networking, and consumer device troubleshooting. Our guides are tested on real hardware before publication and updated when firmware or ISP configurations change.

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.