NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Error: "Couldn't Authenticate Connection"
I'm running the R8000 and had been running what today is the most recent firmware (1.0.4.74) but based on other threads just rolled back to 1.0.4.46 in hopes of grabbing a pre-Armor version hoping it might get me past this issue. No joy.
Issue: Primarily finding it limited to mobile phones, when attempting to connect to 2.4g an error continues to be encountered which simply states "Couldn't Authenticate Connection".
Multiple reboots of the router and mobile phones don't seem to work, in any particular order. But then after days of not being able to connect it will simply start working. If I do anything, such as attempt to get another smart device (switches, bulbs, etc.) added back to the network (because I'm finally able to connect again), then I may be lucky enough to get a 1-2 added before the authentication error begins happening again.
I am not using Smart Connect as it is near impossible to get smart devices to connect to the network with this enabled, and as such disabled it long ago.
I do have different SSID for the 2.4 and 5.0 networks, again - this allows me to easily select the correct network when attempting to enable smart devices which require 2.4 network access.
I use port forwarding for one port (Plex) but other than this, all other settings and security features are default. I've disabled auto-firmware updates, as it would be counter productive to roll-back and then watch it auto-update to latest version again.
Something I can add is that I've tried swapping between Dynamic and Static Phone MAC addresses across the different phones (Andriod with all latest updates). It does not seem to make any change to the behavior outlined above.
Before attempting a factory reset, which would have me re-adding 50+ smart devices all over again, I am hoping someone may have insight or ideas. Please advise... and thank you, in advance!
Update:
Reset the router and figured I'd let it update to latest firmware, being I'd be able to reset it again if there were any signs of trouble (V1.0.4.76_10.1.82). Ran for a bit and all seemed well.
Enabled Smart Connect, thinking that once I was ready to start adding IoT devices I'd disable 5.0G SSID but as I started adding 5.0 compatible devices (Google Mini's, etc.) I took a stab at some 2.4G devices and they were adding without issue. I've proceeded to add the remaining devices (all while having Smart Connect enabled - to my amazement), and everything is working, and none of the mobile phones are getting authentication errors.
Appreciate the responses, folks... will stick a fork in this one!
10 Replies
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
How is the wireless radios configures? Up to Speeds? What channels are you using? What wireless security mode are you using? Should be WPA2-AES only.
WMM should be enabled as well.
Does this error only appear on wireless devices? Wired devices ok?I would try a full on reset and setup from scratch.
I'm running an Arris SB6190 modem.
Wired devices have no issues, and neither do the mobile phones when connected to 5.0G SSID. This is only with the 2.4G SSID.
I have the channel set to "AUTO" and mode set to "up to" 600Mbps.
As stated, and it is confirmed, the only security mode I'm using is WPA2-PSK [AES]
Note that wireless smart devices, once connected to the network are working fine. This includes Google Mini's, Fiet smart bulbs, KASA smart switches, etc. Even with a 100 different resets of the network, these smart devices reconnect every time. It does seem to be mobilve devices only that this issue is limited to. And the only reason it's an issue is that I need to use a mobile device to connect smart devices to the 2.4G SSID. Otherwise I'd live on the 5G and call it good.
What happens if you change from AES to TPIK on 2.4Ghz?
