This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have an RBR750 and RBS750. Last week I noticed that none of my devices were connecting to my satellite. I checked the router's page and saw that the satellite was not on the network. I tried reboots and re-syncs and it would not sync or join the network.
I brought the satellite into the room with the router, it still would not sync. I then connected it via ethernet. It got an IP but still would not come online as a satellite. I logged into the web admin console. That's when I saw the RBS750 was running firmware 4.6.8.2 while my router still had 4.6.5.14.
Netgear's support site recommended putting the latest firmware onto my satellite so I pulled down RBS750-V4.6.5.14 from Netgear's website because it was listed as the Latest for my device. I used the web console to flash the RBS.
Now it's a brick. It will boot, it will eventually come up and get an IP via ethernet. But the web console's status page does not finish loading, does not report a firmware version. The fwUpdate page can be accessed via direct URL but it won't upload firmware. Factory resets don't help.
What can I do to get a working satellite? Thanks! I found another thread about the 750s and 4.6.8.2 today but that thread is locked.
I started going through the process for TFTP today, and had the RBS directly connected to my PC. I noticed the power LEDs weren't cycling in the way the TFTP guide suggests they would. Out of curiosity I checked for a web server at 192.168.1.1, no answer. I checked 192.168.1.250, which I found from another post that said .250 was the default IP for Satellites that couldn't connect. No answer. Then I tried 192.168.1.28, which is the IP that the RBS was last given via DNS from the RBR. It was responding there. Also, the status page now said that the RBS FW was v4.6.5.14, which I had attempted to flash the night before but didn't seem to boot successfully over the weekend (no answer on WiFi, would only connect as a device when hardwired, and could not report its status).
But today? Today it booted up as a functioning Satellite and connected to my RBR. It's now working as part of the mesh. I don't know what's different than yesterday when it didn't know its identity. My best guess is that the firmware downgrade actually worked but something was stuck in memory or some circuitry was behaving in a bad way. After being disconnected from power and ethernet for 12+ hours, something finally dissipated?
Anyway, working somehow, for now at least.
Another interesting piece of information: Over the weekend (both when on 4.6.8.2 and half-alive on 4.6.5.14) the RBS accepted the default login credentials of admin/password. But today it rejected those credentials and INSTEAD it accepted admin/<my personal password for the RBR>. Yeah, it went from "I only accept my default password" to "I only accept your customized password." It almost seems like 4.6.8.2 itself made the memory unreadable in a way that survives reboots but now after a night of rest the values are readable again. Weird.
I started going through the process for TFTP today, and had the RBS directly connected to my PC. I noticed the power LEDs weren't cycling in the way the TFTP guide suggests they would. Out of curiosity I checked for a web server at 192.168.1.1, no answer. I checked 192.168.1.250, which I found from another post that said .250 was the default IP for Satellites that couldn't connect. No answer. Then I tried 192.168.1.28, which is the IP that the RBS was last given via DNS from the RBR. It was responding there. Also, the status page now said that the RBS FW was v4.6.5.14, which I had attempted to flash the night before but didn't seem to boot successfully over the weekend (no answer on WiFi, would only connect as a device when hardwired, and could not report its status).
But today? Today it booted up as a functioning Satellite and connected to my RBR. It's now working as part of the mesh. I don't know what's different than yesterday when it didn't know its identity. My best guess is that the firmware downgrade actually worked but something was stuck in memory or some circuitry was behaving in a bad way. After being disconnected from power and ethernet for 12+ hours, something finally dissipated?
Anyway, working somehow, for now at least.
Another interesting piece of information: Over the weekend (both when on 4.6.8.2 and half-alive on 4.6.5.14) the RBS accepted the default login credentials of admin/password. But today it rejected those credentials and INSTEAD it accepted admin/<my personal password for the RBR>. Yeah, it went from "I only accept my default password" to "I only accept your customized password." It almost seems like 4.6.8.2 itself made the memory unreadable in a way that survives reboots but now after a night of rest the values are readable again. Weird.
Glad you got it working. Seems to have worked it self out.
I believe it's not the v.2 FW thats caused this, rather the auto update system and how it was applied that causes this. NG is experienced a high volume of bad updates that was recently pushed about two weekends ago. I believe it effected users that had not manually updated to v.2 prior that actually I posted about about a week prior to NG pushing it via the auto update path. Some of us included me had v.2 loaded on our systems manually and had not seen problems as expressed by you and others. v.2 FW is ok in it self when manually loaded. What ever caused the FW updates to go bad while being auto updated is still a mystery. Not the first time auto update has caused problems.
This is what finally worked for me, holding down the reset button on the satellite for > 1 minute. I'm so glad I stumbled across this suggestion, I tried the 30-30-30 thing and it did not work.
The satellite UI would accept my login credentials, but after that the UI would only partially load, and would show the spinning icon forever. This was after I downgraded my satellite from 4.6.8.2 to 4.6.5.14 (which was the same version that the router was running). I thought I had bricked one of the satellites when I downgraded. Could not get nmrpflash to reflash the firmware on the satellite.
I had my satellite hardwired to the router when I did this 1 minute reset. The router reset as well, to my surprise. It started to light up magenta, then after a few minutes, the satellite appeared as being connected in the router's UI.
I did lose the connectivity to the other satellite in the process. I could ping the other satellite's IP address, but I could not get into the UI, and it would not sync. I tried the sync buttons multiple times, on the satellite then the router, then vise versa (some websites said to try this as well). A power cycle fixed the issue.
Is there an option to not have the system auto-update? This has been an unnecessary ordeal.
