NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR750 403 Access denied after upgrade to 4.6.3.7 firmware
I'm getting a proxy error from the router, and am unable to access its configuration page after firmware update from 3.x version to 4.6.3.7. I factory reset the router, and then I'm able to conne...
Netgear has set up a community forum specifically for the Orbi AX product. Most of the people who watch that forum are more likely to have experience with Orbi AX and know how to work it better than those of us who follow this "general Orbi" forum. Might be more likely to find someone who has a solution if the question is posted there:
https://community.netgear.com/t5/Orbi-AX/bd-p/en-home-orbi-axThank you.
Got an RBK852 & having the exact same issue on Firmware 4.6.3.9.
I understand, this may not be the correct forum, but my initial point is that this issue is not limited to a single model or one exact firmware version.
Based in a comment from raven_au in a different thread, I've been able to confirm the issue appears to be related to using a public IP range for the router's private LAN. Ie. I was using 192.100.17.x for my IP range, which started generating this same error since my last firmware update. And since that range worked flawlessly in former firmware versions & on more than 8 other router brands & models for over 10 years, it didn't occur to me that my chosen IP range was the cause.
Summary - Use a PRIVATE IP range & see if you continue getting this error.
Fortunately, I didn't have to suffer through Netgear's absolutely HORRIFIC, sad excuse for technical support... I thank my luck stars again for that, alone!!
NETGEAR - Please, please document this new limitation within your firmware release notes!!
Had it been declared there, it would have been a huge favor to all of us... And we wouldn't have wasted so much time chasing it down. Whether the behavior was previously allowed via a "bug" or not is irrelevant. It's quite clearly a functional change implimented via firmware versions. Thus, should be documented as such.
Thanks,
I understand, this may not be the correct forum, but my initial point is that this issue is not limited to a single model or one exact firmware version.
Based in a comment from raven_au in a different thread, I've been able to confirm the issue appears to be related to using a public IP range for the router's private LAN. Ie. I was using 192.100.17.x for my IP range, which started generating this same error since my last firmware update. And since that range worked flawlessly in former firmware versions & on more than 8 other router brands & models for over 10 years, it didn't occur to me that my chosen IP range was the cause.
Summary - Use a PRIVATE IP range & see if you continue getting this error.
Fortunately, I didn't have to suffer through Netgear's absolutely HORRIFIC, sad excuse for technical support... I thank my luck stars again for that, alone!!
NETGEAR - Please, please document this new limitation within your firmware release notes!!
Had it been declared there, it would have been a huge favor to all of us... And we wouldn't have wasted so much time chasing it down. Whether the behavior was previously allowed via a "bug" or not is irrelevant. It's quite clearly a functional change implimented via firmware versions. Thus, should be documented as such.
Thanks,