NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
murchman
Dec 12, 2016Apprentice
New Firmware 1.4.0.18 released
Bug Fixes: Fixes the add-on satellite sync issue. Supports the NETGEAR Orbi app. http://kb.netgear.com/000036450/RBR50-RBS50-Firmware-Version-1-4-0-18
DarrenM
Dec 28, 2016Sr. NETGEAR Moderator
Hello dethier1958
This is a odd issue is it just on your main PC or any device when using the web login?
DarrenM
dethier1958
Dec 28, 2016Guide
I solved the problem by changing the static IP address of my computer. Not sure why that fixed it. But I have a hunch.
I originally set up the Orbi from this computer, connected to the router by ethernet, with a static IP address of 192.128.1.250 ... And almost every time I tried to list the attached devices in the web interface, I would get that message about another device being logged in. Other pages in the web interface seemed okay. When I used another computer on my network, also connected to the router by ethernet, but with a different static IP address, no problem.
So I tried changing my IP address to 150, then later to 251. I have not had that problem since. So I wonder if setting the router up with a computer with a static IP address caused some kind of problem where the router remembers that IP address, or creates some process using that IP address, which then conflicted with my computer's IP address. Because, along with this error, I would sometimes get an error from my computer saying there was another device on the network with the same IP address.
So seems like some sort of glitch in the firmware possible related to initial set up from a computer with a static IP address.
- Imthe0neDec 28, 2016Guide
dethier1958,
I don't know if it is a typo or not, but I wouldn't recommend using the 192.128.x.x as an IP range. This is technially a public range, I would move it to a private range "192.168.x.x". In the off chance that you start coming across webpages that are hosted in the 192.128.x.x space, you would find yourself in a problematic situation of not being able to access those sites, as it is going to send you to your local addresses instead.
- dethier1958Dec 28, 2016Guide
Sorry, it was 192.168.1.250 ... and is now 192.168.1.251 and no repeat of the problem.