NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Xr700 disconnects
Cm1000 modem, xr700 router, to Xbox. Using vandesail cat 8 Ethernet. 500 mb down 30 mb up speeds on cable internet. Usually get 600-660 down an 32-40 up. Xbox shows 60-74 latency. Was playing last night and router lost signal from modem. Pulled up dumbos on laptop and verified. Tried different cable. Cycled modem. Rebooted router and nothing worked. Router felt warm. About as warm as my arris sb8200 modem I have on a different ip. The fan on this was not turning. Is it thermally controlled or does it run constant? Hooked up my wrt32x router and had connection again. Let the xr700 sit until next day hooked it up and it connected. Firmware was already updated before this happened. I had no internet connection to any devices wired or wireless
took out the firmware anbd reloaded it have not had an issue since then. did my best mtu setting had fragmented files after 1400 mtu doing the run-cmd- ping yahoo.com -f -l 1400. then did the +20+8 for a 1428 mtu. after 1400 mtu had framented which sucks; but that is on my isp. Thank you for the fan threshold info did not know about it. set it up where it kicks on here and there. just so it does not sit idle. it does work. BO4 hit detection is still off. been playing with the anti buffer bloat 70% - 40% no difference). have geo at 600 mile from me with 15-33 ping. dsl tests are A with bufferbloat. Have dove dumaos games checked and unchecked. qos to xbox is 70% down and up. upgraded cat cable to cat8 26 awg.
21 Replies
Try a full factory reset on the XR router and setup from scratch. Walk thru the setup wizard while connected to the CM modem.
Try the XR router with the SB modem...same thing happen there?
I have not had any drops or disconnects doing a Hardware Reset might resolve the issue.
You could also check your modems dBmV levels they should be within -7 to +7.
Btw: you can modify the fan settings. http://routerlogin.net/debug.htm
T(High-H) - This means that when the temperature reaches this thresh hold the fan will kick in at at faster speed 4000rpm
T(High-L) - This means that when the temperature reaches this thresh hold the fan will kick in at at faster speed 3500rpm
T(Low-H) - This means that when the temperature reaches this thresh hold the fan will kick in at at faster speed 3000rpm
T(Low-L) - This means that when the temperature reaches this lower thresh hold the fan will kick in on the lowest speed 2000rpm
Note: My fan settings are set to always On full because I like to keep it cool and if the fan dies I can always open it up and replace it.If this continues, definitely get in touch with official NETGEAR support as you might have a hardware problem: https://www.netgear.com/support/contact.aspx
Gamer_0224 Are you sure that these drops are not occuring due to issues with the Arris SB8200 Cable Modem? Can you post a screenshot of the status and the event log page of your Arris SB8200 so we can see if there is any issues with upstream or downstream signal or issues in the event logs.
Fan won't be turn on until hitting the turn-on threshold. You can enforce to turn it on via a hidden page.
took out the firmware anbd reloaded it have not had an issue since then. did my best mtu setting had fragmented files after 1400 mtu doing the run-cmd- ping yahoo.com -f -l 1400. then did the +20+8 for a 1428 mtu. after 1400 mtu had framented which sucks; but that is on my isp. Thank you for the fan threshold info did not know about it. set it up where it kicks on here and there. just so it does not sit idle. it does work. BO4 hit detection is still off. been playing with the anti buffer bloat 70% - 40% no difference). have geo at 600 mile from me with 15-33 ping. dsl tests are A with bufferbloat. Have dove dumaos games checked and unchecked. qos to xbox is 70% down and up. upgraded cat cable to cat8 26 awg.
My router was crashing every 30 minutes on 1.0.1.2. I had to downgrade to 1.0.0.20 to get the router stable. Hoping this issue is resolved with the release of 1.3
I never factory reset. I upgraded back to 1.0.1.2 to make sure it was the firmware. Should I factory reset on 1.0.1.2?
