NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cannot update device names/types
My system consists of 1 RBR50 and two RBS50 satellites running in AP mode behind a router with DHCP server. Ever since I performed the firmware update to 2.3.5.30 (although I'm not 100% sure if it's...
Problem got progressively worse after update of all Orbis to V2.5.0.38. Half of the device name entries can be changed, the other half refuses to change (at all). Doesn't matter if the device is connected to router or one of the satellites (my system has one RBR50 and two RBS50 satellites). After the update, I even switched off the satellites, deleted the device connection and reconnected them again. No change. If I look in the web interface of the satellites, 2.4 kHz connections are not shown (although they're definitely there, I pinged them) and the other device names show as "UNKNOWN" although they're specified in the RBR50. What's going on here? Do I have to completely reset the satellites and router to default after every firmware upgrade? Really?
- It got worse again tonight: I decided to see whether disconnecting, resetting and reconnecting the satellites would help. It changed nothing. Still the names cannot be changed. And what's worse: I could connect both satellites again, but the second one, while being correctly shown in the web pages of the router as connected with the right name and IP-number, cannot be pinged anymore! This means that opening the web interface also doesn't work. When looking in the web interface for the first satellite all connected devices are shown as UNKNOWN. What's happening with the second satellite, I don't know. Perhaps the reset damaged the firmware part for the web server. I also gave the second satellite a different IP number in the DHCP router (the Orbi router doesn't do that as it's in AP mode). It's correctly shown again in the web interface of the Orbi router and also in the DHCP router but it still cannot be pinged on the IP number. Any help would be appreciated.
Have you removed or disconnected the RBS from the RBRs web page. Then factory reset the RBS and then re-sync them wirelessly, one at a time while in the same room as the RBR?
If you can get them added one at a time, do a IP address reservation for each RBS on the RBR for them.
There is nothing you can do for the device naming issue. NG will have to get it fixed hopefully in the next FW update.
- That's more or less exactly what I did. I didn't reconnect them in the same room wirelessly, but in good proximity. The connection is good. I have IP reservations for both satellites, but since I cannot ping the second one, I changed the reservation for that one to a different IP to see what happens. As I said, the router web page now shows both satellites well connected with the right data and IP numbers but I cannot ping the second one anymore, nor can I get to its web page, of course.
By the way, I did not remove the first satellite by clicking the remove button on the router web page before I reconnected it. I only did it before reconnecting the second one. Could that be a reason? Although, the first one works as expected.
Looks like I have to factory reset everything now... - Don't worry about that problem anymore. I just switched off the second satellite, changed its DHCP binding to another IP number again and then had the satellite restart... after some white flashing the ring turned blue and then after several minutes it turned off. Checked the ping and it was working. Could log in to the satellite's web page as well. So, at least I'm back to where I was. Now I'm waiting for an update for the FW to solve the naming issue...
Anything is possible.
Does the RBS work in regards to internet connections for the one RBS that you can't access or ping?
I would factory reset. I would swap RBSs as well. Install the 2nd RBS first wirelessly. Besure the other RBS is turned off. Once the RBS is installed, set up a IP address reservation for it and save and apply. The RBR will reboot. Check to make sure you can ping and access it's web page. If so. Log off and turn it OFF. Power on the next RBS and do the same thing. Once IP reserved and the RBR reboots check Ping and web page access. If good. Power off the RBS. Please the RBSs at there remote locations. Power ON the RBS 1 at a time. Then check for ping and web page access.
jtcommunity wrote:
That's more or less exactly what I did. I didn't reconnect them in the same room wirelessly, but in good proximity. The connection is good. I have IP reservations for both satellites, but since I cannot ping the second one, I changed the reservation for that one to a different IP to see what happens. As I said, the router web page now shows both satellites well connected with the right data and IP numbers but I cannot ping the second one anymore, nor can I get to its web page, of course.
By the way, I did not remove the first satellite by clicking the remove button on the router web page before I reconnected it. I only did it before reconnecting the second one. Could that be a reason? Although, the first one works as expected.
Looks like I have to factory reset everything now...Thanks for the procedure.
As I said in the next post, I solved the problem myself. I have no idea why what I did din't work two times and then worked the third time I did it. What is different from your proposal is that my RBR does not do the DHCP binding, because it is set up as an AP.
The IP number comes from the router of my internet provider.
Perhaps something was wrong or needed to restart there...
Well that explains more. Well if the Orbi is in AP mode, then any DHCP reservations behaviors on the upstream router would need to be looked at there.
Something else to try later on if you want to, disable ALL wifi radios on the modem, configure the modems DMZ/ExposedHost or IP Pass-Through for the IP address the Orbi router gets from the modem. Then you can use the Orbi router in Router mode.
jtcommunity wrote:Thanks for the procedure.
As I said in the next post, I solved the problem myself. I have no idea why what I did din't work two times and then worked the third time I did it. What is different from your proposal is that my RBR does not do the DHCP binding, because it is set up as an AP.
The IP number comes from the router of my internet provider.
Perhaps something was wrong or needed to restart there...