NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
LanceBurbank
Dec 22, 2021Aspirant
RAX35v2 is not allowing Dropbox to sync
I have an RAX35v2 router. Originally Dropbox worked fine with it, but now the router appears to be blocking Dropbox syncing. Sync works fine when I use another router so I'm ruling out the Mac OS or my security software. Also ... when I switch between my 2G and 5G networks sync will start working again (sometimes), only to stall again after the first sync.
I'm now thinking that the router is assuming Dropbox syncs are DoS attacks but I don't know how to fix this without disabling DoS protection entirely, which I don't want to do.
Looking for any help I can get because I'm get tired of bouncing between my 2G and 5G networks waiting for Dropbox sync to get unblocked.
Seen odd things with Monterey. I'd contact Apple and let them know what your seeing betwee your two Macs. I've filed s few items against OSX 12 since beta started. They fixed most of them. One of them was Monterey would crash if I connected to my NAS via SMB. Another was scrolling with mouse in text exit would cause the app to hang.
11 Replies
Sort By
What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?Is Smart Connect, Beamforming and MIMO and WMM Enabled on the router?
- LanceBurbankAspirant
Thanks for the reply. I really appreciate it.
Firmware = V1.0.4.100_2.0.64
Smart Connect = NOT enabled
Beamforming = Enabled (5g)
MIMO = NOT enabled
WMM = Enabled
Same thing happens if Smart Connect is enabled?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
- LanceBurbankAspirant
Sorry, forgot to respond re the modem. Unfortunately, I don't see any name/model info on it. It's just labeled Spectrum.
Taking a look on the Spectrum website, looks like a Spectrum D3.1 eMTA DOCSIS 3.1 Advanced Voice Modem.
Thanks again.
- LanceBurbankAspirant
So the issue seems to have resolved itself today. Or ... more likely, some application that had caused a conflict was updated. Who knows?