NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
hornywell
Nov 03, 2021Tutor
Error after R7960P Firmware Upgraded to 1.4.2.84_1.3.42
The post is about R7900P X6S AC3600. After upgrading the firmware to 1.4.2.84_1.3.42, I constantly experienced this ‘Hmm, we can’t reach this page’ error in Microsoft Edge, or similar messages in...
NetOp
Mar 22, 2022Tutor
I can confirm 100% that 1.4.2.84_1.3.42 is still BROKEN firmware! Ping your gateway and you will find >1ms latency even on a wired connection. Run DNS through the router and it will not load web sites on the first try with a timeout. If I refresh a website I get the DNS to resolve. Trace route also fails to resolve on the first attempt! The latency to the gateway on a directly connected wired connection less than 10 feet away from the router is showing Netgear Engineers are not properly testing firmware releases for routers. IS THIS PLANNED OBSOLESCENCE? This seems like WILLFUL NEGLIGENCE on Netgear's part and needs to be fixed ASAP. Even the damn wifi 10 feet away with only 2 PCs connected has triple digit ms latency at times with this firmware! No one is using the network at all right now. Netgear you must fix this!
C:\WINDOWS\system32>tracert cert.org
Unable to resolve target system name cert.org.
C:\WINDOWS\system32>nslookup cert.org
Server: UnKnown
Address: 192.168.10.1 <<< BROKEN ROUTER FIRMWARE 1.4.2.84_1.3.42 >>>
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
<<< DIRECTLY WIRED CONNECTION LATENCY >>>
C:\WINDOWS\system32>ping 192.168.10.1 -t
Pinging 192.168.10.1 with 32 bytes of data
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time=7ms TTL=64
Reply from 192.168.10.1: bytes=32 time=5ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time=15ms TTL=64
- FURRYe38Mar 22, 2022Guru
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Has a factory reset and setup from scratch been performed since last FW update? A complete pull of the power adapters for a period of time after the factory reset then walk thru the setup wizard and setup from scratch.
I would power OFF the ISP modem for 1 minute. Factory reset the Orbi router and power it off. Power ON the ISP modem and let it sync. Then power ON the Orbi router and walk thru the setup wizard again using a wired PC and a web browser.Otherwise you'll need to roll back to prior working version of FW.