NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR and Sats Disconnect Monthly
RBR 850 and 3 RBS850 V4.6.9.11_2.3.5 Century Link ISP, 1G up and down RBR and sats disconnect monthly, can almost set my watch by it. This has been an issue going back to 2020 and FW: V3.2.16....
Late reply, apologies.
Was running great for over a month using just the router. Plugged in the first of three satellites two weeks ago to test and started having issues today. Answers below in order:
- Yes, default router mode.
- Have never tried restarting only the RBR, have always restarted both. With that, have always had wired connection to ISP device despite no connectivity from the router. Was previously the first thing I would check/ troubleshoot before restarting all.
- Yes, IPV6 is enabled at ISP and router level.
skeelo wrote:
Was running great for over a month using just the router. Plugged in the first of three satellites two weeks ago to test and started having issues today.
Perhaps it would be useful to describe the "issues" in more detail.
- The router says, "no internet"?
- Devices lose connection to the router?
- Devices remain connected to router but claim, "no internet"?
Meanwhile, the ISP router continues on?
I see that new firmware was released for the 850 product on 12/1, V4.6.14.3. Has the system been updated to that version?
Clarity would be helpful indeed!
Issues are spotty/ choppy internet (wired and wirelessly) then no internet at all. ISP goes to router, router goes to unmanaged switch, switch goes to all wired devices. Tested wired connectivity at RBR when having these issues and have similar access - spotty then no access.
ISP (wired) access works without issue - there is no WiFi from ISP (disabled) and RBR is in ISPs DMZ. I did this years ago to eliminate a double NAT when first setting all up.
Running V4.6.9.11_2.3.5 currently and this connectivity issue has persisted since firmware versions got into the 4's. There was a point in time where this was not an issue at all.
skeelo wrote:
Running V4.6.9.11_2.3.5 currently and this connectivity issue has persisted since firmware versions got into the 4's. There was a point in time where this was not an issue at all.
What is it the Brits say, "Bugger All!" (Guess I should look that up to make sure I'm offending - nah.)
Not much to lose then by updating to the latest firmware.
Will give it a shot this weekend.