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...
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...
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...
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...