NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi RBR50 Device Names not Saving
I'm using the RBR50 through my Verizon Router as an AP and I'm trying to change the device names of my connected devices to know which device is which. Initially, when I was setting up the first few...
I am on firmware version V1.4.1.42_1.3.4 and upgraded from .30. This exact problem showed up after the upgrade.
So apparently Netgear has STILL not been able to fix this problem.
Pathetic. Looking at other router manufacturers now.
kalyson wrote:I am on firmware version V1.4.1.42_1.3.4 and upgraded from .30. This exact problem showed up after the upgrade.
So apparently Netgear has STILL not been able to fix this problem.
Pathetic. Looking at other router manufacturers now.
This is a bit confusing. The model referenced in the post footer lists Nighthawk, yet this is a user forum for Orbi. V1.4.1.42_1.3.4 is not a firmware release for the RBR50. The latest Orbi firmware for my RBR50 updates device descriptions and types and seems to "stick". While the episode has been dismal, and I remain annoyed to lose the pretty pictures and device types, it is hardly a problem I would consider scrapping a network for. (Buying new WiFi because I'm bored and want to upgrade, sure. But, because device names are not the way I like them?)
- Device manipulation, including the naming of devices and selecting device types is Fundamental to any router operation. NETGEAR can’t seem to understand this let alone fix it. It’s embarrassing that they release such atrocious software behind such quality hardware.
Um, your way behind on FW. v2.5.1.8 has solved the device naming issue. Please manually download it and apply to your RBS first then RBR lastly. Factory reset the system and setup from scratch. Then name your devices. It works.
kalyson wrote:I am on firmware version V1.4.1.42_1.3.4 and upgraded from .30. This exact problem showed up after the upgrade.
So apparently Netgear has STILL not been able to fix this problem.
Pathetic. Looking at other router manufacturers now.
And, the release notes say that versions prior to 212 have to be upgraded to it first.
