Why does my Arris modem say connected but no internet?

This classic symptom means your device has a valid local (LAN) IP address but the modem's WAN connection to the ISP has failed. The most common causes are: (1) the ISP's DHCP server did not assign a public IP — check the admin page at http://192.168.100.1 or http://192.168.1.254 and look for a 0.0.0.0 WAN IP; (2) a provisioning file download failure — power-cycle for 30 seconds to trigger re-provisioning; (3) ISP outage in your area — check your ISP's status page or call support. If the WAN IP is valid, the problem may be DNS — try overriding your DNS to 8.8.8.8 in the router settings.

How do I fix Arris WiFi not working when wired internet works fine?

When wired connections work but WiFi doesn't, the issue is isolated to the wireless radio or SSID configuration. Steps: (1) Log into the admin portal and confirm the WiFi radio is set to 'Enabled' — check both 2.4 GHz and 5 GHz separately. (2) Look for active WiFi schedules or parental controls that may have turned the radio off. (3) Change the WiFi channel to 1, 6, or 11 for 2.4 GHz. (4) If no devices can see the SSID at all, perform a 30-second power cycle. (5) If the SSID is visible but passwords fail, check that the security mode is WPA2 or WPA2/WPA3 mixed, not WPA3-only.

What does it mean when the Arris SURFboard is not connecting to the internet?

The SURFboard (SB6183, SB8200, etc.) is a standalone modem — not a router — so 'not connecting to internet' means the DOCSIS registration process is failing. Check http://192.168.100.1 → Status → Connection. Look for T3/T4 timeout errors in the Event Log, which indicate upstream channel ranging failures caused by line noise or signal level problems. Downstream power should be -7 to +7 dBmV and SNR above 33 dB. If signal levels are bad, inspect coaxial cables and remove any splitters for testing. If levels are good but the modem still won't come online, call your ISP — the modem's MAC address may need to be re-provisioned on the account.

How do I troubleshoot the Arris NVG443B or NVG468MQ specifically?

Both are AT&T-issued gateways with backend dependencies. For the NVG443B (DSL/VDSL): check the broadband LED color — green means synced, red means no DSL sync. Ensure DSL line filters are on all non-gateway phone connections. For the NVG468MQ (fiber): the gateway relies on AT&T's 802.1X authentication through the ONT. If the broadband light blinks amber or red, authentication has failed — this cannot be fixed locally and requires AT&T support to reset the port. For both: access the admin portal at http://192.168.1.254 → Diagnostics → Reboot and perform a controlled reboot. If IP Passthrough is configured and stops working, re-enter the connected device MAC address after every factory reset.

Why does my Arris router keep disconnecting every few hours?

Intermittent disconnections on Arris devices are usually caused by one of four issues: (1) DHCP lease expiration — your ISP issues short leases and the renewal fails due to line noise; check signal levels for T3/T4 errors during the drop windows. (2) Overheating — Arris gateways are sensitive to heat; ensure the device has 6 inches of clearance on all sides and is not in an enclosed cabinet. (3) Firmware bug — particularly on NVG468MQ models prior to firmware 12.x; request an AT&T firmware push. (4) WiFi channel congestion — if only wireless devices drop while wired stays up, use a WiFi analyzer app to identify congested channels and switch to a less occupied one.

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

Fix Arris router issues fast: modem connected but no internet, WiFi not working, NVG443B/NVG468MQ problems. Step-by-step solutions inside.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,639 words

Key Takeaways

Root cause 1: IP address lease failure or DHCP conflict — your Arris modem/router obtains a local IP but fails to receive a valid public IP from the ISP, resulting in 'connected but no internet' symptoms.
Root cause 2: Provisioning or firmware mismatch — ISP-locked Arris devices (NVG443B, NVG468MQ, SURFboard) may lose their provisioning file after a power cycle or firmware update, causing auth failures.
Root cause 3: WiFi radio disabled or channel congestion — the 2.4 GHz or 5 GHz radio may be toggled off via parental controls, or heavy channel interference causes packet loss severe enough to appear as no connectivity.
Quick fix summary: Power-cycle the modem (30-second full unplug), release/renew DHCP on client devices, factory-reset if provisioning is lost, and contact ISP to re-push the provisioning file if the WAN IP remains 0.0.0.0 after two reboot cycles.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle (30-second reboot)	First response to any connectivity loss; clears transient DHCP/provisioning state	2-5 min	None
DHCP release/renew on client	Device shows 'no internet access' but modem WAN IP is valid	1-2 min	None
Factory reset (pinhole)	Misconfigured settings, forgotten admin password, or persistent WiFi failure	10-15 min	Wipes all custom settings
ISP provisioning re-push	WAN IP stuck at 0.0.0.0 or 169.x.x.x after reboot; modem not authenticated	15-30 min (ISP call)	None
Firmware update via ISP portal	Known bugs in current firmware causing NVG443B or NVG468MQ drops	20-40 min	Low — requires ISP to push
WiFi channel change	Slow speeds or intermittent drops in dense environments (apartments)	5 min	None
DNS server override	Pages not loading but ping to IP works; resolves ISP DNS outages	3 min	None
Cable/coax line check	Arris SURFboard showing T3/T4 timeout errors in event log	15-30 min	None

Understanding Arris Router and Modem Issues

Arris devices — including the SURFboard SB8200, NVG443B, NVG468MQ, and various cable boxes — are widely deployed by ISPs including AT&T, Comcast/Xfinity, and Cox. Because they are ISP-provisioned, many problems stem from the relationship between the device and the ISP backend rather than the hardware itself. Understanding this distinction is critical before spending hours reconfiguring settings that will be overwritten on the next provisioning sync.

How Arris Modems Authenticate

When an Arris cable modem or gateway powers on, it performs the DOCSIS registration process:

Scans for a downstream channel lock
Ranges on an upstream channel
Downloads a configuration file (TFTP) from the ISP's CMTS
Registers with the ISP's network and receives a public WAN IP via DHCP

If any step fails, you'll see symptoms like 'connected but no internet,' a WAN IP of 0.0.0.0, or the online LED blinking indefinitely.

Step 1: Identify Your Exact Symptom

Before touching any settings, match your symptom to the correct fix path:

Symptom A — 'Arris modem connected but no internet' (all devices affected) This points to a WAN-side failure: provisioning, DHCP from ISP, or physical line issue.

Symptom B — 'Arris WiFi not working' (wireless devices only, wired works) This isolates the problem to the WiFi radio, SSID configuration, or 5 GHz band steering.

Symptom C — 'Arris connected without internet' on one device only This is almost always a client-side DHCP or DNS issue, not the router.

Symptom D — NVG443B or NVG468MQ troubleshooting (AT&T gateway) AT&T residential gateways use a different provisioning model (RG mode vs. passthrough). Issues often stem from AT&T's backend or IP Passthrough misconfiguration.

Step 2: Check the Physical Layer First

Always start with the coax or DSL line before touching software settings.

Inspect coax connectors for corrosion or loose fittings. Hand-tighten all F-connectors.
Check for splitters in the line — each splitter adds 3.5 dB of signal loss. Connect the modem directly to the wall outlet for testing.
Log into the modem diagnostics page (typically http://192.168.100.1 for SURFboard models, or http://192.168.1.254 for NVG gateways) and check signal levels:
- Downstream power: should be between -7 dBmV and +7 dBmV
- Upstream power: should be between 38 dBmV and 48 dBmV
- SNR (Signal-to-Noise Ratio): should be above 33 dB
Check the Event Log tab for T3 or T4 timeout errors, which indicate upstream ranging failures caused by physical line problems.

Step 3: Power-Cycle the Correct Way

A quick power button press is NOT sufficient. Follow this sequence:

Turn off all devices connected to the router.
Unplug the Arris modem/router from the wall outlet (do not just press the power button).
If you have a separate router behind the modem, unplug it too.
Wait a full 30 seconds — this clears the CMTS ARP cache on the ISP side.
Plug the modem back in first. Wait for the online LED to become solid (up to 3 minutes).
Plug in the router (if separate). Wait 1 minute.
Reconnect client devices.

Step 4: Diagnose WAN IP Assignment

Access the router admin page and navigate to the WAN or Connection Status section:

NVG443B / NVG468MQ: Browse to http://192.168.1.254 → Broadband → Status
SURFboard: Browse to http://192.168.100.1 → Status → Connection

If the WAN IP shows 0.0.0.0 or a 169.254.x.x address after a full reboot cycle, the modem is not receiving a DHCP lease from the ISP. This requires an ISP call or a MAC address reset.

If the WAN IP is valid but internet is still down, run the following from your computer:

ping 8.8.8.8
traceroute 8.8.8.8
nslookup google.com

If ping 8.8.8.8 works but nslookup google.com fails, the problem is DNS only — override with 8.8.8.8 or 1.1.1.1 in your router's DNS settings.

Step 5: Fix WiFi-Specific Issues (Arris WiFi Not Working)

5a. Verify the radio is enabled On NVG443B/NVG468MQ: Login → Home Network → Wireless. Confirm both 2.4 GHz and 5 GHz radios show 'Enabled.' Parental controls or a scheduled WiFi-off timer are common culprits.

5b. Change the WiFi channel On crowded 2.4 GHz bands, switch to channels 1, 6, or 11 (non-overlapping). For 5 GHz, channels 36, 40, 44, or 48 are generally cleaner.

5c. Check band steering NVG468MQ has aggressive band steering that can trap devices on 5 GHz even when signal is weak. Temporarily split the SSIDs (give 2.4 GHz and 5 GHz different names) to isolate band-specific problems.

5d. Update WiFi security settings Old devices may fail to connect if the router uses WPA3 only. Set security to WPA2/WPA3 mixed mode.

Step 6: Factory Reset (Last Resort Before ISP Call)

If all above steps fail and you have not already done so, perform a factory reset:

Locate the pinhole reset button (usually on the back or bottom).
With the device powered ON, insert a straightened paperclip and hold for 10-15 seconds until the LEDs cycle.
The device will reboot to factory defaults.
For ISP-provided gateways (NVG443B, NVG468MQ): The ISP will automatically re-provision the device over the next 3-5 minutes. You do NOT need to reconfigure SSID/password from scratch — the ISP's provisioning file will restore it, OR you'll need to call the ISP to push the config.
For retail SURFboard modems: After reset, call your ISP and have them re-provision the modem to your account.

NVG443B Specific Troubleshooting (AT&T)

The NVG443B is an AT&T-exclusive DSL/fiber gateway. Common unique issues:

IP Passthrough stops working after reboot: Navigate to Firewall → IP Passthrough, re-enter the device MAC, and save. This setting occasionally de-registers.
Broadband light flashing red: AT&T line authentication failure. Check that DSL filters are installed on all non-modem phone jacks, or call AT&T to check the DSLAM port assignment.
WiFi dropping every few hours: Disable 'Smart WiFi' under Home Network if present, as it can cause radio resets.

NVG468MQ Specific Troubleshooting (AT&T)

The NVG468MQ is a fiber (ONT-connected) gateway:

ONT light is green but gateway shows no broadband: The fiber handoff requires AT&T authentication via 802.1X. If authentication fails, the WAN stays down — this requires an AT&T technician or backend reset.
5 GHz disappears randomly: Known firmware issue in versions prior to 12.x. Request a firmware update from AT&T or enable auto-update under Settings → Diagnostics → Update.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# Arris Router / Modem Connectivity Diagnostic Script
# Run on a client machine connected to the Arris network
# Compatible with macOS and Linux
# ============================================================

echo "===== ARRIS NETWORK DIAGNOSTICS ====="
echo "Started at: $(date)"
echo ""

# --- 1. Check local IP and default gateway ---
echo "[1] Local Network Configuration:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  GATEWAY=$(netstat -nr | grep default | head -1 | awk '{print $2}')
  LOCAL_IP=$(ipconfig getifaddr en0 2>/dev/null || ipconfig getifaddr en1 2>/dev/null)
else
  GATEWAY=$(ip route | grep default | awk '{print $3}' | head -1)
  LOCAL_IP=$(hostname -I | awk '{print $1}')
fi
echo "  Local IP   : $LOCAL_IP"
echo "  Gateway    : $GATEWAY"
echo ""

# --- 2. Ping the gateway (Arris router LAN IP) ---
echo "[2] Ping Arris Gateway ($GATEWAY):"
ping -c 4 -W 2 "$GATEWAY" 2>&1 | tail -3
echo ""

# --- 3. Check Arris admin portal reachability ---
ARRIS_ADMIN_IPS=("192.168.100.1" "192.168.1.254" "192.168.0.1")
echo "[3] Arris Admin Portal Check:"
for IP in "${ARRIS_ADMIN_IPS[@]}"; do
  STATUS=$(curl -s -o /dev/null -w "%{http_code}" --connect-timeout 3 "http://$IP")
  echo "  http://$IP → HTTP $STATUS"
done
echo ""

# --- 4. Ping ISP DNS and public DNS ---
echo "[4] WAN Reachability Tests:"
for TARGET in "8.8.8.8" "1.1.1.1" "9.9.9.9"; do
  RESULT=$(ping -c 2 -W 2 "$TARGET" 2>&1 | grep -E "transmitted|loss")
  echo "  Ping $TARGET: $RESULT"
done
echo ""

# --- 5. DNS resolution test ---
echo "[5] DNS Resolution:"
for HOST in "google.com" "cloudflare.com" "amazon.com"; do
  RESOLVED=$(nslookup "$HOST" 2>&1 | grep -E "Address|server can|timed out" | head -3)
  echo "  nslookup $HOST:"
  echo "    $RESOLVED"
done
echo ""

# --- 6. DNS override test (bypass ISP DNS) ---
echo "[6] DNS Override Test (using 8.8.8.8):"
for HOST in "google.com" "cloudflare.com"; do
  RESULT=$(nslookup "$HOST" 8.8.8.8 2>&1 | grep -E "Address" | tail -1)
  echo "  $HOST via 8.8.8.8: $RESULT"
done
echo ""

# --- 7. Traceroute to first 5 hops ---
echo "[7] Traceroute (first 6 hops toward 8.8.8.8):"
if command -v traceroute &>/dev/null; then
  traceroute -m 6 -w 2 8.8.8.8 2>&1
elif command -v tracepath &>/dev/null; then
  tracepath -m 6 8.8.8.8 2>&1 | head -10
fi
echo ""

# --- 8. DHCP release and renew (Linux only) ---
if [[ "$OSTYPE" != "darwin"* ]]; then
  IFACE=$(ip route | grep default | awk '{print $5}' | head -1)
  echo "[8] DHCP Release & Renew on $IFACE:"
  echo "  Releasing..."
  sudo dhclient -r "$IFACE" 2>&1
  sleep 2
  echo "  Renewing..."
  sudo dhclient "$IFACE" 2>&1
  NEW_IP=$(hostname -I | awk '{print $1}')
  echo "  New IP: $NEW_IP"
else
  IFACE=$(route get 8.8.8.8 2>/dev/null | grep interface | awk '{print $2}')
  echo "[8] DHCP Release & Renew on $IFACE (macOS):"
  echo "  Run manually: sudo ipconfig set $IFACE DHCP"
  echo "  Or: networksetup -renewdhcp Wi-Fi"
fi
echo ""

# --- 9. Flush DNS cache ---
echo "[9] 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 (systemd-resolve or nscd)."
fi
echo ""

# --- 10. Check for WiFi channel info (macOS) ---
if [[ "$OSTYPE" == "darwin"* ]]; then
  echo "[10] WiFi Channel Info (macOS):"
  /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I 2>/dev/null | grep -E "SSID|channel|agrCtlRSSI|lastTxRate"
  echo ""
fi

echo "===== DIAGNOSTIC COMPLETE ====="
echo "If WAN pings fail (Step 4), call your ISP — the modem is not provisioned."
echo "If DNS fails (Step 5) but pings work (Step 4), override DNS in router to 8.8.8.8."
echo "If Gateway ping fails (Step 2), perform 30-second modem power cycle."

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and network specialists with combined experience across ISP infrastructure, enterprise networking, and consumer hardware troubleshooting. Our guides are built from real incident postmortems, ISP escalation ticket patterns, and hands-on lab testing. We cover everything from DOCSIS provisioning failures to BGP misconfigurations, always prioritizing 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.