NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBS850 - Out of Sync
Hello,
My Mesh System satellite (RBS850) is showing Out of Sync.
I have tried to connect directly to it, via ethernet cable, and:
- can not connect to it via http://192.168.1.250
- it correctly responds to ping command on IP address: 192.168.1.250
- by scanning ports on 192.168.1.250 I am getting following response:
Nmap scan report for 192.168.1.250
Host is up (1.0s latency).
Not shown: 999 closed tcp ports (conn-refused)
PORT STATE SERVICE
53/tcp open domain
Nmap done: 1 IP address (1 host up) scanned in 201.40 seconds
I did exactly the same scan for my second (RBS850) satellite, to which I can connect via http:
Host is up (0.0042s latency).
Not shown: 996 closed tcp ports (conn-refused)
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
443/tcp open https
5000/tcp open upnp
Nmap done: 1 IP address (1 host up) scanned in 46.21 seconds
Clearly the HTTP/HTTPS server is running on working RBS but not on the faulty one.
I have tried to reset faulty RBS multiple times but I always get the same result.
Does it mean that my satellite is dead and nothing can be done to fix it?
Is Negar able to help in such cases?
Thans a lot!
10 Replies
I saw a discussion describing how Netgear changed the default LAN IP for Orbi AX model satellites, such as the RBS850. When they were first introduced, a Factory Reset resulted in the satellite responding to 192.168.1.250, but sometime later (no one seems to remember exactly when), Netgear changed the firmware and now when an AX satellite is Factory Reset, the default LAN IP is 192.168.10.250 To add even more frustration, Netgear has never updated the user manuals to reflect this change.
It might be worth making another attempt with 192.168.10.250. It is quite a chore (at least for me) to set a Static IP on my computer/laptop in the 192.168.10.x subnet, disconnect from everything else, power up the satellite, open a web browser and connect to 192.168.10.250 When the satellite responds and I see that it has a different firmware version than the router, I say, "dammit. I should have downloaded the satellite firmware for that version. now I have to undo everything, get the right firmware file, and do this all again."
bogbogandbog wrote:
Is Netgear able to help in such cases?
People usually come to the Community Forum because their 90 days of 'complimentary support' have long expired (and maybe the one year warranty as well) and they are reluctant to pay Netgear a lot of money to talk to someone who is likely to say, "beats me, dude." If the warranty has expired, for certain Netgear will do nothing.
CrimpOn thank you for your message.
I confirmed that the satellite uses 192.168.1.250.
I have other same model satellite and indeed it uses 192.168.10.250.
It seems that the http service for some reason is not starting on 192.168.1.250 and this is the whole problem.
If Netgear is not willing to help then this product is useless. I wish there were other way to flash the firmware...My understanding is that Netgear's primary response when a device does not work is to replace it. But that only applies if it (a) is part of an original purchase from an authorized retailer (not used), and (b) is within the warranty period.
I find the default LAN IP issue frustrating. After a Factory Reset, if the satellite is responding to 192.168.1.250 that would seem to indicate that it has firmware from before Netgear made that change to 192.168.10.250
Was this satellite "working" before and has stopped working, or was this recently acquired and has not been made to function yet? (i.e. could it actually have older firmware on it?)
Knowing the MAC address and the LAN IP address are key because most Netgear products go through a process when powered on that involves activating a TFTP server to accept a firmware load. I have done this on a couple of Orbi satellites (but not recently) and found it to be "not fun". I would get the firmware file loaded on a PC. Have the TFTP client ready to go. Then power up the satellite. Try to start the transfer too soon... fail! Wait a second too late.... fail! I failed five times in a row and was about to dump the device in the trash, and thought, "what else do I have to do right now?" Worked!
Since TFTP operates over UDP rather than TCP, the device sending packets gets no response from the server after each packet. That's also why it matters so much to have the correct LAN IP address. If it is really 10.250 then it will not accept a TFTP transfer to 1.250 (or the opposite).
What FW version is loaded on the system?
