NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi 960 Fails to connect and has become unstable
My Orbi AXE11000 has worked fairly well for the past year. It has three satellites in total, however recently it's become extremely unstable. This is $2000 in gear! I'm using what I believe is the la...
I've tried to respond to this several times and the send keeps failing. For starters I'm using firmware version V6.3.7.10_3.3.3 I've made sure that all three satellites have the same firmware version. I reset everything to factory and started over and while all of the satellites are now connected and I seem to have good signal, the router will not connect to the internet. I first attempted to connect directly to Starlink via ethernet cable and I tried two different cables and that didn't work.
I was previously using a PepWave Max Transit Duo modem connected to both Starlink and dual cellular cards and for the past year all was working fine, until in recent days the satellites kept dropping the connection and I couldn't reestablish a connection between my various Mac computers, my iPhone. They couldn't connect to the Orbi satellites no matter what I tried. I could however establish a direct connection to the Starlink, no problem.
I'm in about a 7,000 square foot house in a rural environment, there is no other WiFi interference as there is nobody around. This is an ICF house with a lot of stone. I've continually had good signal throughout the house and this system worked just fine until it started to have these glitches. At the moment, none of the satellites are communicating with the router again and I'm back to square one.
Does the front LED on the RBR turn on PINK when this happens?
If your using Starlink, be sure there services and hardware are working well. There are others in this forum with Starlink and have posted about problems using that ISP.
Be sure your using a good quality LAN cable between the modem and router. CAT6A STP is recommended. There is a difference between STP and UTP cabling.
Also been mentioned that using a non managed GB LAN switch in-between the RBR and Starlink adapter can help as well. There a thread on this here too somewheres.
I would sign up for the Beta FW as well. It's good stuff.
Thanks-
I signed up for the beta, but no response yet. I'm using the same cable since the day I got it. I've tried another cable and there is no difference. I've monitored Starlink's signal and it's fine. I'm using it as I write this. Starlink doesn't seem to be the problem, nor is the PepWave. I've tried connecting both directly to the PepWave and directly to the Starlink and nothing works. There are no settings I can find that would cause this problem. The color of the light is currently magenta.
The satellites are connecting and disconnecting intermittently. This seems like a failing product, which shouldn't happen this new, ever. Again, everything was working just fine for months, and then suddenly it started to have bugs. Lots of bugs where I was frequently having to reboot to get everything to work.
I appreciate the help. I'm highly frustrated by this experience and Netgear hardware.
Tom
Starlink recently did some things from what others have posted about that caused RBRs to not work right with there stuff. No idea what they are doing. There the only ones doing this seems like.
I just took my 960 off line from being online for past month with no issues. Mines on the beta as well. Never saw any issues prior beta either but I don't have SL, cable modem and a CAX30 and CAX80 currently. I feel something is going on with the SL ISP on there side causing a mis-handling of the connection between the RBR and there hardware. I'd give the non-managed switch in between the SL adapter and the RBR a try.
I'll see if we can expedite the beta for you.
Thank you, I appreciate all the help. I don't know why it's suddenly become so unreliable. I've been troubleshooting for six hours now and every time I think I'm making progress, I'm back to square one starting all over again.