Community Forum

SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Highlighted
Frequent Visitor

SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

OK,  I have many tech vist come out and they all say it's my equipment which doesn't make sense because there are others with this same issue as me. It seems that the techs are able to get a with their xm1 meter but I can't get passed300-400 with my computer. I noticed that my upload speed is fine it seems that my download speed is the one that is the problem  I have a consistent 40 upload but download speed that's all over the place please help 

 

I am paying for a gig  ($100/ month)

only getting 300-400 which is way under the advertised min amount I should be getting

this is a speed test with me wired directly into the modem by the way

 -------------------------------------------------------------------------------------------------------------------------

My setup is over $3000 all brand new 

2MSI GP72  LEOPARD-LAPTOP (I can reach a gig on this laptop at my friends house just not at mine)

MSI CUSTOM BUILT DESKTOP (ALSO CAN REACH A GIG I HAVE TESTED THIS AT MY BROTHERS)

NETGEAR-CM100V2 MODEM(  HAS ERRORS ON IT )

NETGEAR-NIGHTHAWKR6700

-----------------------------------------------------------------------------------------------------------------------------------------

 

Below are the error logs on my modem

TimePriorityDescription
2020-10-07, 16:22:43Warning (5)Dynamic Range Window violation
2020-10-07, 16:22:43Warning (5)RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-07, 16:22:43Warning (5)Dynamic Range Window violation
2020-10-07, 16:22:43Warning (5)RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-07, 16:22:38Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:05:30Critical (3)SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:05:17Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:05:02Critical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:04:58Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:04:58Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 12:28:40Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 11:05:07Critical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 11:05:02Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 11:04:55Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-09-30, 10:11:38Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-09-29, 05:53:02Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-09-22, 15:47:21Critical (3)Resetting the cable modem due to docsDevResetNow
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

 

 

Here are my power levels from the modem

ProcedureStatusComment
Acquire Downstream Channel693000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnableBPI+
IP Provisioning ModeHonor MDDIPv6 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
ChannelLock StatusModulationChannel IDFrequencyPowerSNR / MERUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1LockedQAM25641693000000 Hz1.6 dBmV39.5 dB37665077258650
2LockedQAM25613525000000 Hz2.3 dBmV41.1 dB3765367389960
3LockedQAM25614531000000 Hz2.1 dBmV39.2 dB37653751531230
4LockedQAM25615537000000 Hz2.0 dBmV40.6 dB37653781831400
5LockedQAM25616543000000 Hz1.8 dBmV40.8 dB37653766911290
6LockedQAM25617549000000 Hz1.7 dBmV40.7 dB37653847781300
7LockedQAM25618555000000 Hz1.9 dBmV40.7 dB37653904901430
8LockedQAM25619561000000 Hz2.0 dBmV40.9 dB37653915921330
9LockedQAM25620567000000 Hz2.0 dBmV40.8 dB37654202141730
10LockedQAM25621573000000 Hz1.9 dBmV40.7 dB37654290951930
11LockedQAM25622579000000 Hz1.7 dBmV40.7 dB37654316852070
12LockedQAM25623585000000 Hz1.5 dBmV40.4 dB37654352352320
13LockedQAM25624591000000 Hz1.4 dBmV40.0 dB37654399872470
14LockedQAM25625597000000 Hz1.5 dBmV40.4 dB37654418902690
15LockedQAM25626603000000 Hz1.5 dBmV40.3 dB37654466543110
16LockedQAM25627609000000 Hz1.7 dBmV40.4 dB37654489932920
17LockedQAM25628615000000 Hz2.0 dBmV40.3 dB37654853713420
18LockedQAM25629621000000 Hz2.2 dBmV38.1 dB37654858843810
19LockedQAM25630627000000 Hz2.4 dBmV39.0 dB37654906035210
20LockedQAM25631633000000 Hz2.4 dBmV39.0 dB37654970434420
21LockedQAM25632639000000 Hz2.3 dBmV40.1 dB37654972635300
22LockedQAM25633645000000 Hz1.9 dBmV40.0 dB37655023065960
23LockedQAM25634651000000 Hz1.5 dBmV39.8 dB37655092707330
24LockedQAM25635657000000 Hz0.9 dBmV39.5 dB37655082628940
25LockedQAM25636663000000 Hz0.4 dBmV39.4 dB376551428510980
26LockedQAM25637669000000 Hz0.5 dBmV39.4 dB37655184459680
27LockedQAM25638675000000 Hz0.8 dBmV39.4 dB376552667210210
28LockedQAM25639681000000 Hz1.1 dBmV39.6 dB37655324219010
29LockedQAM25640687000000 Hz1.7 dBmV39.6 dB37655327999350
30LockedQAM25642699000000 Hz1.6 dBmV39.5 dB376553867911470
31LockedQAM25643705000000 Hz1.7 dBmV39.3 dB376553822014380
32LockedQAM25644711000000 Hz1.5 dBmV39.2 dB376553495513120

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
ChannelLock StatusModulationChannel IDFrequencyPower
1LockedATDMA535600000 Hz42.0 dBmV
2LockedATDMA629200000 Hz43.0 dBmV
3LockedATDMA722800000 Hz42.0 dBmV
4LockedATDMA816400000 Hz43.0 dBmV
5Not LockedUnknown00 Hz0.0 dBmV
6Not LockedUnknown00 Hz0.0 dBmV
7Not LockedUnknown00 Hz0.0 dBmV
8Not LockedUnknown00 Hz0.0 dBmV

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPowerSNR / MERActive Subcarrier Number RangeUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1Locked0, 1159762000000 Hz1.4 dBmV37.5 dB1126 ~ 29697041199675191281260
2Not Locked000 Hz3.8 dBmV0.0 dB0 ~ 4095000

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
1Not LockedUnknown00 Hz0 dBmV
2Not LockedUnknown00 Hz0 dBmV

 

I am posting here because the techs are clueless  when they come here they just  test the wall and leave  I really need help I am tired of overpaying

please help

 

Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Wow that is a lot of errors! I would schedule another appointment for a tech to come out. Ask them if they can run a QAM test, check the line to and into your house as well as all neighboring lines at the tap (where your line hooks up to).

I’m not sure if it’s possible and might be a long process but if you can bring your Modem and router to your friends house and test your equipment there. If you’re having issues with your modem and router still at their house it could be faulty .
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

  I swear these tech  are lazy  so they get pull 1000/40 and I cant get nothing and I have also taken this modem to my brothers hose and used it works just fine but they dont belive that just say its your  problem  and walk out

Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Its not the modem our router both hit 1000mbs easy  at my brother's house there is something wrong with here at my house but they say since they can get the speeds on their testing meeter its fine it's my devices which isn't the case because When i use my modem by his house no errors  when its on his account when its on mine a errors slow speeds i even bought another modem and router just to make sure  I bought the night hawk 1900 and another cm 1000v2

same probelm so I am stuck with its my equiment 

Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

I’d have them come back out and check QAM at the tap, the lines coming to and into your house as well as neighboring lines. The errors weren’t constant. Try to take notice if it’s intermittent too!

I appreciate it. The second part that you said answered my previous question about that exact modem on someone else’s account.
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

They run the test and say everything looks fine on their part  but I will try does  the signals look ok  to you what is causing the  errors do yout think

Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

It could be a bad/loose fitting, small cuts or old coax lines, Lines that aren’t being used but are still attached to your splitters. Also if your neighbors have bad lines and are attached to the tap, it could possibly affect you as well.

Upstream and downstream on the log is perfect there are a lot of QAM errors and I’d have them run a QAM analysis test on that cable line and at the tap.

Is it every time you run the test? Also If you can make sure all of your equipment has the latest firmware installed. I’m pretty sure that doesn’t cause t3 timeouts but rather be safe than sorry.
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

How are they able to pull a gig and I am not is my question  off the modem

 

also I have had the Comcast modem and had the same error also on the  xb7  as well

Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

If they plugged in Ethernet from their meter to the modem and tested gig fine it could be an intermittent issue. Try to pull the log and take notice if it’s around certain timeframes.

Try these things and let me know what’s coming up.

1. Check for any VPN or firewalls that can lower speeds at the time of the test.

2. With Ethernet Run the speed test directly from the CM1000v2 and not the R6700

3. If you can; run the test speed test through wifi on your smartphone right next to the R6700 one on 2.4 then one on 5G .

Keep in this in mind. IPhone 8 Plus, galaxy S5 and most google pixel models can only handle around 850mbs through 5G.

Let me know how you make out. I still would recommend that you have another tech come out and test the QAM and different lines though
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

No vpn or firewalls tried multiple computers all stuck at 300 mbs  tried differnt modems same resualt

Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Both are getting stuck on 2.4 and 5g?
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

hardwired not wifi

Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

  Your downstream is not the problem.

 

  The problem is that your upstream power cannot exceed 43dbMV because you have 8 bonded channels and Comcast has DISABLED the extended upstream power facility of your modem.

 

  The reason the tech has no problem is because his tester doesn't respect power levels based upon bonded channels.  Your modem is obligated to respect them because Comcast has configured it that way.

 

  Basically, the CMTS is ordering your modem to increase its power and it cannot do it because Comcast has disabled Extended Upstream power  and the modem has to reduce power because of the number of upstream channels you have.

 

  Normally a single upstream channel can be transmitted at 55dBmV.   Two bonded channels can use a maximum of 52dBmV.   4 bonded channels have a maximum of 49dBmV and based upon your system, it seems that 8 bonded channels have a maximum of 43dBmV.

 

  If Comcast refuses to fix this, I suggest you switch your plan AWAY from Gigabit to a lower tier which only uses 4 bonded channels (a plan with a maximum of 10M upstream speed).  This will reduce your upstream channels from 8 to 4, thus allowing your modem an extra 6dBmV of power to transmit data.

 

It might not fix everything, but it will definitely be better than what you have.

 

  Oh... and what they actually should be doing is testing the attenuation between your modem and the CMTS.    It seems obvious that there is way too much signal attenuation between the two.

Highlighted
Expert

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!


@Netgearhead wrote:

  Your downstream is not the problem.

 

  The problem is that your upstream power cannot exceed 43dbMV because you have 8 bonded channels

 

FWIW, that's incorrect. There are only 4 bonded upstreams. The upstream power is fine / well within spec.

 

The reason the tech has no problem is because his tester doesn't respect power levels based upon bonded channels.  Your modem is obligated to respect them because Comcast has configured it that way.

 

Incorrect.

 

  Basically, the CMTS is ordering your modem to increase its power and it cannot do it because Comcast has disabled Extended Upstream power  and the modem has to reduce power because of the number of upstream channels you have.

 

Yes, they may have disabled the extended upstream power level feature but the CMTS still commands what the upstream power level will be.

 

  Normally a single upstream channel can be transmitted at 55dBmV.   Two bonded channels can use a maximum of 52dBmV.   4 bonded channels have a maximum of 49dBmV and based upon your system, it seems that 8 bonded channels have a maximum of 43dBmV.

 

They only offer 4 or 5 upstreams. The others show as "not locked".

 

  If Comcast refuses to fix this, I suggest you switch your plan AWAY from Gigabit to a lower tier which only uses 4 bonded channels (a plan with a maximum of 10M upstream speed).  This will reduce your upstream channels from 8 to 4, thus allowing your modem an extra 6dBmV of power to transmit data.

 

Incorrect.

 

  Oh... and what they actually should be doing is testing the attenuation between your modem and the CMTS.    It seems obvious that there is way too much signal attenuation between the two.

 

The numbers do not indicate excessive attenuation.


 



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

@Netgearhead wrote:

  Your downstream is not the problem.

 

  The problem is that your upstream power cannot exceed 43dbMV because you have 8 bonded channels

 

FWIW, that's incorrect. There are only 4 bonded upstreams. The upstream power is fine / well within spec.

 

My bad, for some reason channels 1 to 4 are labelled 5 to 8 and I mixed that up.

 

The reason the tech has no problem is because his tester doesn't respect power levels based upon bonded channels.  Your modem is obligated to respect them because Comcast has configured it that way.

 

Incorrect.

No.   Correct.    Comcast disabled extended upstream power with a firmware push earlier this year.

 

  Basically, the CMTS is ordering your modem to increase its power and it cannot do it because Comcast has disabled Extended Upstream power  and the modem has to reduce power because of the number of upstream channels you have.

 

Yes, they may have disabled the extended upstream power level feature but the CMTS still commands what the upstream power level will be.

Yes and the modem is REJECTING that command because it's exceeding the dynamic ranging window.  That's what this error in the log means:

"RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW".

 

  Normally a single upstream channel can be transmitted at 55dBmV.   Two bonded channels can use a maximum of 52dBmV.   4 bonded channels have a maximum of 49dBmV and based upon your system, it seems that 8 bonded channels have a maximum of 43dBmV.

 

They only offer 4 or 5 upstreams. The others show as "not locked".

Yes, I did make a mess of that.   However the 49dBmV limit for 4 bonded channels is correct.

 

  Oh... and what they actually should be doing is testing the attenuation between your modem and the CMTS.    It seems obvious that there is way too much signal attenuation between the two.

 

The numbers do not indicate excessive attenuation.

They might not, but the CMTS telling the modem to increase power beyond limits does.  Any time the modem complains about an excessive power request from the CCAP, it means the hub site wants increased signal and the modem is complaining it can't do it.

 

When extended upstream power was available, the modem had an extra 6dBmV to play with.  Now that it doesn't, upstream signal quality issues are everywhere.  You can see this error all over these forums.

Highlighted
Expert

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!


@Netgearhead wrote:

 

 

The reason the tech has no problem is because his tester doesn't respect power levels based upon bonded channels.  Your modem is obligated to respect them because Comcast has configured it that way.

 

Incorrect.

 

No.   Correct.    Comcast disabled extended upstream power with a firmware push earlier this year.

 

I'm not disputing that part of your comment.

 

  Basically, the CMTS is ordering your modem to increase its power and it cannot do it because Comcast has disabled Extended Upstream power  and the modem has to reduce power because of the number of upstream channels you have.

 

Yes, they may have disabled the extended upstream power level feature but the CMTS still commands what the upstream power level will be.

 

Yes and the modem is REJECTING that command because it's exceeding the dynamic ranging window.  That's what this error in the log means:

"RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW".

 

That's not what that means, sorry.

 

  Normally a single upstream channel can be transmitted at 55dBmV.   Two bonded channels can use a maximum of 52dBmV.   4 bonded channels have a maximum of 49dBmV and based upon your system, it seems that 8 bonded channels have a maximum of 43dBmV.

 

They only offer 4 or 5 upstreams. The others show as "not locked".

 

Yes, I did make a mess of that.   However the 49dBmV limit for 4 bonded channels is correct.

It depends on the QAM of the carrier.

 

Oh... and what they actually should be doing is testing the attenuation between your modem and the CMTS.    It seems obvious that there is way too much signal attenuation between the two.

 

The numbers do not indicate excessive attenuation.

They might not, but the CMTS telling the modem to increase power beyond limits does.  Any time the modem complains about an excessive power request from the CCAP, it means the hub site wants increased signal and the modem is complaining it can't do it.

 

When extended upstream power was available, the modem had an extra 6dBmV to play with.  Now that it doesn't, upstream signal quality issues are everywhere.  You can see this error all over these forums.

 

Please do some research.


 



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Honestly thank you guys for all this help because the tech that comes out here don't do anything at all but just use a meeter and say its your problem and you need our modem

 

Just for clarification what should I ask them to do when they come out next time

 

Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Before you call just make sure you have the latest firmware installed and there are no updates available. Try to run a speed test only through wifi right next to it too. One on 2.4 and a separate test on 5g.


When you call into customer support ask them if they can check if you have the correct boot file for gig speed.

When the techs arrive. Let them know there has been multiple T3 timeouts and if they can to check neighboring lines and all lines going into your house for ingress. If the tech has a XM2 meter ask them do the speed test via Ethernet (They’ll only get what your modem is currently pushing out.) Lastly I would ask them to test QAM analysis at the tap and at your modem.

No problem fingers crossed!!!
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

I have another question I have. They have tested from the wall using my modem and with my router and still had the same issue whith my download speed not reaching the right speed  is there away  I can convince them to actaully test because I would like to stay on the gig plan

Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

 They have tested from the modem and gotten full speed   but I believe someone said on here the meter  doesn't  help this

Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

I have a time for them to come and check next week on the 19th of oct

 

I have I would like a list of things they need to check for so far I have a QAM test

but what else should I ask them to check for because it seems from what I have read it doesn't matter if they connect into my modem or not they will get the speeds  because the xm1 meeters done respect power levels  and my modem doese 

 

so in this case what should I do

 

 

 

Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Here is the most recent error log for you guys to look at

 

 

2020-10-15, 18:16:10Warning (5)REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-15, 18:16:06Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-10-15, 18:15:01Critical (3)Resetting the cable modem due to docsDevResetNow
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 23:27:48Critical (3)Resetting the cable modem due to docsDevResetNow
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:21:45Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:21:41Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:21:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:21:20Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:21:02Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:21:01Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:20:41Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:20:40Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:20:09Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:20:03Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 22:19:59Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-14, 09:50:33Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:05:30Critical (3)SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:05:17Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:05:02Critical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:04:58Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 13:04:58Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 12:28:40Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 11:05:07Critical (3)No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 11:05:02Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
2020-10-01, 11:04:55Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=44:a5:6e:b4:20:50;CMTS-MAC=80:e0:1d:03:0b:22;CM-QOS=1.1;CM-VER=3.1;
 
 

 

Power levels :
 
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency

<tabindex=-1>Startup Procedure</tabindex=-1>
ProcedureStatusComment
Acquire Downstream Channel693000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnableBPI+
IP Provisioning ModeHonor MDDIPv6 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
ChannelLock StatusModulationChannel IDFrequencyPowerSNR / MERUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1LockedQAM25641693000000 Hz1.3 dBmV39.8 dB410489805680
2LockedQAM25613525000000 Hz2.4 dBmV41.3 dB40944156160
3LockedQAM25614531000000 Hz2.1 dBmV37.4 dB40944554460
4LockedQAM25615537000000 Hz2.1 dBmV40.7 dB409448897100
5LockedQAM25616543000000 Hz1.8 dBmV41.1 dB409452314110
6LockedQAM25617549000000 Hz1.7 dBmV41.0 dB40945597090
7LockedQAM25618555000000 Hz1.8 dBmV40.9 dB40946000370
8LockedQAM25619561000000 Hz1.9 dBmV41.0 dB409463500100
9LockedQAM25620567000000 Hz1.8 dBmV40.9 dB409470672150
10LockedQAM25621573000000 Hz1.7 dBmV40.9 dB409474894150
11LockedQAM25622579000000 Hz1.6 dBmV40.8 dB409478238130
12LockedQAM25623585000000 Hz1.3 dBmV40.6 dB409481845160
13LockedQAM25624591000000 Hz1.2 dBmV40.5 dB409485930190
14LockedQAM25625597000000 Hz1.3 dBmV40.4 dB409489420140
15LockedQAM25626603000000 Hz1.3 dBmV40.6 dB409492925230
16LockedQAM25627609000000 Hz1.5 dBmV40.5 dB409496874220
17LockedQAM25628615000000 Hz1.8 dBmV40.6 dB409502923220
18LockedQAM25629621000000 Hz2.0 dBmV38.9 dB409506772230
19LockedQAM25630627000000 Hz2.2 dBmV38.4 dB409510723370
20LockedQAM25631633000000 Hz2.1 dBmV40.2 dB409514689340
21LockedQAM25632639000000 Hz2.0 dBmV40.3 dB409518350330
22LockedQAM25633645000000 Hz1.7 dBmV40.2 dB409521464360
23LockedQAM25634651000000 Hz1.2 dBmV39.7 dB409526970540
24LockedQAM25635657000000 Hz0.6 dBmV39.7 dB409530018640
25LockedQAM25636663000000 Hz0.1 dBmV39.5 dB409533904690
26LockedQAM25637669000000 Hz0.2 dBmV39.5 dB409537364470
27LockedQAM25638675000000 Hz0.5 dBmV38.8 dB409541307680
28LockedQAM25639681000000 Hz0.8 dBmV39.6 dB409544647640
29LockedQAM25640687000000 Hz1.3 dBmV39.9 dB409548740580
30LockedQAM25642699000000 Hz1.3 dBmV39.7 dB409552686710
31LockedQAM25643705000000 Hz1.3 dBmV39.4 dB409555450960
32LockedQAM25644711000000 Hz1.2 dBmV39.4 dB409555448880

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
ChannelLock StatusModulationChannel IDFrequencyPower
1LockedATDMA535600000 Hz41.8 dBmV
2LockedATDMA629200000 Hz42.8 dBmV
3LockedATDMA722800000 Hz41.8 dBmV
4LockedATDMA816400000 Hz42.8 dBmV
5Not LockedUnknown00 Hz0.0 dBmV
6Not LockedUnknown00 Hz0.0 dBmV
7Not LockedUnknown00 Hz0.0 dBmV
8Not LockedUnknown00 Hz0.0 dBmV

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPowerSNR / MERActive Subcarrier Number RangeUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1Locked0, 1159762000000 Hz1.1 dBmV37.0 dB1126 ~ 296936133069221223250
2Not Locked000 Hz3.9 dBmV0.0 dB0 ~ 4095000

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
1Not LockedUnknown00 Hz0 dBmV
2Not LockedUnknown00 Hz0 dBmV
 
Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Ask them to test the lines from the tap to your house. The upstream snr has dropped below 31 intermittently and has had around 2000 uncorrectable errors each day. For customer service ask them to make sure they have the correct firmware for CM1000V2.

A couple things I would try out on your end before the 19th is to check all the settings on the modems website and search what they mean just Incase you have to switch some settings up.

Out of curiosity Is the wifi giving you higher speeds on 5g compared to the Ethernet speed test?

Fingers crossed!
Highlighted
Expert

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

FWIW, the stats are o/k. The "upstream SNR" can not be read by the modem.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!


@The94DelSol wrote:
Before you call just make sure you have the latest firmware installed and there are no updates available. Try to run a speed test only through wifi right next to it too. One on 2.4 and a separate test on 5g.


When you call into customer support ask them if they can check if you have the correct boot file for gig speed.

When the techs arrive. Let them know there has been multiple T3 timeouts and if they can to check neighboring lines and all lines going into your house for ingress. If the tech has a XM2 meter ask them do the speed test via Ethernet (They’ll only get what your modem is currently pushing out.) Lastly I would ask them to test QAM analysis at the tap and at your modem.

No problem fingers crossed!!!

I am only getting 155.9 download  and 12.8 upload on 5g  I went out and bought new modem today and router just befor doing this test   that test was the highest I have gotten on the mobile phone I have I have a note 10+    wich I am sure I should get more than that cause I have seen a video of someone getting 600mbs on this phone

Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

This morning I dug more into it. It’s not the modem or router. I was just trying to make sure they had the correct firmware on it and all settings were correct. Ask the tech to check the lines. after they’re done doing what they have to do; Ask them to check scout. They should be able to see the upstream SNR and uncorrectable upstream errors that’s been going on.
Highlighted
Expert

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Ok well you asserted this;

 

"The upstream snr has dropped below 31 intermittently and has had around 2000 uncorrectable errors each day."

 

Scout is a dinosaur..

 

 



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

I just felt bad that they went out and bought a new one. I don’t want them to waste their time so I tried to reinforce what seems to be the issue. The line to the modem had a spike in noise as well. Thats why I was pushing the fact 😞
Highlighted
Expert

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Fact ? Again, how could you know what their upstream SNR is / did ?



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

I’m a tech just trying to help out in my spare time 🙂
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

well my new modem and new  router didnt help out any my brother brought his pc which hits a gig over just to test and see if it was my pc which I highly doubt it because I can hit a gig at his house when we play games over there  but he was getting max 400mbs this is actually crazy he also has comcast with my same modem the netgear cm1000 and a nighthawk . So I am sure something is wrong on comcasts side I will honestly flip if they say I need an xb7 or its my equiment  on the 19th

Highlighted
Contributor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

Good morning Kim,
I understand It’s a frustrating situation. Like I was saying; the other day I looked more into it. Let the techs do their tests but if you can make sure that they start from the line connected to the tap.

I can’t stress enough how important it is that they check the lines for ingress. Let me know how it goes 🙂
Highlighted
Frequent Visitor

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!


@EG wrote:

  Basically, the CMTS is ordering your modem to increase its power and it cannot do it because Comcast has disabled Extended Upstream power  and the modem has to reduce power because of the number of upstream channels you have.

 

Yes, they may have disabled the extended upstream power level feature but the CMTS still commands what the upstream power level will be.

 

Yes and the modem is REJECTING that command because it's exceeding the dynamic ranging window.  That's what this error in the log means:

"RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW".

 

That's not what that means, sorry.

 

Okay, if you want to be pedantic.    What it means is that the CMTS has commanded a power increase which causes at least one of the upstream channels to fall outside the 12dB range of the dynamic ranging window.  This could be a decrease, but it's mostly likely to be an increase.  And it could be just one channel, but it's more likely to be all of them.

 

On its own, it's not usually a problem unless your upstream levels are already flirting with the upper bound of upstream power levels.   Which is applicable in my case and probably within his case.  We don't know what levels are triggering the issue since the modem doesn't report them at the time.

 

 

 

 

Please do some research.

 

How patronizing.

 

Anyway, back to the problem.  T3 timeouts are indicative of upstream comms issues.  They represent 16 attempts by the modem to get a response to a ranging request.  Given the modem cannot even initiate that dialogue without matching sync with the CMTS (IE:  It has to be able to hear before it can speak), it seems obvious that during these issues, the CMTS is not "hearing" the modem.

 

Also, it's important to understand the power levels the modem reports are not updated in real time.  They're a snapshot representing the levels at a particular point in time.  Probably the most recently successfully negotiated levels.

 

Also, Kimdesu's cable modem is connecting to a CMTS produced by CISCO.  In cases such as this, CISCO's own documentation suggests adding an amplifier to help boost signal levels back to the CMTS.

 

Kimdesu in an ideal world, Comcast would send out a tech who understands that something between your cable modem and the local hub is making a mess of your upstream signal levels.  Failing that, what is well worth trying is getting yourself a Return Gain Amplifier such as the Antronix RRA1-10 (you can find it on Amazon). 

 

You'll also need 2 extra coax cables.  I'd suggest some decent RG6.  You can get this anywhere including Amazon.

 

Read the instructions carefully, make sure you hook it up correctly. 

 

What this device does is amplify the the return signal levels from your cable modem by about 10dB.  This gives the whole system a lot more leeway in determining upstream power levels.

 

I had exactly the same problem you did and installing this device rectified it immediately.   You'll still get the Dynamic Ranging Window violation warnings, because whatever is making a mess of your upstream power levels is still there.

 

Nonetheless, there's a decent chance your T3 timeouts will vanish.  They certainly did in my case and my internet has been rock solid since.

Highlighted
Expert

Re: SLOW SPEEDS & ERRORS FROM COMCAST |CM1000V2 |NETGEAR R6700|HELP!!!!!

"Pedantic" ? LMAO. You had to resort to using an insulting term..... That typically shows insecurity on the part of the insulter.... I won't lower myself to that level..... As for the rest, tell me stuff that I don't already know.....

 

Yes and the modem is REJECTING that command because it's exceeding the dynamic ranging window.  That's what this error in the log means:

"RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW".

 

That's still not what that means, sorry.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!