NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New Orbi firmware 2.1.2.18 update issues?
I noticed that there was a new firmware version 2.1.2.18 for Orbi RBK50. Has anyone installed this version, and has there been any issues after the installation. Please provide any details that you...
Took v2.1.2.18 a few hrs ago did factory reset, nvram clear now sattalite does not show as connected sattalite but as attached as a device to the main Orbi unit! Yes I rebooted both several times as well anyone else seeing this? a devices show connected to main unit as well so nothing fixed for me.
After switcihing off daisy chain 1 of my nearby satellites still only connecting on 2.4
I saw the firmware update fixed the special character wifi password issue. I was also hoping that it would fix the wifi password issue which I have (lower case 18+ characters), but it didn't. Basically, my issue is that it takes several attempts to connect wirelessly and sometimes the lowercase password I mentioned above works and sometimes the default router password has to be used. It's odd because I have changed the default password, but it still accepts the default password. I'm a pretty patient person, but I just got this setup a few days ago and am seriously considering returning it. I heard so many good things about this network, but I didn't think something as basic as a password change would be a problem.
Now 5 reboots in 4 hours. REALLY NETGEAR???
Regardless of the “unknown” connection to my far daisy chained sat with a good connection, I am getting about 12 millisecond pings to all of my 30 devices as I walk around the house with an iPad Pro. 7% load on the router. This is an iPho)e, iPad house with a Roku and a Chromcast thrown in.
AP mode with Fios at 85. DSL report on buffer is B with A+ quality internet ratIns.
- Quick update...I rebooted router and satellites a couple of more times and now my password works and default password no longer works. Thanks Netgear for fixing this.