Distinct consumer questions

Home networking troubleshooting

Routers that restart, Wi-Fi that drops, mesh nodes with a weak link and devices with no internet: how to find which part of the home network is at fault. Mesh Wi-Fi status lights are listed by manufacturer, each taken from that manufacturer's own support pages.

Exact symptomFault boundarySafe first testVerificationStop condition

Part of Consumer-product troubleshooting by exact model, symptom and code

Browse by platform

321 complete records in this directory

eero status light colorsEvery LED color and pattern, with the fix for red NETGEAR Orbi router and satellite lightsPower, router ring and satellite ring LEDs TP-Link Deco LED colorsYellow, blue, green and red patterns NETGEAR network models10 model families · 154 exact-scope answers TP-Link network models7 model families · 109 exact-scope answers eero network models7 model families · 112 exact-scope answers Ubiquiti network models6 model families · 50 exact-scope answers

Reviewed records

321 exact answers

Showing 100 representative records. Choose a platform or manufacturer above to see its complete set.

Diagnose the exact device problem

Home networking · roaming

Devices stay connected to a far-away mesh node

Client devices decide when to roam, so a phone may cling to a usable distant node. Excessively close mesh points, transmit power and stale client state can worsen it.

Open record Home networking · migration

Devices will not connect after replacing the router with the same Wi-Fi name

Reusing an SSID/password can reconnect many devices, but changed security, band steering, DHCP or cached network parameters can block others.

Open record Home networking · Ethernet

Ethernet is connected but there is no internet

A link light shows electrical connection, not a valid IP route. Compare cable/port, DHCP address, router LAN status and another wired device.

Open record Home networking · guest isolation

Guest Wi-Fi cannot see the printer, TV or speakers

Guest networks usually block local-device discovery by design. Internet may work while printers and casting remain isolated.

Open record Home networking · mesh placement

Mesh Wi-Fi node says its connection is weak

A mesh node needs a strong connection to the upstream node; placing it inside the dead zone repeats a weak signal. Move it halfway or use wired backhaul.

Open record Home networking · one device

Only one device connects to Wi-Fi but has no internet

If other devices work, the modem and provider are probably healthy. Check the failing device’s IP address, VPN, private DNS, captive portal and saved network profile.

Open record Home networking · stability

Router keeps restarting by itself

Repeated router reboots can follow unstable power, overheating, firmware crashes or a failing adapter. Confirm that the unit actually reboots rather than only losing internet sync.

Open record Home networking · inbound access

Router port forwarding is configured but not working

Forwarding fails when the target IP changes, the service is not listening, host firewall blocks it, double NAT/CGNAT exists, or testing occurs from inside without loopback support.

Open record Home networking · DNS

Some websites fail with DNS errors while others work

Partial DNS failure can involve a resolver, VPN/filter, IPv6 path, stale cache or the site itself. Compare hostname lookup with direct access and another resolver/network.

Open record Home networking · latency

Video calls freeze even though speed tests are fast

Video calls depend on latency, jitter, packet loss and upload headroom, not just peak download speed. Test during the call from the same location.

Open record Home networking · upload

Wi-Fi download is fast but upload is very slow

Slow upload can come from provider upstream limits, cloud backups, weak return signal, interference or router queueing. Compare wired and Wi-Fi upload with other traffic paused.

Open record Home networking · interference

Wi-Fi drops when the microwave is running

Microwave interference commonly affects 2.4 GHz near the appliance. Confirm timing, then move compatible devices to 5/6 GHz and improve placement rather than opening the appliance.

Open record Home networking · extender

Wi-Fi extender makes the connection slower

A wireless extender may halve airtime and cannot improve a weak backhaul. Placement, radio use and repeated SSIDs matter more than advertised link rate.

Open record Home networking · authentication

Wi-Fi keeps saying the correct password is wrong

A correct-looking password can fail because the device selects a similarly named network, uses stale credentials, cannot support the security mode or receives a smart-setup prompt.

Open record Home networking · internet outage

Wi-Fi says connected but no device has internet

When every device joins Wi-Fi but none reaches the internet, focus on modem/ONT, provider status, router WAN address and cabling—not individual device resets.

Open record Home networking · coverage

Wi-Fi works near the router but not upstairs

A location-specific failure is a coverage or interference problem, not an internet-account outage. Measure signal and performance at the router, stairwell and failed room before buying hardware.

Open record eero · 100 Mbps

eero 6 Ethernet link is limited to 100 Mbps or disconnects

eero 6 Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to eero 6.

Open record eero · slow Wi-Fi

eero 6 internet or Wi-Fi is slow

eero 6 internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to eero 6.

Open record eero · node offline

eero 6 mesh node or satellite is offline

eero 6 mesh node or satellite is offline: node power, parent signal, firmware, account and backhaul should be separated. Scoped to eero 6.

Open record eero · device won't connect

eero 6 will not connect one device

eero 6 will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to eero 6.

Open record eero · 100 Mbps

eero 6+ Ethernet link is limited to 100 Mbps or disconnects

eero 6+ Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to eero 6+.

Open record eero · guest network

eero 6+ guest network cannot reach devices, cast or print

eero 6+ guest network cannot reach devices, cast or print: guest isolation is usually intentional; internet and local discovery are separate permissions. Scoped to eero 6+.

Open record eero · slow Wi-Fi

eero 6+ internet or Wi-Fi is slow

eero 6+ internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to eero 6+.

Open record eero · node offline

eero 6+ mesh node or satellite is offline

eero 6+ mesh node or satellite is offline: node power, parent signal, firmware, account and backhaul should be separated. Scoped to eero 6+.

Open record eero · parental controls

eero 6+ parental controls or schedules are not working

eero 6+ parental controls or schedules are not working: target identity, randomized MAC, time zone, DNS/VPN bypass and overlapping profiles should be separated. Scoped to eero 6+.

Open record eero · double NAT

eero 6+ shows double NAT or strict NAT

eero 6+ shows double NAT or strict NAT: provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries. Scoped to eero 6+.

Open record eero · Wi-Fi drops

eero 6+ Wi-Fi keeps disconnecting

eero 6+ Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to eero 6+.

Open record eero · setup

eero 6+ will not complete setup

eero 6+ will not complete setup: modem/ONT provisioning, WAN type, app/account and cabling should be proved before resets. Scoped to eero 6+.

Open record eero · device won't connect

eero 6+ will not connect one device

eero 6+ will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to eero 6+.

Open record eero · 100 Mbps

eero Beacon Ethernet link is limited to 100 Mbps or disconnects

eero Beacon Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to eero Beacon D010001.

Open record eero · guest network

eero Beacon guest network cannot reach devices, cast or print

eero Beacon guest network cannot reach devices, cast or print: guest isolation is usually intentional; internet and local discovery are separate permissions. Scoped to eero Beacon D010001.

Open record eero · slow Wi-Fi

eero Beacon internet or Wi-Fi is slow

eero Beacon internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to eero Beacon D010001.

Open record eero · node offline

eero Beacon mesh node or satellite is offline

eero Beacon mesh node or satellite is offline: node power, parent signal, firmware, account and backhaul should be separated. Scoped to eero Beacon D010001.

Open record eero · parental controls

eero Beacon parental controls or schedules are not working

eero Beacon parental controls or schedules are not working: target identity, randomized MAC, time zone, DNS/VPN bypass and overlapping profiles should be separated. Scoped to eero Beacon D010001.

Open record eero · port forwarding

eero Beacon port forwarding is not working

eero Beacon port forwarding is not working: local service, firewall, reserved IP, double NAT, CGNAT and provider blocks should be proved in order. Scoped to eero Beacon D010001.

Open record eero · double NAT

eero Beacon shows double NAT or strict NAT

eero Beacon shows double NAT or strict NAT: provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries. Scoped to eero Beacon D010001.

Open record eero · Wi-Fi drops

eero Beacon Wi-Fi keeps disconnecting

eero Beacon Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to eero Beacon D010001.

Open record eero · setup

eero Beacon will not complete setup

eero Beacon will not complete setup: modem/ONT provisioning, WAN type, app/account and cabling should be proved before resets. Scoped to eero Beacon D010001.

Open record eero · device won't connect

eero Beacon will not connect one device

eero Beacon will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to eero Beacon D010001.

Open record eero · DNS

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) cannot open websites because DNS fails

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) cannot open websites because DNS fails: resolver, filter, VPN and cache should be separated from a site or provider outage. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · 100 Mbps

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) Ethernet link is limited to 100 Mbps or disconnects

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · firmware

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) firmware update will not install

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) firmware update will not install: exact model/hardware revision, stable power, storage and signed firmware are required. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · guest network

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) guest network cannot reach devices, cast or print

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) guest network cannot reach devices, cast or print: guest isolation is usually intentional; internet and local discovery are separate permissions. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · dead zones

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) has weak signal or dead zones

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) has weak signal or dead zones: building loss, access-point placement, band and mesh backhaul should be measured at the node location. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · no internet

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) has Wi-Fi but no internet

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) has Wi-Fi but no internet: provider modem/ONT, router WAN address, DNS and one client should be separated. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · slow Wi-Fi

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) internet or Wi-Fi is slow

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · node offline

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) mesh node or satellite is offline

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) mesh node or satellite is offline: node power, parent signal, firmware, account and backhaul should be separated. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · parental controls

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) parental controls or schedules are not working

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) parental controls or schedules are not working: target identity, randomized MAC, time zone, DNS/VPN bypass and overlapping profiles should be separated. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · port forwarding

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) port forwarding is not working

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) port forwarding is not working: local service, firewall, reserved IP, double NAT, CGNAT and provider blocks should be proved in order. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · restarts

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) restarts, freezes or overheats

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) restarts, freezes or overheats: power supply, ventilation, load, firmware and hardware should be separated. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · double NAT

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) shows double NAT or strict NAT

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) shows double NAT or strict NAT: provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · VPN

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) VPN client or server will not connect

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) VPN client or server will not connect: provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · Wi-Fi drops

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) Wi-Fi keeps disconnecting

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · setup

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) will not complete setup

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) will not complete setup: modem/ONT provisioning, WAN type, app/account and cabling should be proved before resets. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · device won't connect

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) will not connect one device

eero mesh wifi (eero Max 7, Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7) will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to eero Max 7, with the Pro 6E, Pro 6, 6+, 6, Pro, Beacon and Outdoor 7 in the model notes.

Open record eero · 100 Mbps

eero Outdoor 7 Ethernet link is limited to 100 Mbps or disconnects

eero Outdoor 7 Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to eero Outdoor 7.

Open record eero · slow Wi-Fi

eero Outdoor 7 internet or Wi-Fi is slow

eero Outdoor 7 internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to eero Outdoor 7.

Open record eero · node offline

eero Outdoor 7 mesh node or satellite is offline

eero Outdoor 7 mesh node or satellite is offline: node power, parent signal, firmware, account and backhaul should be separated. Scoped to eero Outdoor 7.

Open record eero · double NAT

eero Outdoor 7 shows double NAT or strict NAT

eero Outdoor 7 shows double NAT or strict NAT: provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries. Scoped to eero Outdoor 7.

Open record eero · Wi-Fi drops

eero Outdoor 7 Wi-Fi keeps disconnecting

eero Outdoor 7 Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to eero Outdoor 7.

Open record eero · 100 Mbps

eero Pro (2nd generation) Ethernet link is limited to 100 Mbps or disconnects

eero Pro (2nd generation) Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to eero Pro B010001.

Open record eero · slow Wi-Fi

eero Pro (2nd generation) internet or Wi-Fi is slow

eero Pro (2nd generation) internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to eero Pro B010001.

Open record eero · device won't connect

eero Pro (2nd generation) will not connect one device

eero Pro (2nd generation) will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to eero Pro B010001.

Open record eero · 100 Mbps

eero Pro 6 Ethernet link is limited to 100 Mbps or disconnects

eero Pro 6 Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to eero Pro 6.

Open record eero · device won't connect

eero Pro 6 will not connect one device

eero Pro 6 will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to eero Pro 6.

Open record NETGEAR · slow Wi-Fi

NETGEAR Nighthawk CAX80 cable modem router internet or Wi-Fi is slow

NETGEAR Nighthawk CAX80 cable modem router internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to CAX80.

Open record NETGEAR · double NAT

NETGEAR Nighthawk CAX80 cable modem router shows double NAT or strict NAT

NETGEAR Nighthawk CAX80 cable modem router shows double NAT or strict NAT: provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries. Scoped to CAX80.

Open record NETGEAR · no internet

NETGEAR Nighthawk RAX120 router has Wi-Fi but no internet

NETGEAR Nighthawk RAX120 router has Wi-Fi but no internet: provider modem/ONT, router WAN address, DNS and one client should be separated. Scoped to RAX120.

Open record NETGEAR · slow Wi-Fi

NETGEAR Nighthawk RAX120 router internet or Wi-Fi is slow

NETGEAR Nighthawk RAX120 router internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to RAX120.

Open record NETGEAR · restarts

NETGEAR Nighthawk RAX120 router restarts, freezes or overheats

NETGEAR Nighthawk RAX120 router restarts, freezes or overheats: power supply, ventilation, load, firmware and hardware should be separated. Scoped to RAX120.

Open record NETGEAR · Wi-Fi drops

NETGEAR Nighthawk RAX120 router Wi-Fi keeps disconnecting

NETGEAR Nighthawk RAX120 router Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to RAX120.

Open record NETGEAR · guest network

NETGEAR Nighthawk RAX50 router guest network cannot reach devices, cast or print

NETGEAR Nighthawk RAX50 router guest network cannot reach devices, cast or print: guest isolation is usually intentional; internet and local discovery are separate permissions. Scoped to RAX50.

Open record NETGEAR · parental controls

NETGEAR Nighthawk RAX50 router parental controls or schedules are not working

NETGEAR Nighthawk RAX50 router parental controls or schedules are not working: target identity, randomized MAC, time zone, DNS/VPN bypass and overlapping profiles should be separated. Scoped to RAX50.

Open record NETGEAR · VPN

NETGEAR Nighthawk RAX50 router VPN client or server will not connect

NETGEAR Nighthawk RAX50 router VPN client or server will not connect: provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated. Scoped to RAX50.

Open record NETGEAR · DNS

NETGEAR Nighthawk RAXE500 router cannot open websites because DNS fails

NETGEAR Nighthawk RAXE500 router cannot open websites because DNS fails: resolver, filter, VPN and cache should be separated from a site or provider outage. Scoped to RAXE500.

Open record NETGEAR · firmware

NETGEAR Nighthawk RAXE500 router firmware update will not install

NETGEAR Nighthawk RAXE500 router firmware update will not install: exact model/hardware revision, stable power, storage and signed firmware are required. Scoped to RAXE500.

Open record NETGEAR · VPN

NETGEAR Nighthawk RAXE500 router VPN client or server will not connect

NETGEAR Nighthawk RAXE500 router VPN client or server will not connect: provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated. Scoped to RAXE500.

Open record NETGEAR · DNS

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) cannot open websites because DNS fails

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) cannot open websites because DNS fails: resolver, filter, VPN and cache should be separated from a site or provider outage. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · 100 Mbps

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) Ethernet link is limited to 100 Mbps or disconnects

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · firmware

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) firmware update will not install

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) firmware update will not install: exact model/hardware revision, stable power, storage and signed firmware are required. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · guest network

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) guest network cannot reach devices, cast or print

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) guest network cannot reach devices, cast or print: guest isolation is usually intentional; internet and local discovery are separate permissions. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · no internet

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) has Wi-Fi but no internet

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) has Wi-Fi but no internet: provider modem/ONT, router WAN address, DNS and one client should be separated. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · slow Wi-Fi

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) internet or Wi-Fi is slow

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · restarts

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) restarts, freezes or overheats

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) restarts, freezes or overheats: power supply, ventilation, load, firmware and hardware should be separated. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · double NAT

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) shows double NAT or strict NAT

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) shows double NAT or strict NAT: provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · VPN

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) VPN client or server will not connect

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) VPN client or server will not connect: provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · Wi-Fi drops

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) Wi-Fi keeps disconnecting

NETGEAR Nighthawk routers (Nighthawk RS700S, RS300, RAXE500, RAX120, RAX50 and CAX80) Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to Nighthawk RS700S, with the RS300, RAXE500, RAX120, RAX50 and CAX80 in the model notes.

Open record NETGEAR · no internet

NETGEAR Nighthawk RS300 Wi-Fi 7 router has Wi-Fi but no internet

NETGEAR Nighthawk RS300 Wi-Fi 7 router has Wi-Fi but no internet: provider modem/ONT, router WAN address, DNS and one client should be separated. Scoped to RS300.

Open record NETGEAR · restarts

NETGEAR Nighthawk RS300 Wi-Fi 7 router restarts, freezes or overheats

NETGEAR Nighthawk RS300 Wi-Fi 7 router restarts, freezes or overheats: power supply, ventilation, load, firmware and hardware should be separated. Scoped to RS300.

Open record NETGEAR · VPN

NETGEAR Nighthawk RS300 Wi-Fi 7 router VPN client or server will not connect

NETGEAR Nighthawk RS300 Wi-Fi 7 router VPN client or server will not connect: provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated. Scoped to RS300.

Open record NETGEAR · Wi-Fi drops

NETGEAR Nighthawk RS300 Wi-Fi 7 router Wi-Fi keeps disconnecting

NETGEAR Nighthawk RS300 Wi-Fi 7 router Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to RS300.

Open record NETGEAR · dead zones

NETGEAR Orbi 750 Series mesh has weak signal or dead zones

NETGEAR Orbi 750 Series mesh has weak signal or dead zones: building loss, access-point placement, band and mesh backhaul should be measured at the node location. Scoped to RBK752/RBS750.

Open record NETGEAR · port forwarding

NETGEAR Orbi 750 Series mesh port forwarding is not working

NETGEAR Orbi 750 Series mesh port forwarding is not working: local service, firewall, reserved IP, double NAT, CGNAT and provider blocks should be proved in order. Scoped to RBK752/RBS750.

Open record NETGEAR · VPN

NETGEAR Orbi 750 Series mesh VPN client or server will not connect

NETGEAR Orbi 750 Series mesh VPN client or server will not connect: provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated. Scoped to RBK752/RBS750.

Open record NETGEAR · DNS

NETGEAR Orbi 850 Series mesh cannot open websites because DNS fails

NETGEAR Orbi 850 Series mesh cannot open websites because DNS fails: resolver, filter, VPN and cache should be separated from a site or provider outage. Scoped to RBK852/RBS850.

Open record NETGEAR · 100 Mbps

NETGEAR Orbi 850 Series mesh Ethernet link is limited to 100 Mbps or disconnects

NETGEAR Orbi 850 Series mesh Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to RBK852/RBS850.

Open record NETGEAR · guest network

NETGEAR Orbi 850 Series mesh guest network cannot reach devices, cast or print

NETGEAR Orbi 850 Series mesh guest network cannot reach devices, cast or print: guest isolation is usually intentional; internet and local discovery are separate permissions. Scoped to RBK852/RBS850.

Open record NETGEAR · dead zones

NETGEAR Orbi 850 Series mesh has weak signal or dead zones

NETGEAR Orbi 850 Series mesh has weak signal or dead zones: building loss, access-point placement, band and mesh backhaul should be measured at the node location. Scoped to RBK852/RBS850.

Open record NETGEAR · no internet

NETGEAR Orbi 850 Series mesh has Wi-Fi but no internet

NETGEAR Orbi 850 Series mesh has Wi-Fi but no internet: provider modem/ONT, router WAN address, DNS and one client should be separated. Scoped to RBK852/RBS850.

Open record NETGEAR · slow Wi-Fi

NETGEAR Orbi 850 Series mesh internet or Wi-Fi is slow

NETGEAR Orbi 850 Series mesh internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to RBK852/RBS850.

Open record

Home network problems: router, Wi-Fi and device faults

A slow or dropping connection is rarely one thing, so the first step is to find where the fault sits. Test one device on Wi-Fi and the same device on a cable: if the cable is fast, the problem is the Wi-Fi; if both are slow, it is the router, the modem or the provider. Devices that connect but have no internet usually have an address, DNS or router problem, while a device that cannot see the network at all may be on the wrong band or too far from a mesh node. Wi-Fi that drops when the microwave runs is interference on the 2.4 GHz band, and video calls that freeze while speed tests look fine often come down to upload speed, congestion or a weak link between nodes.

Restart the modem and router in order (modem first), keep the router in the open and off the floor, and update its firmware. Mesh nodes work best when each one sees the next with a strong signal. Port forwarding fails mostly because of a double NAT or because the device does not keep a fixed address. Status lights on mesh systems differ by brand and are explained on the brand pages.

Why is my Wi-Fi fast on a speed test but video calls freeze?

Calls depend on upload speed and a steady connection, not just download speed. Test upload, check how many devices are in use and move closer to the router or node.

Why is a Wi-Fi extender making my connection slower?

An extender repeats the signal on the same channel, which can halve the speed. Place it where it still gets a strong signal from the router, or use a wired mesh node.