Orbi RBS 50 satellite will not stay connected to router, even when in the same room.

So far, I've had a terrible experience with this product.  To start, the remote device is RARELY connected, and when it is I don't think it's switching my devices.

Also, because I had to factory reset the device 5 times to finally see the remote, I had to frequesnty go back to factory SSID then change it back to what I wanted.  This last time I reset the SSID, the unexplainable started happening.  I had to reset the network setting on my android, I had re-enter the password even when hte SSID was the precise same name.  I had two Known Networks in my system with the exact same same (Windows 10).  I've never seen this behavior before.

My Nest won't connect.  The signal is bouncy as heck, It's just awful.

netgear - Seriously, what is going on with this?  I've seen lots of forumes with this exact same problem.  I saw somewhere on your forum, a Netgear employee state to "give it 10-15 minutes".  This is unacceptable, and your technician was called out on it.  There was no reply or edit to the post.

You're hte most expensive home Mesh system by a decent amount.

Qualifications: Own and operate an IT consulting firm who services some of the largest enterprise networks in the country.

---

GaryInEdmond wrote:

I was having the same issue with the new firmware update.

The problem turned out to be that the router had updated to the new firmware (V1.12.0.18) but the satellite had not.

I had to log directly into the satellite and update to the new firmware manually and everything worked fine after that.

The login to the satellite will be something like 192.168.1.5 with the last number being variable.  Mine has changed back and forth between 5 and 6 so I knew to use that number but it will very possibly be different in your situation.

 

When I had manually updated my satellites firmware, it went back to working flawlessly.  I wouldn't hesitate to call tech support if you have trouble updating your satellite.  I've had my orbi since they first came out and this is the first time the automatic update had problems.

---

See, I have done that already.  Updating firmware is ALWAYS the first thing I do.

I updated the router to 1.12.0.18.  The satellite wouldn't reconnect.  I downgraded the router back to the original firmware because I couldn't see the remote - it wasn't synced so it wasn't on the network.  I scanned the heck out of my network for it.

After downgrading, the remote came back online.  I upgraded the remote first, then the router.  Everything got screwed up again.  I flashed back to facory, firmware remained at the latest release.  Everything connected after about 4 hours.

Then I rebooted the router, last night in fact.  STILL hasn't reconnected.  I tried hitting the sync button on both devices - nothing.  Close, somewhat close, far away - doesn't matter.  It will NOT connect to the remote.

Honestly, there are way too many posts about the same issue, without solutions from NetgearSupport_. 

GaryInEdmond - I know it worked for you, and I'm stoked for you.  But too many of us are having the same issue.  And tier 1 is going to annoy the bejesus out of me before they will even consider sending me to 2 or 3.  At the risk of sounding braggish, I am a highly skilled network engineer.  I know what is going on with this, and I've even run my scan tools on the remote and the base.  I see the signals, I see the packets coming across, and quite frankly the multicast solution being used to synchronize these devices is a bad decision on Netgear's part.  There are like, 1000 ways to do it better.

I did buy this to test for some of my smaller clients.  I have my answer.

~Nick

I went through the same process with support to back up to the older version.  Still doesn’t work!

---

DarrenM wrote:

Hello everyone

 

Sometimes with the latest firmware you may need to factory reset the satellite and then bring them close to the main router and resync them then put them back in the area you need the coverage.

 

DarrenM

---

Darren - Thank you for your reply.  This procedure does not work.  I did this procedure about 15 times (not kidding).  Every time power was lost to either the router or the satellite, they will NOT reconnect.  And mind you I gave it overnight opportunities to reconnect.

The reality is, this product is not ready for production.  I have returned mine and went with another solution that had me up and running in less than 10 minutes - from taking the plastic off the box, to fully configured and placed satellites.  I spent 5 days (even took a day off work!) to try to make it happen with the Orbi. 

I'll be kind and not share my new solution on your message boards - that's a bit unfair.  But I will say, it took a long time to get a reply on this thread from someone at Netgear, and the other threads are still open with no solution as I expect this one to be.

It's not the users this time, guys.  I'm an IT consultant - I understand user error.  This is NOT the case here.  I build wireless networks for colleges and areanas and other large scale deployments.  I was really hoping to have a great solution for my smaller clients with this, but it's just not ready for that.  Anything more than 5 minutes to reconnect remotes is unacceptable.

Happy to help you solve the problem if you want, just reach out and let me know how I can help you fix this issue.  But development will need to be involved.

Edit: Please forgive my spelling.  I fix computers, definitely not an english major.  :)

~Nick from Matchless IT

Any progress on this issue ? 

Do you still need help ? 

I’ve already worked with support for hours and no resolution.  I can’t afford to deal with a non working system for my business, so had to go another direction.

How do we get compensated for a system that no longer works and is past return policy?