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 Google Chrome / Firefox. Initially, I was not sure if there is any direct relation due to the router firmware update. But if I tether my laptop to my T-Mobile hot spot or have it hardwired (Ethernet) directly to the modem, such error messages do not appear.
The problem happens almost all in cases where the pages are being forwarded to different sites.
I downgraded the firmware to 1.4.1.68_1.3.28, which was a stable release, such error messages go away.
It seems version 1.4.2.84_1.3.42 is a troublesome release.
52 Replies
- plemansGuru - Experienced User
You're right. It is trouble some.
we've see a lot of the newest firmware releases across multiple product line have DNS issues.
Some have been able to enable IPv6 and it works.
Others have been able to set individual DNS addresses in their devices and it works.
others have had to downgrade.thanks for posting as the more people who do, the more likely the mod's/engineers see the issue.
YES, I did all of these before downgrading the firmware. I was even thinking the possibility that uprading to 1.4.2.84_1.3.42 somehow bricked my R7960P router. SO I started looking for a cheap one on eBay, and I actually bidded one at $25.00:)
These error messages didn't showup when I was tethering my laptop to my TMo phone on an out of town trip last week, so I had to think it's either the ISP modem, or the router.
- FURRYe38Guru - Experienced User
Can you downgrade back to v68?
- FURRYe38Guru - Experienced User
Has a factory reset and setup from scratch been performed since last update?
Be sure to clear out all browser caches before entering the page.
Something I haven't seen on mine since updating.
hornywell wrote:
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 Google Chrome / Firefox. Initially, I was not sure if there is any direct relation due to the router firmware update. But if I tether my laptop to my T-Mobile hot spot or have it hardwired (Ethernet) directly to the modem, such error messages do not appear.
The problem happens almost all in cases where the pages are being forwarded to different sites.
I downgraded the firmware to 1.4.1.68_1.3.28, which was a stable release, such error messages go away.
It seems version 1.4.2.84_1.3.42 is a troublesome release.
- sidneymouraInitiate
The same problem occurred with my R8000P router before downgrading it to 1.4.1.68. Thanks for your report!
- Lee-netTutor
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.
- FURRYe38Guru - Experienced User
THanks for letting us know.
Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/24231/How-do-I-back-up-the-router-configuration-settings-on-my-Nighthawk-router
Enjoy. - DickScheelAspirant
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.
- FURRYe38Guru - 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.
- FURRYe38Guru - Experienced User
Putting this here for user experiences with v.84 FW.
Put my R7960P on yesterday and its' been working well.
CAX80 (Modem Mode)>R7960P(Router Mode). Armor, Circle(Parental Controls) and QoS not enabled. Smart Connect, Traffic Meter and DST is enabled.
Manual Wi-Fi channels 11, 48 and 161
Gotta say Wifi on 5Ghz is pretty good:
No DNS issues seen as of yet. I'm monitoring for this:
Just saw one DNS Probe message while selecting a tab here in the NG forums. Though it doesn't seem to happen often, just noticed this DNS Probe message when I refreshed the NG forum web page. It flashed up on the browser quickly, then the browser continue to load the page correctly on it's own.
I'll pass this on to NG for review.
- ZDaultonInitiate
I had this issue with Nighthawk R8000P firmware 1.4.2.84_1.3.42. Downgrading to the previous build fixed this.
When can we expect a new firmware update that resolves this issue?
I changed my DNS targets within the admin panel but ALL possible DNS servers still produced the same issue. Reverting to the old firmware fixed it.
- FURRYe38Guru - Experienced User
NG doesn't make it known when new FW is forth coming. Contact NG support to let them know what your having issues with.
Good Luck. - SSDCarroll3Aspirant
Two weeks ago installed firmware update V1.4.2.84_1.3.42 and I have had nothing but trouble with my internet connection since. I am receiving the same messages with message saying "This site can't be reached" and to check if there is a typo in the address. These are sites I go to many times a day and have never had an issue until now.
I have have my internet company replace the modem and I have no problems using my computer direct to the modem, nor do I have these issues when using other people's networks. The issue is definitely my router.
My question is, how do I uninstall the most recent firmware update and go back to an earlier version? I have done a factory reset on my router and it brings me to the newest firmware update that started this issue.
Thanks in advance
- c627627Tutor
Find firmware R7960P-V1.4.1.68_1.3.28 which is not buggy, downgrading to this version resolves this horrible bug.
At this point we have to consider that Netgear knows about this bug and has left it in place, to do damage every day, wasting people's time. How frustrating must it be for so many people who trusted Netgear...
To what end is Netgear doing this and why?
- c627627Tutor
R7960P-V1.4.2.84_1.3.42 is ABSOLUTELY buggy - do not upgrade to this version! You will not be able to load web pages...
R7960P-V1.4.1.68_1.3.28 is not buggy, downgrading to this version resolves this horrible bug.
Are these threads read by Netgear Engineers? How do we report a bug outside of our warranty period?
- michaelkenwardGuru - Experienced User
c627627 wrote:
Are these threads read by Netgear Engineers? How do we report a bug outside of our warranty period?
See above.
- c627627Tutor
This is a MAJOR bug of such magnitude that it warrants pulling this update file immediately.
All forum posts should techinically be read by a moderator, will the moderator reading this post please alert Netgear about this huge problem.
- FURRYe38Guru - Experienced User
You can certainly contact a forum moderator directly via PM.
c627627 wrote:
This is a MAJOR bug of such magnitude that it warrants pulling this update file immediately.
All forum posts should techinically be read by a moderator, will the moderator reading this post please alert Netgear about this huge problem.
- c627627Tutor
I am grateful for your repsonse. If you could perhaps provide a link on how to do this, I would follow it and submit the alert for them to look at this thread myself.
- DarrenMSr. NETGEAR Moderator
I have escalated this thread to our engineers for them to take a look at the issue.
DarrenM
While I'm grateful for you drawing engineering attention to this issue/thread, for 4 CONTINUOUS MONTHS your customers have been on these forums - for lack of any other place to report - that you have broken DNS on MULTIPLE Netgear router models (mine is an R8000, numerous threads for that one too). We get errors like the one below endlessly. I have just ordered a replacement router (obvious not Netgear, and never again) because I'm left with a choice of rolling back several releases and reverting a number of critical bug fixes or having constant errors like:
DNS error, fittingly on Netgear Community site
- BubbaWInitiate
My short story....Please pass this on to Tech support even tho it concerns R8000P AC4000....Thanks !
*Purchased R8000P AC4000 Dec 2020 Firmware 1.4.1.50
--Router worked satisfactorily and chose to attempt to update firmware in Feb.....unsuccesful as manyyyyy are aware !
--revisited updating months later since router was still working satisfactorily and VIA these support forums discovered the problem with
Firmware 1.4.1.50
--On 11/29/21 after re-reading many new threads concerning the flaw, chose to re-try the 4 steps I ran across earlier in year
1* updating thru router menu
2* manual download of newer firmware chk file
3 *attempted thru Netgear app
4 *by following How to upload firmware to a NETGEAR router using TFTP client? | Answer | NETGEAR Support
Gave in this past tues 11/30 and called Customer service...
* Dealt with first agent, very cordial/helpful....tranferred to next tech
* Informed 2nd tech(Ashish) of issue, also vey cordial/helpful...was informed I would be contacted in 24/48 hrs to further my case
* 12/2 rcvd email approving free replacement with refurbished unit....RMA # 3683766 Case ID 45391292. I personally chose $17 shipment whereby they send unit when available.
* 12/3 Rcvd unit
* 12/4 placed refurbished unit into service and for next few days dealt with DNS and page loading slowness issues. Checked issues on my end, changed DNS servers to google servers....8.8.8.8/8.8.4.4 with no sucess
* 12/6 ran across this thread and others threads concerning V1.4.2.84_1.3.42 DNS issues
* Today 12/7, reverted back to V1.4.1.68_1.3.28 and so far have had no DNS issues and page loading is back to as it should be.
Personal lesson learned....will not up date firmware until I check these support forums for satisfactory firmware update !
Thanks,
Bob Williams
- David53Aspirant
I am having the exact same issue as described in this thread. I get the "Hmmm ... cannot reach page" error. It says check spelling. A few clicks and I usually I finally get the site. It has caused me major problems when it happens when I am paying on checkout. My firmware is v1.0.4.120. It says it is the latest.
R6400: AC1750 Router. I also am ready to buy a new non NETGEAR router.
- mjcyberTutor
Downgrading to a vulnerable firmware is not a solution.
Firmware V1.4.2.84_1.3.42 has buggy DNS and no amount of toggling, resetting and tweaking will fix it.
Netgear needs to properly support their product and provide a firmware that doesn't break everyone's DNS.- FURRYe38Guru - Experienced User
You'll need to contact NG support and let them know what your experiencing.
https://my.netgear.com/support/contact.aspx
In meantime, either downgrade or use it as is.
mjcyber wrote:
Downgrading to a vulnerable firmware is not a solution.
Firmware V1.4.2.84_1.3.42 has buggy DNS and no amount of toggling, resetting and tweaking will fix it.
Netgear needs to properly support their product and provide a firmware that doesn't break everyone's DNS.I think the poster's point is that this thread has 1579 views, and having this issue marked as solved is not helping to potentially bring it to Netgear's attention. Netgear obviously pay almost no attention to their own forums, but trending issues like this at least have a chance of catching notice if they don't have a big green tick incorrectly suggesting the issue is resolved. I'm not sure what correct forum etiquette is about that.
You're right of course that each of us need to report it directly to Netgear. Others will presumably find as I did that official support has no interest in discussing a firmware problem with a product not purchased in the past 90 days. Ultimately I have had to replace my router and won't ever return to Netgear (Netgear broke DNS on multiple models 6 months ago and have not acknowledged let alone fixed this), only commenting here because I got an email about activities on threads I still cared about when I used the product.
My observations on this issue fwiw:
- It does not appear to affect Macs, so there appears to be an interaction with Windows. This is true across multiple browsers (Brave, Chrome, Edge), that they were fine on Mac on not PC.
- It is repeatably a problem after bring a Windows machine out of sleep.
- The impact is really under-estimated by those commenting on it without experiencing it. Interactive activities, like posting a web form, or completing a banking transaction, are particularly likely to fail because the different steps in the process use different DNS. Some failures are hard to attribute to this until you track them down (e.g. multiplayer servers on Xbox failing because of DNS when already connected in the game). These are high user pain scenarios, where you lose what you were working on, or transaction fails and reattempting has unknown consequences or is not possible, or the user is not in control of re-attempts. This bug is a disaster and makes the router pretty much unusable, hence the anger at it not being fixed.
I had to give up on Netgear and move on, but I won't be a customer again.