NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAX 120 authentication issues
For some reason after a period of several hours any device that trys to logon into my wireless system gets an authenication error, the password is invalid. My firmware is V1.0.1.90. I have tried t...
Just throwing my hat in here for the same issues. On 1.0.1.90 as well currently. I think that version fixed an AX issue with my Samsung Galaxy S10+ getting WiFi 6, so I'm hesitant to downgrade. Willing to try the newest version they just came out with and have messaged Christian. I tried to trouble shoot this issue locally for about 4 hours..changed password, removed devices, etc. and am somewhat relieved to see that others are having the same issues. When the wifi does drop and all devices lose access, the 5G stream seems to stay up, just the 2.4 drops. But of course almost all smart devices (over 20 lightbulbs for example) only connect to 2.4. Anyway, will give feedback if I'm able to get and upgrade to new firmware beyond .90, otherwise I'll be downgrading to .84. Thanks.
I'm having the same issues with my RAX120 that's about 2 months old. I've been battling this for a few weeks.
I just managed to stumble on this thread, so I hope whatever case is open for this issue, I can be added as a customer as well.
My router shipped with V1.0.1.90 and I've tried re-applying without luck. I continuosly have to reboot my router, which is unacceptable. I was just watching HULU on one TV and playing on a wirelessly connected desktop on another TV, and my PC disconnects, "Attempting to Authenticate" and the HULU is unaffected.
Spent a good 30 minutes just making sure this wasn't a fluke as a lot of our mobile devices have had the same error the past two weeks. After disabling the wireless on the desktop, moving to another USB port, uninstalling, reinstalling the driver, removing the saved network and trying to reconnect, nothing worked until I reboot the router. All is fine now for anywhere between a few hours to a couple days.
I've opened a case with support since I'm still within that time period, mostly for visibility, and so maybe if this is fixed, I can get the correct firmware. After stumbling on this thread, I've downgraded to V1.0.0.84 as well, and we'll see how it goes.