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.
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?
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?
All speeds are impacted--wired and WiFi. I'm having problems posting the logs. Will post later.
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 393000000 Hz Locked
Connectivity State Ok Operational
Boot State Ok Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables UnCorrectables
1 Locked QAM 256 1 297000000 Hz -2.2 dBmV 38.9 dB 441 0
2 Locked QAM 256 2 303000000 Hz -2.7 dBmV 40.3 dB 414 0
3 Locked QAM 256 3 309000000 Hz -2.9 dBmV 40.3 dB 484 0
4 Locked QAM 256 4 315000000 Hz -2.9 dBmV 40.3 dB 451 0
5 Locked QAM 256 5 321000000 Hz -2.7 dBmV 40.3 dB 487 0
6 Locked QAM 256 6 327000000 Hz -2.5 dBmV 40.3 dB 450 0
7 Locked QAM 256 7 333000000 Hz -2.5 dBmV 40.3 dB 468 0
8 Locked QAM 256 8 339000000 Hz -2.5 dBmV 40.9 dB 553 0
9 Locked QAM 256 9 345000000 Hz -2.4 dBmV 40.3 dB 489 0
10 Locked QAM 256 10 351000000 Hz -2.2 dBmV 40.3 dB 559 0
11 Locked QAM 256 11 357000000 Hz -2.2 dBmV 40.3 dB 562 0
12 Locked QAM 256 12 363000000 Hz -2.7 dBmV 40.3 dB 600 0
13 Locked QAM 256 13 369000000 Hz -3.0 dBmV 40.3 dB 571 0
14 Locked QAM 256 14 375000000 Hz -3.2 dBmV 38.9 dB 593 0
15 Locked QAM 256 15 387000000 Hz -3.5 dBmV 40.3 dB 643 0
16 Locked QAM 256 16 393000000 Hz -3.7 dBmV 40.3 dB 658 0
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 4 5120 Ksym/sec 16600000 Hz 49.5 dBmV
2 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 49.5 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 49.5 dBmV
4 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 49.5 dBmV
Current System Time: Thu Mar 5 10:32:33 2020
System Up Time: 21:04:47
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 Centeryour 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?