NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
adavidso
Mar 24, 2024Tutor
Access Denied after update to firmware version v1.1.4.28
This issue is still a problem where login becomes impossible through a browser (only when internet is connected on wan port). Only solution is to roll back to earlier firmware and factory reset and tu...
adavidso
Mar 25, 2024Tutor
Thanks for the reply. This thread is about a defective firmware update first identified here: https://community.netgear.com/t5/Nighthawk-with-WiFi-6-AX-and/Access-Denied-after-update-to-firmware-version-v1-1-4-28/m-p/2362757#M37766.
That thread was "solved" however I wanted to be clear that the solution required a rollback to previous firmware and turning off automatic firmware updates, so it is not really solved.
My ONT is a Nokia modem only with no extra ports or router functionality. This is not caused by double NAT.
That thread was "solved" however I wanted to be clear that the solution required a rollback to previous firmware and turning off automatic firmware updates, so it is not really solved.
My ONT is a Nokia modem only with no extra ports or router functionality. This is not caused by double NAT.
michaelkenward
Mar 25, 2024Guru - Experienced User
adavidso wrote:
Thanks for the reply. This thread is about a defective firmware update first identified here: https://community.netgear.com/t5/Nighthawk-with-WiFi-6-AX-and/Access-Denied-after-update-to-firmware-version-v1-1-4-28/m-p/2362757#M37766.
So your message cropped up with no connection to past discussions.
I think there were several conversations on that issue.
This seems to have been the most useful contribution:
Solved: Re: Access Denied after update to firmware version... - NETGEAR Communities
Then there was this:
Solved: Re: New - RAX41/42/43/50/54 V2 Firmware Version 1.... - NETGEAR Communities
As you say, it isn't SOLVED but there were workarounds to get you out of the immediate hole.
- adavidsoMar 25, 2024TutorAgreed, and thanks for this. I suggest that this thread remain unsolved until either 1) firmware 1.4.28 is fixed or 2) a subsequent firmware is released that solves this issue.