Why does my Netgear router show 'connected, no internet' even though all lights are green?

Green lights on a Netgear router only indicate the physical link is up (LAN and WAN ports are connected). 'No internet' typically means the router received a WAN link but either: (1) DNS resolution is failing — fix by setting DNS to 8.8.8.8 in Advanced → Internet Setup; (2) the WAN IP lease hasn't been assigned — click Release then Renew in Internet Setup; (3) there is a genuine ISP outage — check your ISP's status page; or (4) MTU mismatch on PPPoE lines — set MTU to 1492. Check each in order.

How do I fix a Netgear extender that is not working or shows no NETGEAR_EXT network?

First, factory reset the extender by holding the reset pinhole for 7 seconds. Move the extender within 15 feet of your router. Power it on and wait 60 seconds. Connect your device to the NETGEAR_EXT open Wi-Fi network, then open a browser and go to http://mywifiext.net to run the setup wizard. Alternatively, use WPS: press the WPS button on your router first, then within 2 minutes press WPS on the extender. Ensure your router is broadcasting on 2.4GHz, as many extenders require it for initial setup.

I can't access routerlogin.net or the Netgear admin panel. How do I get back in?

First, connect via a wired Ethernet cable directly to the router — wireless access to the admin panel can fail if the Wi-Fi association is in a bad state. Open a browser and try http://192.168.1.1 directly instead of routerlogin.net. Run 'ipconfig /flushdns' and 'arp -d *' on Windows to clear stale cache entries. If your IP address is 169.254.x.x, your DHCP lease failed — power-cycle the router. If you've forgotten the admin password, perform a factory reset (pin hold for 10 seconds with power on) and use the default credentials: username 'admin', password 'password'.

My Netgear Nighthawk keeps disconnecting from the internet randomly. What should I do?

Random disconnections on Nighthawk routers (R7000, R8000, RAX series) are most commonly caused by outdated firmware. Log into routerlogin.net, go to Advanced → Administration → Firmware Update, and apply the latest firmware. If using Dynamic IP, check whether your ISP has a short DHCP lease time — set your router's WAN DHCP lease renewal manually. Also check for 2.4GHz/5GHz interference: in Advanced Wireless Settings, try changing the 5GHz channel to a non-overlapping DFS channel (100, 116, or 132). If on DSL/PPPoE, MTU mismatch (default 1500 vs required 1492) can cause periodic TCP resets that appear as disconnects.

How do I troubleshoot the Netgear Nighthawk M6 Pro not connecting to the internet?

The M6 Pro connects via 5G/LTE, so troubleshooting differs from cable-connected routers. First, verify your SIM card is properly seated and your mobile data plan supports hotspot/router use (some plans block it). Check signal bars in the admin UI at http://192.168.1.1 — if below 2 bars, reposition the device near a window. Update firmware to the latest version (V1.0.1.130 or newer) which fixes known WAN drop bugs. If APN settings are wrong, go to Settings → Mobile → APN and enter your carrier's correct APN (e.g., T-Mobile: 'fast.t-mobile.com', AT&T: 'broadband'). If still failing, perform a factory reset.

Netgear Router Not Working or Not Connecting to Internet: Complete Troubleshooting Guide

Fix Netgear router, Nighthawk, and extender issues fast. Step-by-step troubleshooting for no internet, can't connect, and Wi-Fi not working problems.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,815 words

Key Takeaways

Root Cause 1: IP address conflicts or DHCP exhaustion — your router or extender fails to assign a valid IP, causing 'connected but no internet' symptoms.
Root Cause 2: Firmware bugs or corrupted settings — especially on Nighthawk models (R7000, R8000, M6 Pro), outdated firmware causes random disconnects and admin panel lockouts.
Root Cause 3: ISP-side issues or WAN cable failures — the router is healthy but the upstream modem or coaxial/fiber handoff is broken.
Root Cause 4: Extender placement and pairing failures — NETGEAR_EXT SSID disappears or fails to bridge because the extender is out of range or stuck in a bad state.
Quick Fix Summary: Power-cycle all devices in order (modem → router → extender → clients), update firmware via routerlogin.net, run a factory reset only as a last resort, and verify ISP WAN status before blaming the router.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power Cycle (modem → router → extender)	First step for any connectivity loss	3–5 min	None
Reboot via Admin UI (routerlogin.net)	Router is reachable but internet is down	2 min	None
Firmware Update via Nighthawk App or Web UI	Random drops, admin panel unresponsive, known bug fixes	10–15 min	Low — do NOT cut power mid-update
Change DNS to 8.8.8.8 / 1.1.1.1	Internet connected but DNS resolution fails ('no internet' despite link)	2 min	None
Release/Renew WAN IP via Admin UI	ISP DHCP lease stale after modem swap or outage	1 min	None
Factory Reset (pinhole reset)	Admin password lost, settings corrupted, last resort	15–30 min (full reconfiguration)	High — all settings wiped
Extender Re-sync (WPS or web setup)	NETGEAR_EXT not found, extender won't pair to router	5–10 min	Low
MTU Adjustment (PPPoE lines)	Pages load partially or HTTPS sites time out	3 min	Low

Understanding Netgear Router and Extender Failures

Netgear devices — including the Nighthawk R7000, R8000, RAX200, AX6000, M6 Pro, and the EX series extenders — share a common set of failure modes that span firmware, networking configuration, and hardware. Before touching any setting, it is critical to distinguish between three categories of failure:

Layer 1/2 failures: Physical link, bad cable, ISP outage, modem not synced.
Layer 3 failures: IP addressing, DHCP, DNS, NAT/routing table corruption.
Application/Firmware failures: Web UI lockout, Nighthawk app not finding router, firmware crash loop.

Step 1: Establish Baseline — Is the ISP the Problem?

Before rebooting anything, check whether your ISP has an outage. Many 'Netgear not working' calls are actually ISP outages.

Check your ISP's outage status page or call their automated line.
Look at the modem's sync light (typically labeled 'DS/US' or 'Online'). If it is blinking or red, the modem has not synced with your ISP — the router is innocent.
If you have a separate modem (not an all-in-one gateway), connect a laptop directly to the modem via Ethernet and run: ping -c 4 8.8.8.8. If that also fails, the issue is upstream.

Common error messages at this stage:

Browser shows: ERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_NO_INTERNET
Windows: No internet, secured under the Wi-Fi icon
macOS: Wi-Fi: No Internet Connection
Nighthawk App: Router not found on network or Unable to connect to router

Step 2: Power Cycle in the Correct Order

The single most effective fix for the majority of Netgear connectivity issues is a proper sequential power cycle. Order matters.

Unplug your modem from power. Wait 60 seconds (capacitors need to drain to clear DHCP state).
Unplug your Netgear router from power.
If you have a Netgear extender (EX3700, EX6120, EX7500, etc.), unplug it.
Power on the modem first. Wait for all lights to stabilize (DS/US and Online solid — can take 2–3 minutes on cable).
Power on the Netgear router. Wait 90 seconds.
Power on the extender. Wait 60 seconds.
Reconnect client devices.

This process forces fresh DHCP leases at every level and clears ARP/NAT state tables.

Step 3: Access the Router Admin Panel

If you cannot access routerlogin.net or 192.168.1.1, follow this checklist:

Connect via wired Ethernet, not Wi-Fi, to eliminate wireless association issues.
Flush your local DNS and ARP cache:
- Windows: ipconfig /flushdns then arp -d *
- macOS/Linux: sudo dscacheutil -flushcache (macOS) or sudo resolvectl flush-caches (Linux)
Confirm your local IP is in the correct subnet. Run ipconfig (Windows) or ip addr (Linux/macOS). Your IP should be 192.168.1.x or 192.168.0.x. If it is 169.254.x.x, your DHCP lease failed — power-cycle the router again.
Try accessing the admin panel by IP directly: http://192.168.1.1 (most Netgear routers) or http://192.168.0.1.
Disable any VPN or proxy on your machine before accessing the panel.
If using the Nighthawk app and it cannot find the router, toggle your phone's Wi-Fi off and on, ensure you are on the Netgear Wi-Fi SSID (not your extender SSID), and force-quit the app.

Step 4: Check and Update Firmware

Firmware bugs are responsible for a significant portion of Netgear Nighthawk problems, including the well-documented M6 Pro issues where the device drops WAN connection after 24–48 hours of uptime, or the R7000 series where older firmware causes DNS rebinding failures.

Via Web UI:

Log into http://routerlogin.net with your admin credentials (default: admin / password).
Navigate to Advanced → Administration → Firmware Update.
Click Check to check online, or download firmware manually from https://www.netgear.com/support/ and upload it.
Do not cut power during update. The process takes 3–5 minutes.

Via Nighthawk App:

Open the Nighthawk app, tap the router icon.
Tap Check for Updates. Apply if available.

Known problematic firmware versions (as of 2024):

Nighthawk R7000: Versions prior to V1.0.11.116 had WPA3 negotiation bugs.
Nighthawk M6 Pro: Firmware below V1.0.1.130 causes LTE band steering failures.
EX7500 Extender: Versions below V1.0.1.98 caused random NETGEAR_EXT SSID drops.

Step 5: Fix 'Connected but No Internet' (Netgear Connected No Internet)

This is the most common symptom: devices connect to the Netgear Wi-Fi, show full signal bars, but browsers return errors.

Check 1 — DNS: Log into the router admin panel → Advanced → Setup → Internet Setup and manually set DNS servers:

Primary DNS: 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare)
Secondary DNS: 8.8.4.4 or 1.0.0.1 Save and reboot.

Check 2 — MTU (critical for PPPoE/fiber connections): Many ISPs use PPPoE, which requires MTU of 1492 instead of the default 1500. Mismatched MTU causes HTTPS pages to hang while HTTP loads. In Admin UI: Advanced → Setup → WAN Setup → Set MTU to 1492.

Check 3 — WAN IP Release and Renew: In Admin UI: Advanced → Setup → Internet Setup → Click Release, wait 10 seconds, then click Renew. This forces a new DHCP lease from your ISP.

Check 4 — Double NAT: If your ISP provided a modem/router combo (gateway), your Netgear router may be receiving a private IP (10.x.x.x or 192.168.x.x) on its WAN port, causing double NAT. Either put the ISP gateway in bridge/passthrough mode or enable Netgear's router as an access point only.

Step 6: Fix Netgear Extender Not Working (NETGEAR_EXT Issues)

Symptom: You can't find the NETGEAR_EXT network, can't connect the extender to router, or the extender shows solid amber/red light.

Placement check: The extender must be within 15–20 feet of the main router during initial setup. Move it closer.
Factory reset the extender: Use a pin to press the reset button for 7 seconds until the power LED blinks. Reconfigure via http://mywifiext.net or the Nighthawk app.
WPS method: Press WPS on the router, then WPS on the extender within 2 minutes. The extender LED should turn solid green.
Manual web setup: Connect your laptop to the NETGEAR_EXT SSID (open network, no password initially). Navigate to http://mywifiext.net. Follow the setup wizard.
Check 2.4GHz vs 5GHz band: Some extenders only support 2.4GHz for the backhaul link. If your router has 5GHz-only mode enabled (band steering), disable it temporarily during extender setup.
Extender not bridging after setup: Log into http://mywifiext.net → check that the extender shows the router SSID as the connected network with strong signal (>-65 dBm).

Step 7: Can't Set Up Netgear Router (New Installation)

If you're setting up a new Netgear router and cannot complete setup:

Ensure the Ethernet cable from your modem goes to the Internet (WAN) port on the Netgear router, not a LAN port.
Use http://routerlogin.net or http://192.168.1.1 — NOT https (SSL is not available on initial setup).
If your ISP requires PPPoE credentials (common with DSL/fiber), have your username and password ready. Enter them in Internet Setup → Does your internet connection require a login? → Yes → PPPoE.
Disable browser extensions (especially uBlock, Privacy Badger) that may block the setup wizard's JavaScript.
Try setup from a wired connection on a computer rather than mobile.

Step 8: Factory Reset as Last Resort

Only perform a factory reset if all other steps fail, you are locked out of the admin panel, or firmware is corrupted (router stuck in boot loop).

Locate the reset pinhole on the back of the router.
With the router powered on, insert a pin and hold for 10 seconds until the power LED blinks amber.
Wait 2 minutes for the router to fully reset and reboot.
Reconnect to the default SSID (printed on the router label).
Navigate to http://routerlogin.net and run the setup wizard.

Note: The Nighthawk M6 Pro has a dedicated reset button (not a pinhole). Hold it for 10 seconds. The device will revert to factory LTE configuration.

Netgear Nighthawk M6 Pro Specific Problems

The M6 Pro is a 5G mobile hotspot/router combo that has specific known issues:

WAN dropping every 24–48 hours: Caused by a memory leak in firmware < V1.0.1.130. Update firmware.
Cannot access admin UI after carrier update: Perform a factory reset; carrier updates occasionally corrupt admin credentials.
5G SA vs NSA mode conflicts: In admin UI, manually set to NSA (Non-Standalone) if your carrier doesn't support SA.
USB-C passthrough not charging: Use a 65W+ PD charger; the unit draws significant power under 5G load.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# =============================================================
# Netgear Router Diagnostic Script
# Run on a client machine connected to the Netgear network
# Works on Linux/macOS; use WSL or Git Bash on Windows
# =============================================================

ROUTER_IP="192.168.1.1"   # Change to 192.168.0.1 if needed
EXTENDER_IP="192.168.1.2"  # Typical extender IP
TEST_HOST="8.8.8.8"
DNS_TEST_HOST="google.com"

echo "===== NETGEAR NETWORK DIAGNOSTIC ====="
echo "Timestamp: $(date)"
echo ""

# --- Step 1: Show local IP and gateway ---
echo "[1] LOCAL NETWORK INFO"
if command -v ip &>/dev/null; then
  ip addr show | grep -E 'inet |inet6'
  echo ""
  ip route show | grep default
else
  ifconfig | grep -E 'inet |inet6'
  netstat -rn | grep default
fi
echo ""

# --- Step 2: Ping router/gateway ---
echo "[2] PINGING ROUTER ($ROUTER_IP)"
ping -c 4 -W 2 "$ROUTER_IP" 2>&1
echo ""

# --- Step 3: Ping WAN (bypasses DNS) ---
echo "[3] PINGING INTERNET (raw IP - bypasses DNS)"
ping -c 4 -W 2 "$TEST_HOST" 2>&1
echo ""

# --- Step 4: DNS resolution test ---
echo "[4] DNS RESOLUTION TEST"
if command -v dig &>/dev/null; then
  echo "Using system DNS:"
  dig +short "$DNS_TEST_HOST" A
  echo "Using Google DNS directly:"
  dig +short "$DNS_TEST_HOST" A @8.8.8.8
  echo "Using Cloudflare DNS directly:"
  dig +short "$DNS_TEST_HOST" A @1.1.1.1
elif command -v nslookup &>/dev/null; then
  nslookup "$DNS_TEST_HOST"
  nslookup "$DNS_TEST_HOST" 8.8.8.8
fi
echo ""

# --- Step 5: Traceroute to identify where packets drop ---
echo "[5] TRACEROUTE (first 10 hops)"
if command -v traceroute &>/dev/null; then
  traceroute -m 10 -w 2 "$TEST_HOST" 2>&1
elif command -v tracepath &>/dev/null; then
  tracepath -m 10 "$TEST_HOST" 2>&1
fi
echo ""

# --- Step 6: Check MTU path (detect MTU mismatch) ---
echo "[6] MTU PATH CHECK (ping with 1472-byte payload = 1500 MTU)"
ping -c 2 -M do -s 1472 "$TEST_HOST" 2>&1
echo "If above fails, try PPPoE MTU (1464-byte payload = 1492 MTU):"
ping -c 2 -M do -s 1464 "$TEST_HOST" 2>&1
echo ""

# --- Step 7: Check router admin panel reachability ---
echo "[7] ROUTER ADMIN PANEL HTTP CHECK"
curl -s -o /dev/null -w "HTTP Status: %{http_code}\nTime: %{time_total}s\n" \
  --connect-timeout 5 "http://$ROUTER_IP/" 2>&1
echo ""

# --- Step 8: ARP table (detect IP conflicts) ---
echo "[8] ARP TABLE (look for duplicate IPs)"
if command -v arp &>/dev/null; then
  arp -n 2>/dev/null || arp -a
fi
echo ""

# --- Step 9: Flush DNS cache (macOS/Linux) ---
echo "[9] FLUSHING LOCAL DNS CACHE"
if [[ "$(uname)" == "Darwin" ]]; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
  echo "macOS DNS cache flushed."
elif command -v resolvectl &>/dev/null; then
  sudo resolvectl flush-caches
  echo "systemd-resolved cache flushed."
elif command -v systemd-resolve &>/dev/null; then
  sudo systemd-resolve --flush-caches
  echo "systemd-resolve cache flushed."
fi
echo ""

# --- Step 10: Netgear router API check (common endpoints) ---
echo "[10] NETGEAR ROUTER API PROBE"
curl -s -o /dev/null -w "routerlogin.net status: %{http_code}\n" \
  --connect-timeout 5 "http://routerlogin.net/" 2>/dev/null
curl -s -o /dev/null -w "mywifiext.net status: %{http_code}\n" \
  --connect-timeout 5 "http://mywifiext.net/" 2>/dev/null
echo ""

echo "===== DIAGNOSTIC COMPLETE ====="
echo "Share this output when filing a support ticket or forum post."

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network specialists with 10+ years of experience in consumer and enterprise networking. We cover Wi-Fi, routing, firmware, and ISP connectivity issues across major router brands including Netgear, ASUS, TP-Link, and Eero. Our guides are validated against real hardware in lab environments before publication.

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.