Why does my router keep disconnecting every few hours?

Intermittent disconnections are usually caused by: (1) DHCP lease expiration where the ISP does not renew — set your router's WAN connection type to 'Keep Alive' or 'Always On'; (2) Overheating — ensure the router has at least 5cm clearance on all sides; (3) Firmware bugs — check for updates at your admin panel; (4) ISP line instability — check router logs for repeated WAN disconnection events and share with ISP support as evidence.

My router shows connected but there is no internet access — what does this mean?

This means your device has a valid LAN IP from the router's DHCP server, but the router itself has no WAN connectivity. Check: (1) The WAN IP in your router admin panel — if it shows 0.0.0.0 or is blank, the ISP is not assigning an address; (2) Log in to admin panel and look for error messages like 'PPPoE authentication failed' or 'DHCP timeout'; (3) Power-cycle the modem/ONT separately from the router; (4) Contact your ISP — they may need to reset the line from their end or re-provision your device's MAC address.

How do I fix AT&T router problems where the broadband light is red?

A red broadband light on AT&T gateways (BGW320, BGW210, NVG599) indicates loss of WAN connectivity. Steps: (1) Reboot the ONT (fiber box outside or in garage) by unplugging power for 60 seconds; (2) Reboot the AT&T gateway; (3) Check the fiber cable from ONT to gateway for physical damage; (4) Log in to 192.168.1.254 and check the Broadband > Status page for specific error codes; (5) Call AT&T at 1-800-288-2020 if the ONT shows a red PON or LOS light — this indicates a fiber signal issue that only AT&T technicians can resolve.

What are common Verizon Fios G3100 router problems and how do I fix them?

The G3100's most common issues include: (1) Wi-Fi 6 / WPA3 compatibility — fix by enabling WPA2/WPA3 mixed mode in Wi-Fi settings; (2) MoCA interference causing packet loss — add a MoCA POE filter on the coax line entry; (3) Slow DNS resolution — set client devices to use 1.1.1.1 or 8.8.8.8 instead of the router's DNS relay; (4) Fios TV Multi-Room DVR not working — ensure MoCA 2.5 is enabled in the G3100's network settings; (5) Router not accepting admin password — factory reset using the pinhole button on the back for 15 seconds.

How do I fix double NAT problems with a modem-router combo?

Double NAT occurs when both your ISP's modem-router and your own router each perform Network Address Translation, causing issues with port forwarding, VPNs, and gaming. Solutions: (1) Best solution — put the ISP modem-router in Bridge Mode (disables its NAT/routing), then let your router handle everything; (2) Alternative — enable DMZ on the ISP router pointing to your router's WAN IP; (3) Quick workaround — use only the ISP router and disable your own router entirely. To enable bridge mode: log in to your ISP router admin panel, find 'Gateway Mode,' 'WAN Mode,' or 'Bridge Mode' settings — the exact location varies by brand (Hitron, Motorola, Arris).

Router Problems: Complete Troubleshooting Guide for All Major Brands (AT&T, Fios, Cisco, Google & More)

Fix router problems fast: step-by-step solutions for AT&T, Fios, Frontier, Cisco, Google, Hitron, Motorola & more. Diagnose and resolve in minutes.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,410 words

Key Takeaways

Most router problems stem from firmware bugs, IP/DHCP conflicts, overheating, or ISP-side outages — not hardware failure.
AT&T, Fios (G3100), Frontier, Consolidated Communications, and Cisco routers each have model-specific quirks such as WPA3 handshake failures, IPv6 conflicts, and BGP misconfiguration.
Quick fix summary: Power-cycle the router (unplug 30 seconds), check ISP status, run a factory reset as a last resort, and update firmware via the admin panel (typically 192.168.1.1 or 192.168.0.1).

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle (soft reboot)	Intermittent drops, slow speeds, DHCP renewal needed	2–5 min	None
Firmware update via admin UI	Known bugs, security patches, feature fixes	10–20 min	Low (brief outage)
Factory reset (hard reset)	Persistent misconfiguration, forgotten credentials	15–30 min	Medium (loses all settings)
Change DNS servers (8.8.8.8)	DNS resolution failures, slow browsing despite good speed	2 min	None
Switch Wi-Fi channel/band	Interference, slow throughput, neighbor congestion	3–5 min	None
Replace Ethernet cable / SFP	Physical layer errors, CRC errors on WAN port	5 min	None
Contact ISP / provision modem	No WAN IP, PPPoE auth failure, line sync issues	30–60 min	None
MTU adjustment (PPPoE: 1492)	Websites partially load, large packets dropped	5 min	Low

Understanding Router Problems

A router connects your local network to the internet. When it misbehaves, symptoms range from complete internet outages to intermittent packet loss, slow throughput, or Wi-Fi dead zones. Understanding where the problem lives — the WAN side (between your router and ISP), the LAN side (between your devices and router), or inside the router itself — is the first diagnostic step.

Common Error Messages You May See

No internet, secured (Windows) — router has LAN connectivity but no WAN IP
DHCPDISCOVER timeout in router logs — ISP not responding to DHCP requests
PPPoE: LCP timeout — PPPoE authentication failing (common on Frontier, AT&T DSL)
Default gateway is not available — driver or DHCP issue on client side
ERR_NAME_NOT_RESOLVED — DNS failure
169.254.x.x self-assigned IP — DHCP server not responding
Cisco IOS: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to down

Step 1: Isolate the Problem Layer

1a. Check ISP Status First Before touching your router, verify whether your ISP has an outage:

AT&T: https://www.att.com/internet/outage/
Verizon Fios: https://www.verizon.com/home/outage/
Frontier: https://outage.frontier.com/
Consolidated Communications: ISP status page or call 1-800-695-8592
Google Fi/Google Wifi: Google Home app → network status

1b. Confirm the WAN IP Log in to your router admin panel (commonly 192.168.1.1, 192.168.0.1, or 10.0.0.1 depending on brand):

AT&T BGW320/BGW210: 192.168.1.254
Verizon G3100 (Fios): 192.168.1.1
Google Nest Wifi: Google Home app
Hitron CODA/CGN: 192.168.0.1
Motorola MG series: 192.168.100.1

Navigate to WAN Status or Broadband tab. If the WAN IP is 0.0.0.0 or blank, the router is not getting an address from your ISP — this is an ISP or provisioning issue.

1c. Ping the Gateway From a connected device:

ping 192.168.1.1       # confirm LAN connectivity
ping 8.8.8.8           # confirm WAN/routing
ping google.com        # confirm DNS

If ping 192.168.1.1 fails, the LAN side is broken (bad cable, wrong subnet, DHCP issue). If ping 8.8.8.8 succeeds but ping google.com fails, it's purely a DNS problem.

Step 2: Fix by Brand and Symptom

AT&T Router Problems (BGW320, BGW210, NVG599)

AT&T uses a combination of fiber ONT and a residential gateway. Common issues:

Red broadband light: ONT fiber signal lost. Reboot the ONT (small white box on exterior wall) by unplugging its power for 60 seconds.
IP Passthrough not working: Go to 192.168.1.254 → Firewall → IP Passthrough. Enter the MAC address of your downstream router. Set allocation mode to DHCPS-fixed.
Double NAT: AT&T gateway + your router creates double NAT. Use IP Passthrough (above) or DMZ to your router's LAN IP.
PPPoE failure: AT&T fiber does NOT use PPPoE on most setups — if you see PPPoE errors, your router is misconfigured. Set WAN type to DHCP.

Verizon Fios G3100 Router Problems

The G3100 is a capable but occasionally finicky router:

Wi-Fi 6 compatibility issues: Some older devices fail WPA3 handshake. Go to My Fios app or 192.168.1.1 → Wi-Fi Settings → Security → change from WPA3 to WPA2/WPA3 mixed.
MoCA conflicts: G3100 uses MoCA 2.5 for backhaul. If you have cable TV splitters, add a MoCA POE filter at the coax entry point.
DNS relay loop: G3100 sometimes causes slow DNS. Set client DNS manually to 8.8.8.8 or 1.1.1.1 as a workaround.
Firmware update: Fios routers update automatically but you can force-check at 192.168.1.1 → System Settings → Check for Update.

Frontier Router Problems

Frontier uses a mix of ISP-provided routers (Arris, Zyxel, Eero):

PPPoE credentials: Frontier fiber still uses PPPoE in many areas. Credentials are printed on the router label or obtainable from Frontier support.
Eero provisioning failure: If the Eero provided by Frontier shows solid red, it failed to provision. Factory reset: hold reset button 15 seconds until LED flashes red.
IPv6 issues: Frontier's IPv6 rollout is inconsistent. If seeing connectivity issues, try disabling IPv6 on the router WAN settings.

Cisco Router Problems (ISR, RV Series, Small Business)

Cisco routers are common in SMB environments:

Interface down: show interfaces to identify physical layer issues. Check cable, SFP module, duplex mismatch.
DHCP pool exhausted: show ip dhcp binding — if pool is full, increase pool range or reduce lease time.
BGP stuck in Active state: Verify peer IP, AS number, and that TCP port 179 is not blocked by ACL.
RV340 firmware bug (1.0.03.x): Known VPN stability bug. Upgrade to 1.0.03.29 or later via Administration → Firmware.
NAT overload (PAT): show ip nat translations — if maxed out, increase ip nat translation max-entries.

Google Router Problems (Google Wifi, Nest Wifi, Nest Wifi Pro)

Solid orange light: No internet. Power-cycle ONT/modem, then router. Wait 2 minutes between each.
Factory reset: Hold reset button on each node for 10 seconds until LED pulses. Reconfigure in Google Home app.
Mesh node offline: Relocate node — must be within ~15m of another node with line of sight.
Double NAT with ISP modem: Put ISP modem in bridge mode, or use Google router in DHCP passthrough mode.

Hitron Router Problems (CODA-4582, CGN3)

CODA-4582 OFDM channel issues: Log in to 192.168.0.1 → Signal → confirm OFDM channels are locked. If not, contact ISP to check signal levels.
Bridge mode: Log in → Basic → Gateway Function → set to Disable (bridge mode). ISP may need to reprovision.

Motorola Router Problems (MG7700, MG8702)

MG8702 double NAT: Ensure ISP has provisioned the modem. Admin panel at 192.168.100.1.
Bonded channel issues: Check downstream/upstream channel bonding counts. Fewer than 8 downstream channels usually indicates signal or splitter issues.

Broadband / Modem-Router Combo Problems

IP conflict (two DHCP servers): If you connect a router behind a modem-router combo, both may run DHCP. Put the modem-router in bridge mode to disable its DHCP/NAT.
Slow speeds: Run speedtest-cli from a wired device directly connected to the modem. If fast, the issue is Wi-Fi or router throughput.

Step 3: Advanced Diagnostics

Check for packet loss:

mtr --report google.com

Check Wi-Fi interference: Use iwlist or nmcli to scan for overlapping channels. On 2.4 GHz, use channels 1, 6, or 11 only.

Check router CPU/memory via SNMP or admin UI: High CPU (>80%) causes packet drops. Common causes: excessive NAT sessions, firewall rules, or malware on LAN devices.

Check for rogue DHCP server on LAN:

nmap --script broadcast-dhcp-discover

MTU troubleshooting (PPPoE connections): PPPoE reduces MTU from 1500 to 1492. If large pages fail to load:

ping -s 1464 -M do 8.8.8.8    # Linux
ping -f -l 1464 8.8.8.8        # Windows

If this fails, lower MTU on WAN interface to 1452 or 1440.

Step 4: When to Factory Reset

Factory reset erases all configuration. Do this only after:

Power-cycle has not resolved the issue
You cannot access the admin panel
Firmware update has not helped
You suspect misconfiguration

Document your current settings (ISP credentials, port forwards, SSID/passwords) before resetting. Most routers: hold the physical reset button for 10–30 seconds until lights flash.

Step 5: When to Replace Hardware

Replace your router if:

It runs hot to the touch and rebooting temporarily fixes issues (capacitor failure)
Wi-Fi range has significantly degraded over time (radio hardware aging)
The router is more than 5 years old and firmware updates have stopped
You see persistent CRC errors or physical interface errors that survive cable replacement

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# Router Diagnostic Script
# Run from a Linux/macOS client connected to the router
# ============================================================

ROUTER_IP="192.168.1.1"   # Change to your router's IP
DNS_TEST="8.8.8.8"
DOMAIN_TEST="google.com"

echo "=== [1] Checking local IP and gateway ==="
ip route show          # Linux
# netstat -rn          # macOS / older Linux

echo ""
echo "=== [2] Ping gateway (LAN health) ==="
ping -c 4 "$ROUTER_IP"

echo ""
echo "=== [3] Ping public DNS (WAN/routing health) ==="
ping -c 4 "$DNS_TEST"

echo ""
echo "=== [4] DNS resolution test ==="
nslookup "$DOMAIN_TEST" "$DNS_TEST"

echo ""
echo "=== [5] Traceroute to detect where packets drop ==="
traceroute -n "$DOMAIN_TEST"   # Linux
# tracert "$DOMAIN_TEST"       # Windows equivalent

echo ""
echo "=== [6] MTU path discovery (PPPoE fix) ==="
# Test with 1464 bytes (1464 + 28 ICMP/IP header = 1492 PPPoE MTU)
ping -c 2 -s 1464 -M do "$DNS_TEST" && echo "MTU 1492 OK" || echo "MTU too large — lower WAN MTU to 1452"

echo ""
echo "=== [7] Check for rogue DHCP servers on LAN ==="
# Requires nmap
if command -v nmap &>/dev/null; then
  sudo nmap --script broadcast-dhcp-discover -e eth0 2>/dev/null
else
  echo "nmap not installed — run: sudo apt install nmap"
fi

echo ""
echo "=== [8] Wi-Fi channel scan (2.4GHz and 5GHz) ==="
if command -v nmcli &>/dev/null; then
  nmcli dev wifi list
else
  # macOS alternative
  /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -s 2>/dev/null
fi

echo ""
echo "=== [9] Continuous packet loss monitor (MTR) ==="
echo "Run: mtr --report --report-cycles 20 google.com"
echo "This shows per-hop latency and packet loss over 20 cycles."

# ---- Cisco IOS Commands (run from router CLI, not bash) ----
# show interfaces GigabitEthernet0/0
# show ip dhcp binding
# show ip dhcp pool
# show ip nat translations
# show log | include %LINK
# debug ip dhcp server events
# show version   (firmware/IOS version)

# ---- AT&T BGW320 Admin API check (browser or curl) ----
# curl -s http://192.168.1.254/cgi-bin/broadbandstatistics.ha | grep -i 'ipaddress\|status'

# ---- Check router DNS from client ==="
# Compare results from router DNS vs. public DNS:
nslookup "$DOMAIN_TEST"        # uses system default (usually router)
nslookup "$DOMAIN_TEST" 1.1.1.1  # uses Cloudflare DNS directly

echo ""
echo "=== Diagnostics Complete ==="

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, network administrators, and SRE professionals with 10+ years of experience diagnosing and resolving infrastructure issues across ISP, enterprise, and home network environments. We've worked with Cisco, Juniper, and consumer router platforms at scale, and we translate that expertise into clear, actionable troubleshooting guides for engineers and end users alike.

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.