Manufacturer and model directory
NETGEAR network model troubleshooting
Choose the complete NETGEAR model family before opening a fix. Model patterns are shown on every page, and unsupported code meanings are not copied between platforms.
Browse by platform
154 complete records in this directoryNETGEAR Nighthawk CAX80 cable modem router cannot open websites because DNS fails
NETGEAR Nighthawk CAX80 cable modem router cannot open websites because DNS fails: resolver, filter, VPN and cache should be separated from a site or provider outage. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · 100 MbpsNETGEAR Nighthawk CAX80 cable modem router Ethernet link is limited to 100 Mbps or disconnects
NETGEAR Nighthawk CAX80 cable modem router Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · firmwareNETGEAR Nighthawk CAX80 cable modem router firmware update will not install
NETGEAR Nighthawk CAX80 cable modem router firmware update will not install: exact model/hardware revision, stable power, storage and signed firmware are required. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · guest networkNETGEAR Nighthawk CAX80 cable modem router guest network cannot reach devices, cast or print
NETGEAR Nighthawk CAX80 cable modem router guest network cannot reach devices, cast or print: guest isolation is usually intentional; internet and local discovery are separate permissions. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · dead zonesNETGEAR Nighthawk CAX80 cable modem router has weak signal or dead zones
NETGEAR Nighthawk CAX80 cable modem router has weak signal or dead zones: building loss, access-point placement, band and mesh backhaul should be measured at the node location. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · no internetNETGEAR Nighthawk CAX80 cable modem router has Wi-Fi but no internet
NETGEAR Nighthawk CAX80 cable modem router has Wi-Fi but no internet: provider modem/ONT, router WAN address, DNS and one client should be separated. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · slow Wi-FiNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · parental controlsNETGEAR Nighthawk CAX80 cable modem router parental controls or schedules are not working
NETGEAR Nighthawk CAX80 cable modem 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 CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · port forwardingNETGEAR Nighthawk CAX80 cable modem router port forwarding is not working
NETGEAR Nighthawk CAX80 cable modem router port forwarding is not working: local service, firewall, reserved IP, double NAT, CGNAT and provider blocks should be proved in order. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · restartsNETGEAR Nighthawk CAX80 cable modem router restarts, freezes or overheats
NETGEAR Nighthawk CAX80 cable modem router restarts, freezes or overheats: power supply, ventilation, load, firmware and hardware should be separated. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · double NATNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · VPNNETGEAR Nighthawk CAX80 cable modem router VPN client or server will not connect
NETGEAR Nighthawk CAX80 cable modem router VPN client or server will not connect: provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · Wi-Fi dropsNETGEAR Nighthawk CAX80 cable modem router Wi-Fi keeps disconnecting
NETGEAR Nighthawk CAX80 cable modem router Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · setupNETGEAR Nighthawk CAX80 cable modem router will not complete setup
NETGEAR Nighthawk CAX80 cable modem router will not complete setup: modem/ONT provisioning, WAN type, app/account and cabling should be proved before resets. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · device won't connectNETGEAR Nighthawk CAX80 cable modem router will not connect one device
NETGEAR Nighthawk CAX80 cable modem router will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to CAX80, with the model boundary and safe stop points made explicit.
Open record NETGEAR · DNSNETGEAR Nighthawk RAX120 router cannot open websites because DNS fails
NETGEAR Nighthawk RAX120 router cannot open websites because DNS fails: resolver, filter, VPN and cache should be separated from a site or provider outage. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · 100 MbpsNETGEAR Nighthawk RAX120 router Ethernet link is limited to 100 Mbps or disconnects
NETGEAR Nighthawk RAX120 router Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · firmwareNETGEAR Nighthawk RAX120 router firmware update will not install
NETGEAR Nighthawk RAX120 router firmware update will not install: exact model/hardware revision, stable power, storage and signed firmware are required. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · guest networkNETGEAR Nighthawk RAX120 router guest network cannot reach devices, cast or print
NETGEAR Nighthawk RAX120 router guest network cannot reach devices, cast or print: guest isolation is usually intentional; internet and local discovery are separate permissions. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · dead zonesNETGEAR Nighthawk RAX120 router has weak signal or dead zones
NETGEAR Nighthawk RAX120 router has weak signal or dead zones: building loss, access-point placement, band and mesh backhaul should be measured at the node location. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · no internetNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · slow Wi-FiNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · parental controlsNETGEAR Nighthawk RAX120 router parental controls or schedules are not working
NETGEAR Nighthawk RAX120 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 RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · port forwardingNETGEAR Nighthawk RAX120 router port forwarding is not working
NETGEAR Nighthawk RAX120 router port forwarding is not working: local service, firewall, reserved IP, double NAT, CGNAT and provider blocks should be proved in order. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · restartsNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · double NATNETGEAR Nighthawk RAX120 router shows double NAT or strict NAT
NETGEAR Nighthawk RAX120 router shows double NAT or strict NAT: provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · VPNNETGEAR Nighthawk RAX120 router VPN client or server will not connect
NETGEAR Nighthawk RAX120 router VPN client or server will not connect: provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · Wi-Fi dropsNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · setupNETGEAR Nighthawk RAX120 router will not complete setup
NETGEAR Nighthawk RAX120 router will not complete setup: modem/ONT provisioning, WAN type, app/account and cabling should be proved before resets. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · device won't connectNETGEAR Nighthawk RAX120 router will not connect one device
NETGEAR Nighthawk RAX120 router will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to RAX120, with the model boundary and safe stop points made explicit.
Open record NETGEAR · DNSNETGEAR Nighthawk RAX50 router cannot open websites because DNS fails
NETGEAR Nighthawk RAX50 router cannot open websites because DNS fails: resolver, filter, VPN and cache should be separated from a site or provider outage. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · 100 MbpsNETGEAR Nighthawk RAX50 router Ethernet link is limited to 100 Mbps or disconnects
NETGEAR Nighthawk RAX50 router Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · firmwareNETGEAR Nighthawk RAX50 router firmware update will not install
NETGEAR Nighthawk RAX50 router firmware update will not install: exact model/hardware revision, stable power, storage and signed firmware are required. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · guest networkNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · dead zonesNETGEAR Nighthawk RAX50 router has weak signal or dead zones
NETGEAR Nighthawk RAX50 router has weak signal or dead zones: building loss, access-point placement, band and mesh backhaul should be measured at the node location. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · no internetNETGEAR Nighthawk RAX50 router has Wi-Fi but no internet
NETGEAR Nighthawk RAX50 router has Wi-Fi but no internet: provider modem/ONT, router WAN address, DNS and one client should be separated. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · slow Wi-FiNETGEAR Nighthawk RAX50 router internet or Wi-Fi is slow
NETGEAR Nighthawk RAX50 router internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · parental controlsNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · port forwardingNETGEAR Nighthawk RAX50 router port forwarding is not working
NETGEAR Nighthawk RAX50 router port forwarding is not working: local service, firewall, reserved IP, double NAT, CGNAT and provider blocks should be proved in order. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · restartsNETGEAR Nighthawk RAX50 router restarts, freezes or overheats
NETGEAR Nighthawk RAX50 router restarts, freezes or overheats: power supply, ventilation, load, firmware and hardware should be separated. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · double NATNETGEAR Nighthawk RAX50 router shows double NAT or strict NAT
NETGEAR Nighthawk RAX50 router shows double NAT or strict NAT: provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · VPNNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · Wi-Fi dropsNETGEAR Nighthawk RAX50 router Wi-Fi keeps disconnecting
NETGEAR Nighthawk RAX50 router Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · setupNETGEAR Nighthawk RAX50 router will not complete setup
NETGEAR Nighthawk RAX50 router will not complete setup: modem/ONT provisioning, WAN type, app/account and cabling should be proved before resets. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · device won't connectNETGEAR Nighthawk RAX50 router will not connect one device
NETGEAR Nighthawk RAX50 router will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to RAX50, with the model boundary and safe stop points made explicit.
Open record NETGEAR · DNSNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · 100 MbpsNETGEAR Nighthawk RAXE500 router Ethernet link is limited to 100 Mbps or disconnects
NETGEAR Nighthawk RAXE500 router Ethernet link is limited to 100 Mbps or disconnects: every cable pair, wall jack, switch and port must negotiate the intended speed. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · firmwareNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · guest networkNETGEAR Nighthawk RAXE500 router guest network cannot reach devices, cast or print
NETGEAR Nighthawk RAXE500 router guest network cannot reach devices, cast or print: guest isolation is usually intentional; internet and local discovery are separate permissions. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · dead zonesNETGEAR Nighthawk RAXE500 router has weak signal or dead zones
NETGEAR Nighthawk RAXE500 router has weak signal or dead zones: building loss, access-point placement, band and mesh backhaul should be measured at the node location. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · no internetNETGEAR Nighthawk RAXE500 router has Wi-Fi but no internet
NETGEAR Nighthawk RAXE500 router has Wi-Fi but no internet: provider modem/ONT, router WAN address, DNS and one client should be separated. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · slow Wi-FiNETGEAR Nighthawk RAXE500 router internet or Wi-Fi is slow
NETGEAR Nighthawk RAXE500 router internet or Wi-Fi is slow: provider rate, wired router throughput, radio link and one service should be measured separately. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · parental controlsNETGEAR Nighthawk RAXE500 router parental controls or schedules are not working
NETGEAR Nighthawk RAXE500 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 RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · port forwardingNETGEAR Nighthawk RAXE500 router port forwarding is not working
NETGEAR Nighthawk RAXE500 router port forwarding is not working: local service, firewall, reserved IP, double NAT, CGNAT and provider blocks should be proved in order. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · restartsNETGEAR Nighthawk RAXE500 router restarts, freezes or overheats
NETGEAR Nighthawk RAXE500 router restarts, freezes or overheats: power supply, ventilation, load, firmware and hardware should be separated. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · double NATNETGEAR Nighthawk RAXE500 router shows double NAT or strict NAT
NETGEAR Nighthawk RAXE500 router shows double NAT or strict NAT: provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · VPNNETGEAR 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, with the model boundary and safe stop points made explicit.
Open record NETGEAR · Wi-Fi dropsNETGEAR Nighthawk RAXE500 router Wi-Fi keeps disconnecting
NETGEAR Nighthawk RAXE500 router Wi-Fi keeps disconnecting: client, band, channel/interference, coverage, firmware and node backhaul should be isolated. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · setupNETGEAR Nighthawk RAXE500 router will not complete setup
NETGEAR Nighthawk RAXE500 router will not complete setup: modem/ONT provisioning, WAN type, app/account and cabling should be proved before resets. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open record NETGEAR · device won't connectNETGEAR Nighthawk RAXE500 router will not connect one device
NETGEAR Nighthawk RAXE500 router will not connect one device: one-client capability, security, band, DHCP, randomized address and access controls should be isolated. Scoped to RAXE500, with the model boundary and safe stop points made explicit.
Open recordProduct lines
How the 10 NETGEAR families here actually differ
These are not marketing tiers. Each group below behaves differently under diagnosis, which is why a procedure written for one does not transfer to another, and it is the first thing to settle before following any fix.
NETGEAR router/mesh; modem integration, Wi-Fi generation, Armor, guest and Ethernet ports vary.
- Nighthawk RS700S Wi-Fi 7 router RS700S
- Nighthawk RS300 Wi-Fi 7 router RS300
- Nighthawk RAXE500 router RAXE500
- Nighthawk RAX120 router RAX120
- Nighthawk RAX50 router RAX50
- Orbi 970 Series mesh RBE971/RBE970
- Orbi 960 Series mesh RBKE963/RBSE960
- Orbi 850 Series mesh RBK852/RBS850
- Orbi 750 Series mesh RBK752/RBS750
Cable-modem router; provider provisioning and DOCSIS signal precede router-only troubleshooting.
Find your model
Model numbers covered, and where each one's answers are
Match the identifier on your appliance or device label to a row below. NETGEAR answers here are scoped to these patterns, and a model outside them is deliberately not claimed rather than covered by a page that guesses.
| Family | Model numbers | Published specs |
|---|---|---|
| Nighthawk RS700S Wi-Fi 7 router | RS700S | 3 researched |
| Nighthawk RS300 Wi-Fi 7 router | RS300 | 3 researched |
| Nighthawk RAXE500 router | RAXE500 | 3 researched |
| Nighthawk RAX120 router | RAX120 | 3 researched |
| Nighthawk RAX50 router | RAX50 | 3 researched |
| Orbi 970 Series mesh | RBE971/RBE970 | 3 researched |
| Orbi 960 Series mesh | RBKE963/RBSE960 | 3 researched |
| Orbi 850 Series mesh | RBK852/RBS850 | 3 researched |
| Orbi 750 Series mesh | RBK752/RBS750 | 3 researched |
| Nighthawk CAX80 cable modem router | CAX80 | 3 researched |
Structured depth, not empty permutations
Every published record carries a direct answer, scope, ordered fixes, risk notes and sources.
Device and manufacturer hubs share a consistent record system, but each answer carries the relevant controls, fault boundaries, consequences and official support entry point for that platform.
See the publication gate