NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
aruit
Dec 11, 2016Guide
Orbi turns Magenta after some days working OK
I have the Orbi system for two weeks and they are working well most of the time.
After installation the Orbi Satellite turned Blue and was working OK for several days.
But suddenly I found the Orbi Satellite turned Magenta.
So I restarted (Power-Off & Power-On) the Orbi Satellite and it turned Blue again.
Again the Satellite was working well for several days, but after a few days it was Magenta again.
Again after restarting the Satellite turned Blue again.
The Orbi Router & Satellite were not moved
So what is causing that a stable connection for days between the Router & Satellite suddenly is broken and after restarting stable again for days?
Hello Darren,
My Netgear Orbi is now running without the solid Magenta light problem, so this problem is really solved with firmware 1.4.0.34.
Thank you for the support,
Anton
20 Replies
hi
possible other wifi interference is causing the orbi to drop , does it not reconnect at all once it goes magenta ?
- aruitGuide
Yes, it reconnects after it goes magenta, so the satellite is functioning OK, but the light stays burning magenta for hours/days.
To switch off the magenta light I have restarted the satellite.
Still some questions:
- How can I find out which other wifi system interference with the connection between the router and the satellite?
- Why is the magenta light not turned off, as soon as the satellite has reconnected to the router?
- How can I turn off the magenta light easy without restarting the satellite?
- DarrenMSr. NETGEAR Moderator
Hello aruit
You may want to move the satellite closer as it could be dropping out because its on the edge of signal but it should shut off after the reconnect but if not the only way to do it is how you are with the reset.DarrenM
- noonwayGuideThat is the exact behavior I am experiencing as well. Should be recreatable on AP mode, Netgear. Please advise if this is a known issue?