Why does my router show connected but there's no internet access?

This almost always means your device has a LAN/WiFi connection to the router, but the router itself has no WAN (upstream) connection, or DNS is broken. Check the router admin panel for WAN IP status — if it shows 0.0.0.0 or is blank, the ISP link is down. If WAN IP looks normal, change your DNS to 8.8.8.8 and 1.1.1.1 on the router. Also run 'ipconfig /release && ipconfig /renew' on Windows to refresh your device's IP lease.

My AT&T or Fios router keeps dropping connection every few hours — how do I fix it?

Intermittent drops on AT&T BGW320/G3100 or Fios G3100 are usually caused by: (1) overheating — ensure the router is in an open, ventilated space; (2) a firmware bug — check for updates in the admin panel under Diagnostics; (3) ISP line instability — call AT&T/Verizon to run a remote line test and check for signal errors. On Fios, also verify the MoCA coax connection is seated firmly. If using your own router behind the ISP device, enable IP Passthrough to eliminate double NAT issues.

How do I fix 'Default Gateway Is Not Available' on Windows?

This error means Windows cannot reach your router's IP. Try these steps in order: (1) Right-click the network adapter in Device Manager and select 'Update driver'. (2) Open cmd as admin and run: 'netsh winsock reset' then 'netsh int ip reset' then reboot. (3) Disable and re-enable the network adapter in Device Manager. (4) Check if your router's admin page is reachable at 192.168.1.1 — if not, the router needs a reboot. (5) As a last resort, uninstall the network adapter driver completely and let Windows reinstall it on reboot.

What causes slow WiFi speeds even with a good router?

The most common causes of slow WiFi despite having a capable router are: (1) Channel congestion — your neighbors' routers are on the same 2.4 GHz or 5 GHz channel. Use a WiFi analyzer app to find the least congested channel and set it manually. (2) Distance and obstacles — move the router to a central location, away from microwaves and cordless phones. (3) Old firmware — update firmware via the admin panel. (4) Too many devices on 2.4 GHz — move modern devices to the 5 GHz band. (5) ISP throttling — run a speed test via an Ethernet cable directly to the modem; if that's also slow, the issue is upstream.

How do I reset a router when I can't access the admin panel?

Use the physical factory reset button: locate the small recessed button on the back or bottom of the router, press and hold with a straightened paperclip or pin for 10–30 seconds (varies by model) until the status LEDs flash or change color. The router will reboot to factory defaults. Note: this erases all custom settings including WiFi name, password, port forwarding rules, and WAN credentials. After reset, use the credentials printed on the router label to log back in, then reconfigure from scratch and apply any firmware updates before reconnecting devices.

Router Problems & Solutions: Fix Common WiFi Router Issues (All Brands)

Diagnose and fix router problems fast. Covers AT&T, Fios, Frontier, Cisco, Google, Hitron, Motorola & more. Step-by-step solutions included.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,410 words

Key Takeaways

Root Cause 1: IP address conflicts, DHCP exhaustion, or incorrect DNS settings cause most 'no internet' errors even when the router shows a solid connection light.
Root Cause 2: Firmware bugs, overheating, and channel congestion are the leading causes of intermittent disconnections and slow speeds on broadband routers including AT&T, Fios, Frontier, Hitron, and Motorola models.
Root Cause 3: WAN/ISP authentication failures (PPPoE credential errors, incorrect MTU, or modem-router combo conflicts) break internet access at the provider handoff layer.
Quick Fix Summary: Power-cycle your router (unplug 30 seconds), run 'ipconfig /release && ipconfig /renew' on Windows or 'sudo dhclient -r && sudo dhclient' on Linux, then check for firmware updates in the router 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	Random drops, slow speeds, frozen admin UI	2-5 min	None
IP Renewal (ipconfig/dhclient)	Device shows connected but no internet; 'DHCP failed' errors	1-2 min	None
Factory Reset	Admin password lost, corrupted config, persistent failures after all other steps	10-20 min	Wipes all settings
Firmware Update	Known bugs, security patches, ISP-mandated updates (AT&T G3100, Hitron, Motorola)	10-15 min	Low (small brick risk if power cut)
Channel Change (WiFi)	Interference errors, slow WiFi speeds, neighbors on same channel	2-3 min	None
MTU Adjustment	Packet loss, sites partially loading, PPPoE 'fragmentation' errors	5 min	Low
ISP Line Test / Modem Swap	No WAN sync, DSL errors, Frontier/AT&T/Consolidated link-down alerts	30-60 min	None (requires ISP)
DNS Server Change	'DNS_PROBE_FINISHED_NXDOMAIN', slow resolution on all devices	2 min	None

Understanding Router Problems

Router problems manifest in several distinct ways: complete loss of internet access, intermittent drops, slow throughput, devices unable to connect, or the router admin page becoming unreachable. Understanding which layer the failure occurs at—hardware, LAN, WAN, or ISP—is the foundation of fast diagnosis.

Common Error Messages You Will See

"No Internet, Secured" (Windows) — device has WiFi but DHCP or DNS failed
"DNS_PROBE_FINISHED_NXDOMAIN" — DNS resolution broken, often wrong DNS server or ISP outage
"Default gateway is not available" — router IP unreachable; often a driver or IP conflict
"PPPoE authentication failed" or "WAN IP: 0.0.0.0" — incorrect credentials on DSL/fiber routers (AT&T, Frontier, Consolidated)
"DHCP failed" on macOS / "Obtaining IP address..." stuck on Android — DHCP pool exhausted or router daemon crashed
"Unable to reach 192.168.1.1" — admin panel unreachable; router in bad state or IP mismatch
"Broadband light flashing red" on modem-router combos (Hitron, Motorola, AT&T BGW320) — no WAN sync

Step 1: Identify the Failure Layer

Test 1 — Can you reach the router itself?

Ping your default gateway from a wired device:

ping 192.168.1.1

If this fails, the problem is between your device and the router (bad cable, wrong IP, driver issue).

Test 2 — Can the router reach the internet?

Log into the router admin panel (commonly 192.168.1.1, 192.168.0.1, 192.168.100.1, or 10.0.0.1 depending on brand).

AT&T BGW320/G3100 — 192.168.1.254
Fios G3100 / Quantum Gateway — 192.168.1.1
Hitron routers — 192.168.100.1
Google Nest WiFi — Google Home app or 192.168.86.1
Cisco/Linksys — 192.168.1.1
Frontier routers — 192.168.254.254
Consolidated Communications — varies; check label

Check the WAN/Broadband status page. If WAN IP is 0.0.0.0 or blank, the router has no upstream connection.

Test 3 — Is it DNS or routing?

Try pinging an IP directly to bypass DNS:

ping 8.8.8.8

If this works but ping google.com fails, DNS is broken.

Step 2: Fix by Problem Type

Problem A: No Internet Despite Connected WiFi

Power cycle: Unplug the router (and modem if separate) from power. Wait 30 seconds. Plug the modem in first, wait 60 seconds for WAN sync, then plug in the router.
Renew IP on affected device (see code block below).
Change DNS: In router admin panel, set primary DNS to 8.8.8.8 and secondary to 1.1.1.1.
If still failing, check the ISP status page for outages.

Problem B: Intermittent Drops / Random Disconnections

Common on Motorola, Hitron, and older AT&T modem-router combos.

Check router temperature: Routers that are hot to the touch need ventilation. Move it off carpet, add a small fan.
Check for channel congestion using WiFi analyzer tools. Switch from auto-channel to a manually selected non-overlapping channel (1, 6, or 11 for 2.4 GHz; 36, 40, 44, 48, 149, 153, 157, 161 for 5 GHz).
Update firmware: Log into admin panel → Administration → Firmware Update. For AT&T BGW320/G3100, AT&T pushes updates automatically but you can trigger a check under Diagnostics > Update.
Check for DHCP lease exhaustion: Admin panel → LAN → DHCP. If the lease pool (e.g., 192.168.1.100–200) is fully allocated, expand it or reduce lease time.
Disable IPv6 temporarily if your ISP doesn't support it — misconfigured IPv6 causes unpredictable drops on many consumer routers.

Problem C: PPPoE / WAN Authentication Failures (AT&T, Frontier, Consolidated, Broadband DSL)

Error seen in router logs: LCP: timeout sending Config-Requests or PADO timeout

In router admin panel, navigate to WAN / Internet Settings.
Confirm connection type is set to PPPoE (not DHCP or Static).
Re-enter your ISP username and password (AT&T uses your Gateway passkey; Frontier uses your account email as username).
MTU: Set WAN MTU to 1492 for PPPoE. Incorrect MTU causes partial page loads and packet loss.
Save and reboot the router.

Problem D: Fios G3100 Specific Problems

Common issue: coax MoCA connection dropping, ONT fallback to Ethernet.

Log into 192.168.1.1 → My Network → Network Connections.
If WAN shows "Broadband Connection (Ethernet)" but should be coax, verify MoCA is enabled.
Factory reset as last resort: hold reset button 10 seconds until power light blinks.

Problem E: Cisco Router Problems (Enterprise/SMB)

Cisco IOS routers show errors like %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to down

SSH into the router and run show ip interface brief to see interface states.
Run show log to review recent error messages.
For DHCP issues: show ip dhcp binding and clear ip dhcp binding *
For routing issues: show ip route to verify default route.

Problem F: Google Nest WiFi / Google Router Problems

Open Google Home app → your router → Settings → Test network.
If the Nest WiFi point (not the primary) is offline: factory reset the point (press reset button 10 sec) and re-add via app.
Check for WAN IP in the app: Settings → Network info. If WAN IP is missing, the ISP line or modem is at fault.

Problem G: Modem-Router Combo Double NAT

Seen with ISP-provided modem-router combos (Hitron, Motorola, AT&T BGW). Your own router behind one creates double NAT, causing game lag, VPN failures, and port-forwarding failures.

Put the ISP device into IP Passthrough (AT&T BGW) or Bridge Mode (Hitron/Motorola).
AT&T BGW320: Settings → Firewall → IP Passthrough → select your router's MAC.
Hitron: Advanced → Gateway Mode → set to Bridged.
After enabling bridge mode, reboot everything and check your own router gets a public WAN IP.

Step 3: Advanced — Factory Reset (Last Resort)

If all else fails and you can't access the admin panel:

Locate the recessed reset button (usually on the back/bottom).
Press and hold with a pin for 10 seconds (some models require 30 seconds) until LEDs flash.
Router returns to factory defaults. You must reconfigure SSID, password, WAN settings, and any port forwarding rules.
After reset, immediately update firmware before reconnecting all devices.

Brand-Specific Admin Panel Quick Reference

Brand	Default Gateway	Default User	Default Password
AT&T BGW/G3100	192.168.1.254	—	Printed on device
Fios G3100	192.168.1.1	admin	Printed on device
Google Nest WiFi	192.168.86.1	—	Google Home app
Hitron	192.168.100.1	cusadmin	password
Motorola	192.168.100.1	admin	motorola
Cisco (home)	192.168.1.1	admin	admin
Frontier	192.168.254.254	admin	Printed on device
Consolidated	192.168.0.1	admin	admin

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# Router Diagnostic & Fix Script
# Works on Linux/macOS. For Windows commands, see comments.
# ============================================================

echo "=== Step 1: Find Default Gateway ==="
# Linux:
ip route | grep default
# macOS:
# netstat -nr | grep default
# Windows (run in cmd): route print | findstr "0.0.0.0"

GATEWAY=$(ip route | grep default | awk '{print $3}' | head -1)
echo "Default Gateway: $GATEWAY"

echo ""
echo "=== Step 2: Ping Gateway ==="
ping -c 4 "$GATEWAY"
# Windows: ping -n 4 %GATEWAY%

echo ""
echo "=== Step 3: Test DNS (bypass DNS to check routing) ==="
ping -c 4 8.8.8.8
echo "If above works but domain resolution fails, DNS is broken."

echo ""
echo "=== Step 4: Test DNS Resolution ==="
nslookup google.com 8.8.8.8
# If this works but your normal DNS fails, change router DNS to 8.8.8.8

echo ""
echo "=== Step 5: Release and Renew DHCP Lease ==="
# Linux (replace eth0/wlan0 with your interface name):
INTERFACE=$(ip route | grep default | awk '{print $5}' | head -1)
echo "Interface: $INTERFACE"
sudo dhclient -r "$INTERFACE" && sudo dhclient "$INTERFACE"
# macOS: sudo ipconfig set en0 DHCP
# Windows (cmd as admin):
#   ipconfig /release
#   ipconfig /renew

echo ""
echo "=== Step 6: Check for IP Conflicts ==="
arping -I "$INTERFACE" -c 3 "$GATEWAY" 2>/dev/null || \
  echo "arping not installed. Run: sudo apt install arping"

echo ""
echo "=== Step 7: MTU Test (detect fragmentation issues) ==="
# Tests whether 1492 bytes pass without fragmentation (ideal for PPPoE)
ping -c 4 -M do -s 1464 8.8.8.8 2>/dev/null
if [ $? -ne 0 ]; then
  echo "MTU issue detected. Try setting WAN MTU to 1492 in router admin panel."
else
  echo "MTU looks fine."
fi

echo ""
echo "=== Step 8: WiFi Channel Info ==="
# Linux (requires iw):
sudo iw dev
iw dev "$INTERFACE" scan 2>/dev/null | grep -E 'SSID|freq|signal' | head -30
# macOS: /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -s

echo ""
echo "=== Step 9: Check Router Admin Page Reachability ==="
curl -s --connect-timeout 5 "http://$GATEWAY" -o /dev/null -w "HTTP Status: %{http_code}\n" || \
  echo "Router admin page unreachable at $GATEWAY"

echo ""
echo "=== Step 10: Flush DNS Cache ==="
# Linux (systemd-resolved):
sudo systemd-resolve --flush-caches 2>/dev/null || sudo resolvectl flush-caches 2>/dev/null
# macOS: sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
# Windows (cmd as admin): ipconfig /flushdns

echo ""
echo "=== Cisco IOS Quick Diagnostics (SSH to router) ==="
# Run these commands on a Cisco router via SSH:
# show ip interface brief
# show ip dhcp binding
# clear ip dhcp binding *
# show ip route
# show log | include %LINK|%OSPF|%BGP
# debug ip dhcp server events (disable with: undebug all)

echo "=== Diagnostic Complete ==="

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network architects with 10+ years of experience managing enterprise infrastructure, ISP integrations, and consumer networking gear. We specialize in translating complex system errors into clear, actionable troubleshooting guides covering routers, servers, cloud platforms, and developer tools.

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.