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...
Lee-net
Nov 06, 2021Tutor
After 2 weeks of extremely frustrated people, downgraded from 1.4.2.84_1.3.42to V1.4.1.68_1.3.28 based on others comments. While on the newest version and running Armor, we would get 'This site can't be reached' on 2/3rds of domains including community.netgear.com. Multiple refreshes later would usually allow access to the site, but unfortuantely, the 1.4.2.84 version is causing denial of service.
In my case, the windows (chrome) error is DNS_PROBE_FINISHED_BAD_CONFIG
Netgear... the other workaround that you could include as an option in your software is to allow us end users to configure the primary and secondary DNS servers in the DHCP configuration on your products. Even though most people are using your router for DHCP, providing the option to configure custom DNS servers would allow us to bypass the faulty DNS config in the 1.4.2.84 release or potentially future releases.
Please provide updates to resolve the DNS service issues! Running older firmware is scary in terms of security compliance.
DickScheel
Nov 09, 2021Aspirant
Downgrading back to version 1.4.1.68_1.3.28 fixed the problem for me too. Unfortunately, that means whatever security vulnerability they fix in 1.4.2.84 is not patched. Hopefully Netgear will find & fix the 1.4.2.84 bug, and then issue a new firmware version with the bug fixed as well as the security issue.
- FURRYe38Nov 09, 2021Guru - Experienced User
Please contact NG support and let them know what your seeing.
DickScheel wrote:
Downgrading back to version 1.4.1.68_1.3.28 fixed the problem for me too. Unfortunately, that means whatever security vulnerability they fix in 1.4.2.84 is not patched. Hopefully Netgear will find & fix the 1.4.2.84 bug, and then issue a new firmware version with the bug fixed as well as the security issue.
- DickScheelNov 11, 2021Aspirant
I can't find a way to report this to Netgear support. My router is out of the support period, so the only support I have been able to find is the Community section. Is there some way to report this to Netgear that I haven't found?
FURRYe38 wrote:Please contact NG support and let them know what your seeing.
DickScheel wrote:Downgrading back to version 1.4.1.68_1.3.28 fixed the problem for me too. Unfortunately, that means whatever security vulnerability they fix in 1.4.2.84 is not patched. Hopefully Netgear will find & fix the 1.4.2.84 bug, and then issue a new firmware version with the bug fixed as well as the security issue.
- FURRYe38Nov 11, 2021Guru - Experienced User
You can send a forum moderator a PM:
DickScheel wrote:
I can't find a way to report this to Netgear support. My router is out of the support period, so the only support I have been able to find is the Community section. Is there some way to report this to Netgear that I haven't found?
FURRYe38 wrote:
Please contact NG support and let them know what your seeing.
DickScheel wrote:
Downgrading back to version 1.4.1.68_1.3.28 fixed the problem for me too. Unfortunately, that means whatever security vulnerability they fix in 1.4.2.84 is not patched. Hopefully Netgear will find & fix the 1.4.2.84 bug, and then issue a new firmware version with the bug fixed as well as the security issue.