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 & m
- Root Cause 1: DHCP lease failure or IP address conflict — your Arris modem/router receives a local IP but fails to obtain a valid WAN IP from your ISP, resulting in 'connected but no internet' symptoms.
- Root Cause 2: Firmware corruption or misconfigured DNS settings causing the router to pass traffic locally but fail DNS resolution, making it appear as though there is no internet connectivity even when the physical link is active.
- Root Cause 3: ISP provisioning issues — the Arris modem's MAC address is not yet registered or has been deprovisioned on the ISP's CMTS (Cable Modem Termination System), blocking internet access at the provider level.
- Quick Fix Summary: Power-cycle your Arris device (30-second full power-off), release/renew your DHCP lease, verify DNS settings (use 8.8.8.8 / 1.1.1.1), factory reset if configuration is corrupted, and call your ISP to re-provision the modem MAC if all else fails.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Power Cycle (Unplug & Replug) | First step for any connectivity issue; clears transient errors and forces DHCP renegotiation | 2-5 min | None |
| Release & Renew DHCP Lease | When device shows 'connected but no internet' or has a self-assigned (169.254.x.x) IP address | 1-2 min | None |
| Change DNS to 8.8.8.8 / 1.1.1.1 | When internet works via IP ping but URLs fail to resolve (DNS failure) | 3-5 min | Low — reversible |
| Factory Reset via Reset Button | When configuration is corrupted, admin password is lost, or router is in a boot loop | 10-15 min | Medium — wipes all custom settings |
| Firmware Update via Admin UI | When known firmware bugs cause instability (e.g., WiFi dropping, intermittent outages) | 15-30 min | Medium — risk of brick if interrupted |
| ISP Re-Provisioning (Call ISP) | When modem is newly purchased, swapped, or shows upstream/downstream signal issues | 15-60 min | None (ISP-side change) |
| Replace Coax/Ethernet Cables | When signal levels are poor or you see intermittent packet loss at layer 1 | 5-10 min | None |
| Bridge Mode Reconfiguration | When double-NAT issues cause connectivity failures behind a third-party router | 20-30 min | Medium — requires reconfiguration |
Understanding Arris Router Issues
Arris manufactures a wide range of networking equipment including cable modems (SURFboard series), combo modem-routers (NVG443B, NVG468MQ), and WiFi gateways distributed by ISPs like AT&T, Comcast, and Cox. Despite their reliability, users frequently encounter symptoms like:
- 'No Internet Access' or 'Connected, no internet' in Windows network tray
- 'This site can't be reached' in browsers despite showing WiFi connected
- Arris WiFi box not working — devices connect to SSID but have no internet
- Arris modem not connecting to internet — all downstream/upstream lights off or blinking
- 169.254.x.x self-assigned IP on client devices
- 'Limited connectivity' on Android/iOS devices
These symptoms have distinct root causes and require different remediation paths.
Step 1: Identify Your Arris Device and Symptom
Before diving into fixes, identify your exact model:
- Arris SURFboard (e.g., SB6183, SB8200): Cable modem only — connect to a separate router
- Arris NVG443B: AT&T-issued DSL/fiber gateway combo unit
- Arris NVG468MQ: AT&T fiber residential gateway with built-in WiFi
- Arris TG-series (TG1672, TG3482): ISP-deployed combo modem-router
Now classify your symptom:
Symptom A — No lights / Modem won't boot: Hardware failure or power issue. Symptom B — Downstream light blinking, no lock: ISP signal problem; call your ISP. Symptom C — Online light solid but no internet on devices: DHCP, DNS, or provisioning issue. Symptom D — WiFi visible but no internet: Router WiFi NAT or DNS issue. Symptom E — Intermittent drops: Signal noise, firmware bug, or overheating.
Step 2: Check Physical Layer and Indicator Lights
For cable modems (SURFboard):
- Power: Solid green = OK
- Receive (DS): Solid green = downstream locked (8+ channels)
- Send (US): Solid green = upstream locked
- Online: Solid green = provisioned and connected to internet
- Link: Activity on Ethernet port
If DS or US lights are blinking, the modem cannot lock onto the cable signal. Check:
- Coax cable connection at the wall and modem — hand-tighten the F-connector
- Try a different coax port or cable
- Check for splitters — each splitter degrades signal by 3.5 dB; remove unnecessary ones
For AT&T Gateways (NVG443B / NVG468MQ):
- Broadband: Green = DSL/fiber link established
- Service: Green = internet provisioned
- WiFi: Green = 2.4GHz active; flashing = traffic
If Broadband is amber or red, the WAN link is not established — this is an ISP-side issue.
Step 3: Power Cycle the Correct Equipment in Order
This resolves the majority of transient Arris issues:
- Turn off all client devices (laptops, phones)
- Unplug your Arris modem from power — wait 30 full seconds (capacitors need to discharge)
- Unplug your router if it is a separate device — wait 30 seconds
- Plug in the modem — wait for the Online light to go solid (up to 3 minutes)
- Plug in the router — wait 60 seconds
- Reconnect client devices
⚠️ Do NOT use the power button or soft restart — a full power-off clears DRAM and forces a fresh DHCP handshake with the ISP's CMTS.
Step 4: Check and Renew IP Address on Client Devices
If your device shows a 169.254.x.x IP, it failed to get a DHCP lease from the Arris router.
Windows:
ipconfig /release
ipconfig /flushdns
ipconfig /renew
macOS:
sudo ipconfig set en0 DHCP
Linux:
sudo dhclient -r eth0 && sudo dhclient eth0
If renewal fails repeatedly, check whether DHCP is enabled in the Arris admin UI at http://192.168.0.1 or http://192.168.1.1.
Step 5: Diagnose DNS Failures
A common cause of 'Arris connected but no internet' is DNS failure — the IP path works but name resolution doesn't.
Test this from your terminal:
ping 8.8.8.8 # Test raw IP connectivity
nslookup google.com # Test DNS resolution
If ping 8.8.8.8 succeeds but nslookup google.com fails, your DNS is broken.
Fix: Log into your Arris admin interface and update DNS:
- Navigate to
http://192.168.0.1(or192.168.1.1) - Go to Basic > DNS or Advanced > DNS
- Set Primary DNS:
8.8.8.8, Secondary DNS:1.1.1.1 - Save and reboot
Alternatively, set DNS on your client device's network adapter directly.
Step 6: Arris NVG443B Specific Troubleshooting
The NVG443B is an AT&T-distributed gateway. Common issues:
- 'Broadband' LED amber: AT&T hasn't provisioned the device; call 1-800-288-2020
- WiFi 5GHz not visible: The 5GHz radio may be disabled — log into
http://192.168.1.254, go to Home Network > WiFi, enable 5GHz - Double NAT: If using a third-party router behind NVG443B, enable IP Passthrough: go to Firewall > IP Passthrough, select your router's MAC, save
- Admin credentials: Default username is
admin, password is printed on the device label
Step 7: Arris NVG468MQ Specific Troubleshooting
The NVG468MQ supports AT&T fiber (ONT input) and has a more aggressive firewall.
- Service LED blinking red: AT&T authentication failed — reboot, and if persistent, call AT&T
- WiFi dropping every few hours: Known firmware bug in versions prior to
9.2.2h0d83; update via Settings > Diagnostics > Update - 5GHz interference: Change WiFi channel from Auto to 36, 40, 44, or 48 in the WiFi settings
- Slow speeds on 2.4GHz: Enable channel bonding and set channel width to 40MHz
Step 8: Factory Reset as Last Resort
If configuration corruption is suspected:
- Locate the Reset pinhole on the back of the device
- With device powered ON, press and hold Reset with a paperclip for 15-30 seconds
- Release when all lights flash — device will reboot to factory defaults
- Reconfigure WiFi SSID/password and admin credentials
- If ISP-issued, you may need to call your ISP to re-provision after reset
⚠️ Factory reset erases all custom configuration including port forwarding rules, custom DNS, and WiFi credentials.
Step 9: Check Modem Signal Levels
For SURFboard and cable modems, poor signal causes intermittent outages. Access the modem diagnostic page:
- Go to
http://192.168.100.1(standard cable modem diagnostic IP) - Navigate to Signal or Status > Signal
- Check these values:
| Parameter | Acceptable Range |
|---|---|
| Downstream Power | -7 to +7 dBmV |
| Downstream SNR | >33 dB |
| Upstream Power | 38 to 48 dBmV |
| Upstream SNR | >25 dB |
If values are out of range, call your cable ISP — this requires a technician visit to check line amplifiers and splitters.
Step 10: When to Call Your ISP
Call your ISP immediately if:
- Online/Service LED never turns solid after 10+ minutes
- Modem logs show
T3 timeoutorT4 timeouterrors (upstream ranging failures) - You recently purchased a retail modem and haven't activated it
- You replaced your modem and it won't provision
- Signal levels are outside acceptable range
Arris retail SURFboard modems require MAC address registration with your ISP before first use.
Frequently Asked Questions
#!/usr/bin/env bash
# Arris Router Diagnostic Script
# Run on the client device connected to the Arris router
# Tested on macOS and Linux (use WSL or Git Bash on Windows)
echo "========================================"
echo " Arris Router Diagnostic Tool"
echo "========================================"
echo ""
# 1. Show current IP configuration
echo "[1] Current Network Interface Configuration:"
if command -v ip &> /dev/null; then
ip addr show
else
ifconfig
fi
echo ""
# 2. Check default gateway (router IP)
echo "[2] Default Gateway:"
if command -v ip &> /dev/null; then
ip route | grep default
else
netstat -rn | grep default
fi
GATEWAY=$(ip route 2>/dev/null | grep default | awk '{print $3}' || netstat -rn 2>/dev/null | grep default | awk '{print $2}' | head -1)
echo " Gateway IP: $GATEWAY"
echo ""
# 3. Ping gateway (Arris router)
echo "[3] Pinging Arris Gateway ($GATEWAY):"
ping -c 4 $GATEWAY 2>/dev/null || ping -n 4 $GATEWAY 2>/dev/null
echo ""
# 4. Ping ISP DNS (raw connectivity test)
echo "[4] Pinging Google DNS 8.8.8.8 (raw IP, no DNS):"
ping -c 4 8.8.8.8
echo ""
# 5. DNS resolution test
echo "[5] DNS Resolution Test:"
nslookup google.com 2>&1 | head -10
echo ""
# 6. Trace route to internet
echo "[6] Traceroute to 8.8.8.8 (first 10 hops):"
traceroute -m 10 8.8.8.8 2>/dev/null || tracert -h 10 8.8.8.8 2>/dev/null
echo ""
# 7. Check for self-assigned IP (APIPA 169.254.x.x = DHCP failed)
echo "[7] Checking for APIPA (169.254.x.x) self-assigned IP (indicates DHCP failure):"
if ip addr 2>/dev/null | grep -q '169.254'; then
echo " ⚠️ APIPA address detected! DHCP lease failed. Run DHCP release/renew."
elif ifconfig 2>/dev/null | grep -q '169.254'; then
echo " ⚠️ APIPA address detected! DHCP lease failed. Run DHCP release/renew."
else
echo " ✓ No APIPA address. DHCP appears successful."
fi
echo ""
# 8. Release and renew DHCP (Linux)
echo "[8] Attempting DHCP Release and Renew (Linux/macOS):"
INTERFACE=$(ip route 2>/dev/null | grep default | awk '{print $5}' | head -1 || route -n get default 2>/dev/null | grep interface | awk '{print $2}')
if [ -n "$INTERFACE" ]; then
echo " Interface: $INTERFACE"
echo " Releasing DHCP lease..."
sudo dhclient -r $INTERFACE 2>/dev/null || sudo ipconfig set $INTERFACE DHCP 2>/dev/null
sleep 2
echo " Requesting new DHCP lease..."
sudo dhclient $INTERFACE 2>/dev/null
echo " New IP configuration:"
ip addr show $INTERFACE 2>/dev/null || ifconfig $INTERFACE 2>/dev/null
else
echo " Could not detect default interface. Run manually: sudo dhclient -r eth0 && sudo dhclient eth0"
fi
echo ""
# 9. Flush DNS cache
echo "[9] Flushing DNS Cache:"
if command -v systemd-resolve &> /dev/null; then
sudo systemd-resolve --flush-caches && echo " ✓ systemd-resolved DNS cache flushed"
elif [[ "$(uname)" == "Darwin" ]]; then
sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder && echo " ✓ macOS DNS cache flushed"
else
echo " Run on Windows: ipconfig /flushdns"
fi
echo ""
# 10. Test alternate DNS resolution
echo "[10] Testing with Alternate DNS (1.1.1.1 - Cloudflare):"
nslookup google.com 1.1.1.1
echo ""
# 11. Access Arris modem diagnostic page
echo "[11] Arris Modem Admin Pages (access in browser):"
echo " Combo Gateway (NVG443B/NVG468MQ): http://192.168.1.254"
echo " Standard Router IP: http://192.168.0.1 or http://192.168.1.1"
echo " Cable Modem Diagnostics (SURFboard): http://192.168.100.1"
echo ""
# 12. Check MTU (misconfigured MTU causes partial connectivity)
echo "[12] MTU Check on Default Interface:"
if [ -n "$INTERFACE" ]; then
ip link show $INTERFACE 2>/dev/null | grep mtu || ifconfig $INTERFACE 2>/dev/null | grep mtu
echo " Recommended MTU for PPPoE: 1492 | Ethernet: 1500"
fi
echo ""
echo "========================================"
echo " Diagnostic Complete"
echo " If issues persist, factory reset the"
echo " Arris device and contact your ISP."
echo "========================================"Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network architects with 10+ years of experience in home networking, ISP infrastructure, and enterprise connectivity troubleshooting. Our guides are tested against real hardware and validated against official vendor documentation. We specialize in turning complex networking failures into actionable, step-by-step resolutions for both technical and non-technical users.
Sources
- https://www.arris.com/products/arris-surfboard-docsis-3-1-cable-modem/
- https://www.att.com/support/article/u-verse-high-speed-internet/KM1010905/
- https://community.att.com/t5/AT-T-Internet-Equipment/NVG468MQ-WiFi-dropping-frequently/td-p/5500000
- https://forums.xfinity.com/conversations/your-home-network/arris-surfboard-not-connecting-to-internet-after-power-cycle/60c3b8a8c6f4a40e57e87e2e
- https://stackoverflow.com/questions/tagged/networking
- https://kb.netgear.com/000060384/What-is-Double-NAT-and-why-is-it-bad
- https://www.cablelabs.com/insights/understanding-docsis-modem-provisioning