NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAX40 Firmware 1.0.3.80 Crash/Bug Log
Hello folks, can everyone please log all the issues they are experiencing with the RAX40 router on 1.0.3.80 firmware under this thread, I see there are several threads going on about the issue, figur...
Still same issues with a rollback. I really can’t believe how awful this is. Went through level 2 tech support. Company stands behind their products a whole ninety days! Lol. The software for this RAX 40/35 is a mess. I wish we could get refunds. This is a joke. Lost a customer for life.
- Same here
very disappoint with netgear. they should TAKE DOWN this defective firmware that is causing wifi drop. they don't because they want people to contact them and charge them for simple reverting back. take the firmware down and issue a new one once is fixed....very bad service netgear....
- Agreed. Silence from Netgear should not be an option. I would not purchase any of their products if it’s not resolved. Thanks community.
Reveted to 62 no luck.
Reset to Factory settings, no luck.
Went back to my little old Trendnet, no problems now.
Whish I nevee spent so much on this device, at least it was on a Black Friday sale.
Can't disable coexistence because my BluRay uses the 20Mhz network and my other devices use the 40.
ok, what i learned is to download the older firmware version from Netgear website, look for the older version
V1.03.64_101 and go into the Admin settings of the route and update firmware manually.
After i did that everything works again back to normal. It tooks me a few days of playing with setting and resets, but today i downloaded and tried the older version and it works
give it a try. Also turn off auto updates so it doesnt happen again, and hopefully another update will come out
stay away from 3.80 version
- For myself I had the same drop and disconnects on the older firmware. I suspect DHCP authentication issues when a device tries to reconnect after being off or away. It tries to assign the old IP to it, fails, and gives is a 169.xxx etc address, which means authentication failure. I’m not a network engineer, but DHCP service should be one of the first things you get right. Hope they find fixes... soon