Skip to main content

    Support

    Offers

jonweareqo's profile
jonweareqo
Conversation Starter
1st Like
1st Reply

Frequent Visitor

 • 

8 Messages

Friday, September 25th, 2020 8:00 AM

Closed

Error on Netgear device: Started Unicast Maintenance Ranging - No Response received - T3 time-out

I am receiving these 5 errors on my Netgear C6220:

  • 16 consecutive T3 timeouts while trying to range on upstream channel 1
  • Unicast Maintenance Ranging attempted - No response - Retries exhausted
  • Started Unicast Maintenance Ranging - No Response received - T3 time-out
  • Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
  • MDD message timeout

These are causing my router/modem to lose connection to the internet & requires that I power-cycle the router.  Happens every 2 hours or so. Is this an issue with the service or with my router? Thanks for your help!

 

**EDIT** A tech visit failed to solve the issue & the corporate employees refuse to answer my messages now. I am losing connection at least 10x/day, making the service basically unusable. All be warned who are having similar issues! I will be switching to the city broadband the second it's available in my neighborhood.

Question

 • 

Updated 

4 years ago

4K

17

This conversation is no longer open for comments or replies and is no longer visible to community members.

EG

Expert

 • 

111.5K Messages

5 years ago

The stats are o/k. Would you please also post the error log entries in their entirety.

0

EG

Expert

 • 

111.5K Messages

5 years ago

Even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.

 

There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.


I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They can check the CMTS (Cable Modem Termination System) for any real time degradation and / or error reports, see your node / cable plant and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.

You should get a reply here in your topic. Good luck !

0

jonweareqo

Frequent Visitor

 • 

8 Messages

5 years ago

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25632585000000 Hz2.2 dBmV39.9 dB14117
2LockedQAM25633591000000 Hz2.8 dBmV40.3 dB1306
3LockedQAM25634597000000 Hz3.1 dBmV40.3 dB18213
4LockedQAM25635603000000 Hz3.4 dBmV40.4 dB14916
5LockedQAM25636609000000 Hz3.2 dBmV40.3 dB11811
6LockedQAM25637615000000 Hz3.7 dBmV40.4 dB12112
7LockedQAM25638621000000 Hz3.8 dBmV40.6 dB11710
8LockedQAM25639627000000 Hz3.6 dBmV40.3 dB1403
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA15120 Ksym/sec36500000 Hz47.5 dBmV
2LockedATDMA25120 Ksym/sec30100000 Hz46.8 dBmV
3LockedATDMA35120 Ksym/sec23700000 Hz44.5 dBmV
4LockedATDMA45120 Ksym/sec17300000 Hz44.5 dBmV

0

0

EG

Expert

 • 

111.5K Messages

5 years ago

Quite welcome !

0

0

jonweareqo

Frequent Visitor

 • 

8 Messages

5 years ago

Thank you so much!

0

0

EG

Expert

 • 

111.5K Messages

5 years ago

Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.


0

jonweareqo

Frequent Visitor

 • 

8 Messages

5 years ago

Sure thing:

TimePriorityDescription
2020-09-25, 07:32:54.0Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-25, 07:28:34.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-25, 07:28:21.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-25, 07:28:21.0Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-25, 07:28:21.0Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-25, 07:28:01.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-25, 07:28:01.0Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-25, 07:28:01.0Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 20:36:35.0Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 20:32:15.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 20:32:08.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 20:32:08.0Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 20:32:08.0Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 20:31:40.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 20:31:40.0Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 20:31:40.0Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 15:50:53.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 08:30:27.0Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 08:26:07.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 08:25:57.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 08:25:57.0Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 08:25:57.0Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 02:36:07.0Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-24, 02:31:47.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-23, 21:50:38.0Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.0;CM-VER=3.0;
2020-09-23, 21:50:16.0Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
2020-09-23, 21:45:56.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.0;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.0;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.0;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:9b:a4:e8;CMTS-MAC=00:01:5c:73:c0:64;CM-QOS=1.0;CM-VER=3.0;

0

0

XfinityAmira

Official Employee

 • 

4.2K Messages

5 years ago

Hello jonweareqo, thanks for reaching out to us on our Forums page. I'm sorry to hear about the connection issues you have been experiencing and I really appreciate you posting your signal levels. I would love to take a further look into this on my end so that we can get this corrected for you. 

 

Can you please send me a Private Message including your first and last name as it appears on the account? 

 

To send me a Private Message, please click my name “ComcastAmira” and click “Send a message". 

0

jonweareqo

Frequent Visitor

 • 

8 Messages

5 years ago

Hi Amira,

I sent you a private message on Friday, but have yet to hear back. Let me know if I need to send another. Thanks!

0

0

XfinityAmira

Official Employee

 • 

4.2K Messages

5 years ago

Good Morning jonweareqo! I have responded to your private message and look forward to hearing back from you. Thank you!

0

0

jonweareqo

Frequent Visitor

 • 

8 Messages

5 years ago

A tech visit failed to solve the issue & the corporate employees refuse to answer my messages now. I am losing connection at least 10x/day, making the service basically unusable. All be warned who are having similar issues! I will be switching to the city broadband the second it's available in my neighborhood.

0

0

EG

Expert

 • 

111.5K Messages

5 years ago

I'm going to try re-escalating this. Good luck !

0

0

jonweareqo

Frequent Visitor

 • 

8 Messages

5 years ago

Thank you EG!

0

0

EG

Expert

 • 

111.5K Messages

5 years ago

No prob ! 

0

0

CCMorgan

Gold Problem Solver

 • 

3.3K Messages

5 years ago

Hi, jonweareqo. Oh no! Sorry to hear that the issues continue. We definitely want to get this worked out for you, as soon as possible. Please send me a PM with your first and last name so I can pick up where you guys left off. Thanks!

0

0

forum icon

New to the Community?

Start Here