NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi firmware update v2.1.4.16 availability
We’ve been monitoring issues that some customers have experienced in OrbiOS 2.1.4. In response, we’re releasing firmware that provides a permanent fix for the homekit issue along with various other f...
Firmware must be production because they are pushing it through auto update.
As for the most recent post, I recommend you just leave it alone for awhile powered on and give it time to sort itself, that is if all sats showed blue before turning lights off and router has no light. Sorry, but the time in my experience is indeterminate.
As for the most recent post, I recommend you just leave it alone for awhile powered on and give it time to sort itself, that is if all sats showed blue before turning lights off and router has no light. Sorry, but the time in my experience is indeterminate.
I've had to shut down my satellite becaue any device connecting to it has no connectivity to anything but other clients of the satellite -- in short, the backhaul is non-functional.
Stev3D wrote:
I've had to shut down my satellite becaue any device connecting to it has no connectivity to anything but other clients of the satellite -- in short, the backhaul is non-functional.
I think you may have tried this already, or you might think it isn't necessary, but you could move the satellite to the same room as the router, but NOT within 3 feet of it and power it back up and see if the backhaul is working. If it still is not working, I would try the next step, or just skip to the next suggestion if you feel that moving it isn't a suitable test. Another thing to try is to give the satellite a static IP address on the LAN. I like to give all my satellites a static IP address outside the DHCP range, but that might be overkill. I know this is a moot point if you can't seem to talk to the satellite through the router, but if you can access the satellite via its IP address or can see it listed on the connected devices page (whether it shows it as a satellite or just a connected device) its worth a shot. After giving it a static IP, I would reboot the router, and then reboot the problematic satellite(s). As you have already done way too many times before, wait for the satellite(s) to show a blue color and then test again.
If that doesn't work, I'd open a support ticket, or just return the things, if either of those options are still free/available to you. If they aren't I'd try the dreaded master reset on all units after the latest firmware is loaded (cause its just going to auto update back to it anyways if you revert), setup the master and satellite(s) in the same room, and try my suggestion about the static IPs again, power off, put them in their proper places and power back up.
loomis1975, great suggestions [see #270 in this thread], but that wasn't enough. But it did get me thinking... The satellite had forgotten how to be a satellite, or the router forgot what its satellite looked like. So I did two things: I told the router to "Disconnect" the satellite it wasn't able to find, and I did a full reset (paperclip in recessed hole/button). After that, I introduced them ("Add a Satellite") as if for the first time -- and it worked. Many thanks.
IMPORTANT CLARIFICATION TO MY POST: I did the full reset on the satellite (not the router).