NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Netgear C6300v2 - Comcast/Xfinity Speed Problems not WiFi
Issue My C6300/AC1750 cable modem/router (Docsis 3.0) is having constant speed problems on Comcast/Xfinity. WiFi is fine on both 2.4 and 5.0GHz. The issue is with the speed as tested by speedtest...
Thanks for the replies. Some were useful, some not. I got a notification that one was accepted as a solution. Not sure how that happens because I didn't do it and it certainly wasn't a "solution". I've called Xfinity and they've agreed to loan me a modem/router free of charge for a few days to test it. I suspect it will work perfectly, but at least I'll be able to compare values of the settings.
vkdelta wrote:Please post your power values and event log.
How often can you see it?
when the speeds are slow, is the wired speeds impacted as well?
I've posted the event log several times, but it keeps disappearing. Does it contain something that shouldn't be posted? I can't imagine what it would be though!
Here is the event log yet again...
Event Log
Clear Log Refresh
Time Priority Description
Mar 02 2020 23:54:16 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Mar 01 2020 22:30:13 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 03:14:37 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 28 2020 03:11:21 Error (4) CheckDmgProvision dmg_provisioning process is not running, need to restart.
Feb 28 2020 01:38:07 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 28 2020 01:36:11 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:36:08 Warning (5) B-INIT-RNG Failure - Retries exceeded
Feb 28 2020 01:34:57 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:34:41 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Feb 28 2020 01:34:40 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:34:39 Warning (5) B-INIT-RNG Failure - Retries exceeded
Feb 28 2020 01:33:36 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:33:20 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Feb 28 2020 01:33:19 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:33:16 Warning (5) B-INIT-RNG Failure - Retries exceeded
Feb 28 2020 01:31:51 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:31:49 Warning (5) B-INIT-RNG Failure - Retries exceeded
Feb 28 2020 01:30:39 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:30:22 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Feb 28 2020 01:30:07 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:30:05 Warning (5) B-INIT-RNG Failure - Retries exceeded
Feb 28 2020 01:29:12 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:29:10 Warning (5) B-INIT-RNG Failure - Retries exceeded
Feb 28 2020 01:27:49 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:27:31 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Feb 28 2020 01:27:30 Warning (5) B-INIT-RNG Failure - Retries exceeded
Feb 28 2020 01:26:04 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:26:02 Warning (5) B-INIT-RNG Failure - Retries exceeded
Feb 28 2020 01:24:57 Critical (3) No Ranging Response received - T3 time-out
Feb 28 2020 01:13:04 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Feb 28 2020 01:12:11 Warning (5) Lost MDD Timeout
Feb 28 2020 01:12:07 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Feb 27 2020 19:57:17 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 26 2020 14:40:05 Critical (3) No Ranging Response received - T3 time-out
Feb 25 2020 09:26:29 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Help CenterShow/Hide Help Center
your RF line has lot of noise or misconfig on the ISP side.
Too many T3 timeouts and also you are getting B-INIT-RNG failure which is bad. That means device is having trouble bonding.
your US power is high as well.
did ISP inspect your line?
vkdelta wrote:your RF line has lot of noise or misconfig on the ISP side.
Too many T3 timeouts and also you are getting B-INIT-RNG failure which is bad. That means device is having trouble bonding.
your US power is high as well.
did ISP inspect your line?
Yes, when I first had the problem right after I got my Netgear modem/router. It worked fine with the Xfinity device. I never really checked the speed because I could stream several devices, download, etc. with no problems and it "seemed" fast.
I"ll have them come back out. I hate Xfinity because they'll charge a service call fee, but they decide that ony after the tech comes out. They couldn't tell me what criteria they use to determine if they charge the fee or not.
