NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unable to setup RBR50 and a satellite
Last year I moved to a new house that had essentially no Ethernet wiring, so I decided to purchase the RBK53 as it was a 3 story structure, a router or satellite on each floor. I got that set up, al...
What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
When doing FW updates, do not use TFTP, use the RBR and RBS web page for all FW updates. TFTP is for recovery only. Let the main web page do the FW processing.
I would re-load v32 FW using a wired PC and web browser, IE11, FF or Opera is what I have tested that work well.
Press the back reset button for 15 seconds then release. This will ensure the system is clear.
You can update the RBS if they don't connect directly using there web page as well. Do this first.
Wire connect 1 PC to the back of the RBS. Factory reset the RBS, wait about 5 minutes. The PC will get a IP address from the satellite. The RBS will be 192.168.1.250. Use this IP address in a web browser to log in to the satellites web page. Log in as admin and password. Use the satellites web page FW update feature to select the FW update file that was unpacked from the .zip file. Then factory reset and then re-sync the satellites to the RBR.
After you get the RBS and RBR reloaded, I recommend setting up the RBR first while not connected to the modem. You can if you wish. Get the RBR configred first. Skip the RBS sync during the wizard.
Once you have the RBR all setup, Connect it to the ISP modem and make sure it works and you can get internet access here.
Disable Diasy Chain on the RBR.
Then bring the RBS to the same room or near the RBR. 10-15feet is good. Press the sync button the RBS then RBR. The RBS should sync in time. Give a few minutes. You can monitor this by watching the connected devices page. It should appear here as a satellite.
You can at this time set a "Reserved IP address" on the RBR for the RBS if you like. I do this. Save and apply the change.
If you have a 2nd or 3rd RBS, Turn of the 1st RBS and turn on the next RBS. Repeat adding the RBS then giving a reserved IP address.
Once RBS are synced. Power OFF the RBS and place in there remote locations.
30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected. https://kb.netgear.com/000036466/How-far-should-I-place-my-Orbi-satellite-from-my-Orbi-router
OK, well I have already used TFTP to update both the router and the satellite to V2.5.1.32.
I've tried various resets of both the router and the satellite and nothing has seemed to work so far.
I tried again setting up the RBR without being connected to the modem. I then connected to the modem and after a few shenanigans I was able to get it and the Internet. However I am still unable to add the satellite. When I press the sync buttons on both, and they are 3 feet away from each other, they both go to flashing white top LEDs. The satellite goes to solid blue, then goes to solid magenta, while the router remains blinking white. After that nothing changes that I can tell. :-(
Any help to get these set up together would be greatly appreciated!
-tl
Try 10-15 feet away. 3 feet maybe too close.
Can you access the RBS web page if you reset the RBS and connect a Wired PC to the back?
Might try a factory reset on the RBS then connect the RBS with a ethernet cable to the RBR and see if it might sync.
If that fails, possible the RBS could be faulty if it won't connect at all.
Well I think it might be the router and not the satellite. I reset the router and now it appears to be in a boot loop. It goes from white abrupt flashing light, to white smooth flashing light, Then it goes to solid white light, followed by a green flash, orange flash, orange flash, and then white abrupt flashing. This repeats indefinitely. Meanwhile my computer connected via a cable to the router is trying to ping 192.168.1.1 and it goes from:
PING: transmit failed. General failure.
to:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
to:
Request timed out.
to:
Reply from 192.168.1.2: Destination host unreachable.
and basically repeats.