No Internet on Verizon: Fix 'Verizon Internet Gateway No Internet Connection' Error
Fix Verizon no internet connection errors fast. Step-by-step guide for Verizon FiOS, router, and gateway issues with diagnostic commands and proven fixes.
- Most Verizon no internet connection errors stem from a dropped WAN link, DHCP lease failure, or ONT (Optical Network Terminal) sync loss — identifiable by the router's WAN/Internet LED status.
- Verizon FiOS gateway devices (G3100, CR1000A) cache stale IP leases; a full power-cycle sequence (ONT → router → devices) resolves the majority of outages without a technician call.
- DNS misconfiguration or IPv6 negotiation failure can cause the gateway to show a connected WAN link but deliver no usable internet — fix by forcing DNS to 8.8.8.8/1.1.1.1 or disabling IPv6 temporarily.
- If the WAN IP shows 169.254.x.x (APIPA) or 0.0.0.0, the gateway failed DHCP from Verizon's BRAS — release/renew the WAN lease or clone the router's MAC address.
- Quick fix summary: power-cycle ONT and router in sequence, check gateway admin panel at 192.168.1.1 for WAN status, run the diagnostic commands below, escalate to Verizon support only after confirming the ONT sync light is solid green.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Full power-cycle (ONT → router → devices) | First response to any Verizon no internet connection event | 5–10 min | None |
| WAN DHCP release/renew via admin panel | WAN IP is 0.0.0.0 or 169.254.x.x after power-cycle | 2–5 min | Very Low |
| DNS override (8.8.8.8 / 1.1.1.1) | WAN IP assigned but DNS queries fail or time out | 2 min | Very Low |
| Disable IPv6 on gateway | IPv6 negotiation loop preventing dual-stack connectivity | 3 min | Low — may affect IPv6-only services |
| MAC address clone on router | ISP authenticates by MAC and old device was swapped | 5 min | Low |
| Factory reset gateway (G3100 / CR1000A) | Persistent misconfiguration surviving reboots | 20–30 min | Medium — erases custom config |
| Coaxial/Ethernet cable swap (MoCA/ONT side) | Physical layer errors, packet loss > 5% on ONT link | 10 min | None |
| Verizon technician dispatch | ONT sync light blinking/off after all software fixes | 1–3 days | None (external) |
Understanding the 'No Internet' Error on Verizon
When your Verizon gateway or FiOS router displays a yellow/red internet LED or the admin panel at 192.168.1.1 reports "No Internet Connection" or "WAN Disconnected", the problem can exist at one of four layers:
- Physical / Optical layer — ONT sync loss, damaged coax or Ethernet from ONT to router
- WAN / DHCP layer — Gateway failed to obtain a valid public IP from Verizon's BRAS servers
- DNS layer — IP obtained but name resolution broken
- Application layer — Firewall rule, VLAN misconfiguration, or firmware bug
Understanding which layer is broken cuts resolution time from hours to minutes.
Step 1: Identify the Symptom Precisely
Before touching any hardware, capture the exact error state.
Check the gateway LED pattern:
- Solid white/green — WAN connected normally
- Solid yellow — WAN connected, internet service degraded or blocked
- Blinking white — Connecting / negotiating
- Solid red — No WAN link at all
- Off — Device unpowered or hardware fault
Check admin panel WAN status:
- Open a browser and navigate to
http://192.168.1.1(default for G3100, CR1000A, and older MI424WR). - Log in (default credentials are on the gateway label — commonly
admin/ last 8 digits of serial). - Navigate to My Network → Network Connections → Broadband Connection (Ethernet/Coax).
- Note the IP Address, Status, and DNS Servers fields.
Expected healthy output:
IP Address: 71.x.x.x (public Verizon address)
Subnet: 255.255.255.252
Gateway: 71.x.x.1
DNS1: 71.3.x.x
DNS2: 71.3.x.x
Status: Connected
Problem indicators:
- IP shows
0.0.0.0→ DHCP failure - IP shows
169.254.x.x→ APIPA fallback, no DHCP response from upstream - Status shows
"Authenticating"loop → PPPoE auth issue (rare on FiOS, common on DSL)
Step 2: Power-Cycle the Full Stack (Most Effective First Step)
The majority of Verizon internet gateway no internet connection issues resolve with a proper sequenced power-cycle — not a simultaneous restart.
Correct sequence:
- Unplug the ONT (usually a white box on exterior wall or in basement) — wait 60 seconds.
- Unplug the Verizon router/gateway — wait 30 seconds.
- Power on the ONT first — wait until the PON and Ethernet/Coax LEDs are solid (typically 90–120 seconds).
- Power on the router/gateway — wait 2–3 minutes for full WAN negotiation.
- Reconnect client devices — test with a wired connection before troubleshooting Wi-Fi.
Why order matters: The ONT must complete optical sync and signal the BRAS before the router sends a DHCP Discover. If the router boots first, its DHCP request goes unanswered and it falls back to 169.254.x.x.
Step 3: Diagnose from a Connected Client
From a PC/Mac connected via Ethernet to the Verizon router:
Test 1 — Can you reach the gateway?
ping 192.168.1.1
If this fails, your local LAN is broken (bad cable, wrong NIC settings).
Test 2 — Can you reach Verizon's DNS?
ping 71.3.128.3
# Verizon primary DNS
Test 3 — Can you reach a public IP (bypasses DNS)?
ping 8.8.8.8
If 8.8.8.8 responds but google.com does not, the problem is DNS only.
Test 4 — Trace the path to identify where packets die:
traceroute 8.8.8.8 # Linux/macOS
tracert 8.8.8.8 # Windows
If the trace dies at hop 1 (192.168.1.1), the WAN link is down. If it dies at hop 2 (Verizon's first router), there is a Verizon-side outage.
Step 4: Force WAN DHCP Release and Renew
If power-cycle did not restore the connection and the WAN IP is invalid:
- Log in to
http://192.168.1.1. - Go to My Network → Network Connections → Broadband Connection.
- Click Release (releases the current WAN lease).
- Wait 10 seconds, then click Renew.
- Watch the IP Address field — it should populate with a public
71.x.x.xor96.x.x.xaddress within 30 seconds.
Alternatively, using the router's built-in CLI (if SSH is enabled on advanced models):
ssh admin@192.168.1.1
ip dhcp client force-renew eth0
Step 5: Fix DNS if WAN IP Is Valid But No Sites Load
If ping 8.8.8.8 works but ping google.com fails, DNS is broken.
Option A — Override DNS on your client (temporary test):
# Linux
sudo resolvectl dns eth0 8.8.8.8 1.1.1.1
# macOS
networksetup -setdnsservers "Ethernet" 8.8.8.8 1.1.1.1
# Windows (PowerShell as Administrator)
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 8.8.8.8,1.1.1.1
Option B — Override DNS on the gateway for all clients:
- Admin panel → My Network → Network Connections → Home/Office Network.
- Edit the LAN settings and change DNS Server from Automatic to Manual.
- Enter
8.8.8.8(Primary) and1.1.1.1(Secondary). - Save and reboot the gateway.
Step 6: Disable IPv6 If Dual-Stack Negotiation Is Looping
Some Verizon gateways enter an IPv6 negotiation loop that blocks all traffic while the router waits for a valid IPv6 prefix.
- Admin panel → My Network → Network Connections → Broadband Connection (Ethernet).
- Scroll to IPv6 section.
- Set IPv6 Address Distribution to Disabled.
- Save and reboot.
- Test connectivity — if restored, re-enable IPv6 after a firmware update or contact Verizon to reset your IPv6 delegation.
Step 7: Check for a Verizon Outage
Before dispatching a technician, confirm whether the outage is localized:
- Visit downdetector.com/status/verizon from a mobile data connection.
- Check the Verizon My Fios app → Internet tab for service alerts.
- Call Verizon support at 1-800-837-4966 and use the automated system to check for area outages.
If the ONT's PON light is off or blinking red after 10+ minutes, there is a fiber signal issue that requires a Verizon field technician.
Step 8: Factory Reset as Last Resort
If the gateway survives reboots with broken configuration:
- Locate the Reset pinhole on the back of the G3100 or CR1000A.
- Hold with a straightened paperclip for 10 seconds until LEDs cycle.
- Wait 3–5 minutes for full reboot.
- Reconfigure Wi-Fi SSID, password, and any port forwarding rules.
Warning: Factory reset erases all custom firewall rules, static IP reservations, and UPnP settings. Document your config before resetting.
Frequently Asked Questions
#!/usr/bin/env bash
# ============================================================
# Verizon No Internet Diagnostic Script
# Run from a device connected via Ethernet to the Verizon router
# Tested on Linux/macOS; adapt ping/traceroute flags for Windows
# ============================================================
GATEWAY="192.168.1.1"
VZ_DNS="71.3.128.3"
PUBLIC_IP="8.8.8.8"
TEST_HOST="google.com"
echo "====================================================="
echo " Verizon Internet Diagnostic - $(date)"
echo "====================================================="
# --- Step 1: Local gateway reachability ---
echo ""
echo "[1] Pinging local gateway ($GATEWAY)..."
if ping -c 3 -W 2 "$GATEWAY" > /dev/null 2>&1; then
echo " PASS: Gateway is reachable"
else
echo " FAIL: Cannot reach gateway. Check LAN cable or NIC settings."
fi
# --- Step 2: Check local IP and default route ---
echo ""
echo "[2] Local IP configuration:"
ip route show default 2>/dev/null || route -n get default 2>/dev/null || ipconfig
echo ""
ip addr show 2>/dev/null || ifconfig 2>/dev/null | grep -A2 'eth\|en'
# --- Step 3: Ping Verizon DNS (tests WAN routing) ---
echo ""
echo "[3] Pinging Verizon DNS server ($VZ_DNS)..."
if ping -c 3 -W 3 "$VZ_DNS" > /dev/null 2>&1; then
echo " PASS: Verizon network reachable"
else
echo " FAIL: Cannot reach Verizon DNS. WAN link may be down."
fi
# --- Step 4: Ping public IP (bypass DNS) ---
echo ""
echo "[4] Pinging public IP $PUBLIC_IP (DNS-independent test)..."
PING_RESULT=$(ping -c 4 -W 3 "$PUBLIC_IP" 2>&1)
if echo "$PING_RESULT" | grep -q 'bytes from'; then
echo " PASS: Public internet reachable via IP"
echo " $(echo "$PING_RESULT" | tail -2)"
else
echo " FAIL: Cannot reach $PUBLIC_IP. WAN or upstream routing issue."
fi
# --- Step 5: DNS resolution test ---
echo ""
echo "[5] Testing DNS resolution for $TEST_HOST..."
DNS_RESULT=$(dig +time=3 +tries=1 "$TEST_HOST" 2>/dev/null || nslookup "$TEST_HOST" 2>&1)
if echo "$DNS_RESULT" | grep -qiE 'ANSWER SECTION|Address:'; then
echo " PASS: DNS resolution working"
else
echo " FAIL: DNS resolution failed. Try overriding DNS to 8.8.8.8"
echo " Fix (Linux): sudo resolvectl dns eth0 8.8.8.8 1.1.1.1"
echo " Fix (macOS): networksetup -setdnsservers Ethernet 8.8.8.8 1.1.1.1"
echo " Fix (Windows): Set-DnsClientServerAddress -InterfaceAlias Ethernet -ServerAddresses 8.8.8.8,1.1.1.1"
fi
# --- Step 6: Traceroute to identify where packets die ---
echo ""
echo "[6] Traceroute to $PUBLIC_IP (first 6 hops)..."
traceroute -m 6 -w 2 "$PUBLIC_IP" 2>/dev/null || tracert -h 6 "$PUBLIC_IP" 2>/dev/null
# --- Step 7: Check for packet loss on gateway link ---
echo ""
echo "[7] Packet loss test to gateway (20 pings)..."
ping -c 20 -i 0.2 "$GATEWAY" 2>/dev/null | tail -3
# --- Step 8: MTU test (catches PPPoE MTU black hole) ---
echo ""
echo "[8] MTU path test to $PUBLIC_IP..."
ping -c 1 -M do -s 1472 "$PUBLIC_IP" > /dev/null 2>&1 && echo " PASS: MTU 1500 OK" || echo " WARN: MTU issue detected. Try setting WAN MTU to 1492 on gateway."
echo ""
echo "====================================================="
echo " Diagnostic complete. Review FAILs above."
echo " Gateway admin panel: http://$GATEWAY"
echo " Verizon support: 1-800-837-4966"
echo "====================================================="Error Medic Editorial
Error Medic Editorial is a team of senior DevOps, SRE, and network engineers with 10+ years of experience diagnosing and resolving ISP connectivity issues, cloud infrastructure failures, and home network problems. Our guides are tested against real hardware and validated against official vendor documentation before publication.
Sources
- https://www.verizon.com/support/residential/internet/highspeed/general-support/equipment/questionsone/121786.htm
- https://forums.verizon.com/t5/Fios-Internet/G3100-No-Internet-Connection-after-power-outage/td-p/975432
- https://superuser.com/questions/1594843/verizon-fios-g3100-wan-ip-shows-169-254-no-internet
- https://www.reddit.com/r/Fios/comments/internet_gateway_no_internet_fix_guide/
- https://support.verizon.com/s/article/Verizon-Router-Light-Status-Meanings