NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
aupton
Feb 24, 2019Tutor
Orbi [WLAN access rejected: incorrect security] from MAC address ... post auto upgrade to v2.2.1.210
My Orbi recently auto-upgraded to the latest version of firmware (with great timing as I had just gone away for two weeks for work so I had a family at home missing internet access more than they mis...
- Feb 24, 2019
Thanks, I just tried to reapply and that didn't work. However, I think that I may have just found the problem. I just noticed, when I looked at the logs that the date (at the top of the page) was wrong. I went to the NTP settings and saw:
Current Time: Wednesday, Sep 26, 2018 20:58:10
Warning: The Orbi Router failed to connect to NTP server, please check your internet connectivity or try another NTP server.
The correct date and time are important for security validation so I think that this may be the root of the issue. I am trying to use a different NTP server pool with no success.
ekhalil
Feb 24, 2019Master
Have you tried to just forget the wifi network from those devices and try to attach again?
- auptonFeb 24, 2019Tutor
Hi,
Yes (should have mentioned that!) I did a factory reset on the Alexa's and they still cannot connect. The block list for the MAC address is likely being stored on the Orbi Hub.
Alastair
- ekhalilFeb 24, 2019Master
It can be that the AP Mode setting is -somehow- "forgotten" by Orbi after the SW update, can you please go to the Route / AP Mode setting page and again mark the AP Mode (even if it's already marked) and click on Apply as follows:
- auptonFeb 24, 2019Tutor
Thanks, I just tried to reapply and that didn't work. However, I think that I may have just found the problem. I just noticed, when I looked at the logs that the date (at the top of the page) was wrong. I went to the NTP settings and saw:
Current Time: Wednesday, Sep 26, 2018 20:58:10
Warning: The Orbi Router failed to connect to NTP server, please check your internet connectivity or try another NTP server.
The correct date and time are important for security validation so I think that this may be the root of the issue. I am trying to use a different NTP server pool with no success.