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...
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!
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?
Made the change, recycled all devices and tested again - no change. Same error "Couldn't Authenticate Connection"
Doing the reset may be worth it at this point, far more hours into fooling around with it than it would have taken to rebuild everything...
iamfozz wrote:
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.
Going back to the original issue, what says "Couldn't Authenticate Connection"?
Is this message from the phone when you are setting up IoT devices? Or always?
It smells like a client issue rather than anything to do with the router.
Most of these connect to 2.4 GHz. Better range and fast enough for most devices.
Of course, they can't see 5 GHz but too many of these come with horribly designed software that won't set up properly if the phone connects to 5 GHz wifi.
Fortunately, the R8000, unlike Orbi and other mesh wifi technologies, lets you turn of the 5GHz SSID broadcasts. You can do that temporarily while you set up IoT toys. Then re-enable it after you've gt things working.
This might be a better option than running separate SSIDs for 2.4 and 5 GHz. Doing that means that you are throwing away some of your router's capabilities and perhaps landing your self with this problem.
It is the phone that says this - and says it most of the time, related to the 2.4g. How or what finally clears up to allow the connection to work is still a mystery but attempting to connect another IoT device is typically met with messing things up all over again, at which point I must wait for the phone and router to play nice again.
I've not had a chance to reset the router yet, so I'll try enabling Smart Connect and then disabling the 5.0 SSID to see if it can be fooled in to connecting. That I should be able to do today.
