NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Feb 25, 2019Guru - Experienced User
New - NetGear Orbi Firmware Version 2.3.0.32 now available...
FW 2.3.0.32 is now available on our support site :
https://www.netgear.com/support/product/RBK50.aspx#download
RBR/RBS 50 Series Only.
To manually update the firmware, there is a need to ...
FURRYe38
Mar 05, 2019Guru - Experienced User
I recommend manually updating FW using a wired connected PC with the router or satellites for FW updates to help avoid problems when using Auto Update.
What is the Mfr and model# of the ISP modem the NG router is connected too?
Is the Wall satellite the only satellite you have with the RBR40? No RBS units?
Turn OFF the RBW and reboot the RBR40 and test wifi range. Do you get connections and range with out the RBW?
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials.
What is the home building materials made up of?
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
What WPA security modes are you using?
Try enabling Beamforming and MIMO.
Beer79 wrote:
This is my 2nd replacement unit as the first setup the wall satellite decided to brick itself when an automatic firmware installation happened around 5 months ago. So have had the replacement around 4 months all seemed to work ok at first. Noticed the drop in WiFi around a month ago but put it down to a bug in the firmware, so have waited for a new release to see if the problem would rectify itself.
Both units are on the latest available firmware from the orbi site, The rbr40 is in the hallway in ap mode as the current providers router is set in bridge mode with an ethernet connection between the two. The wall satellite (rbw30) is set up around 10 meters from the rbr40 in another room plugged in around a metre from the ground. Using WiFi anyalzer app on Android phone when standing directly above rbr40 the signal strength shows 60dBm walk a metre away from the rbr40 and the signal drops to 80dBm. For all other signals whether it's the wall satellite 5ghz or 2.4 or 2.4ghz on the rbr40 the signal strength is hitting 40dBm or higher and the same for the backhaul channel on the rbr40 that shows 30dBm when on top of router. Have changed channels, played around with various settings, transmitter power, fast roaming etc. But the problem still exists that's what makes me think it could be a hardware problem, potentially a faulty 5ghz radio transmitter?? The 5ghz network still works within the house but all devices are connecting to the wall satellite and refuse to connect to the 5ghz router as the signal is too weak. Looks like I may have to return the item back to Amazon or put up with the defect??
walkerx
Mar 05, 2019Guide
well updated to the latest firmware on my new orbi's and this is what i've found so far
1) still no improvement in connection with satellites after reboot of main orbi, still takes 5 minutes plus for the satellites to show in the status of software.
2) connection for satellites, still show as 5ghz wifi even though one is using wired backhaul
3) still no access via mobile app if connected via a satellite
4) accessing gui interface of satellite from pc can be slow
5) wired satellite knows which devices are connected via wire, so knows connected via wire
6) satellite using wifi backhaul, constantly disconnecting (approximately 25ft away from main orbi) and going through config sync again
- FURRYe38Mar 05, 2019Guru - Experienced User
I would reset both router and satellite and setup from scratch and see how things go. 25 feet maybe too close. If you can't move the satellite a bit farther out, you can try to set the power output level from 100% to 75% and see if this helps with the distance.
walkerx wrote:
well updated to the latest firmware on my new orbi's and this is what i've found so far
1) still no improvement in connection with satellites after reboot of main orbi, still takes 5 minutes plus for the satellites to show in the status of software.
2) connection for satellites, still show as 5ghz wifi even though one is using wired backhaul
3) still no access via mobile app if connected via a satellite
4) accessing gui interface of satellite from pc can be slow
5) wired satellite knows which devices are connected via wire, so knows connected via wire
6) satellite using wifi backhaul, constantly disconnecting (approximately 25ft away from main orbi) and going through config sync again
- walkerxMar 05, 2019Guide
I shouldn't have to reset everything and start from scratch again, not only that its a pain in the neck having to move everything so they in the same room so can get it configured and setup.
Even the initial install took a couple of hours of getting it working and that was when they were next to each other and using the mobile app.
Overall, setting up the orbi's have been worse than setting any other part of my network
- FURRYe38Mar 05, 2019Guru - Experienced User
Sometimes it's needed. You should be able to make a backup, factory reset and then restore the backup.
walkerx wrote:
I shouldn't have to reset everything and start from scratch again, not only that its a pain in the neck having to move everything so they in the same room so can get it configured and setup.
Even the initial install took a couple of hours of getting it working and that was when they were next to each other and using the mobile app.
Overall, setting up the orbi's have been worse than setting any other part of my network
- SW_Mar 06, 2019Prodigy
>> 6) satellite using wifi backhaul, constantly disconnecting (approximately 25ft away from main orbi) and going through config sync again
Had similar problem with latest v.32 as well, but my 2 RBS50s are about 40ft-50ft away from RBR50 AP. I've never had this problem prior to upgrade. The 2 RBS50s are looping constantly, config_sync -> good -> config_sync-> good, every 5-10 seconds. Reverted back to v.210, everything works as expected. Upgrade to v.32 again, same problem shows up. Going back to v.210, the problem disappeared as expected.
FWIW, the new v.32 has better tput/speed than v.210 when it works.