U

Thursday, October 3rd, 2024 7:13 PM

No Ranging Response received - T3 time-out

I had a tech out a few months ago after upgrading my Internet speeds and not being able to obtain promised upload speeds. He voluntarily replaced one of the outside lines and coax splitters. Then, suddenly there were frequent announcements that work was being done in town that lasted over an week, no explanation given.

Unfortunately, family emergencies kept me at a hospital. Back at home I still wasn’t receiving advertised upload speeds. Things have finally calmed down and I went to take a closer look at what was going on because we have been receiving intermittent disconnects.

Two days ago, I went crazy speaking with online outsourced tech support and got nowhere. I even posted some of my modem’s logs for them to see the disconnects and errors. When one rep found out I had been using my own modem, he simply stated I needed to rent one from you which is ridiculous. I’ve had my own modems for over 15 years without any issues like this. In fact, the modem was working fine prior to the speed upgrade and also the original person updating my modem’s bootfile.

I can’t afford to have these intermittent connections, so I replaced my 1 year-old supported Motorola Docsis 3.1 modem with a newer Arris S34 last night and provisioned it. 

Lo and behold, I’ve gone up from ~45 mbps upload speeds to around 340 mbps speeds. 

It would have nice if your techs were knowledgeable/trained enough from the start to let me know that the poor upload speeds could have been resolved with a newer modem that had more upload channels. It would have saved everyone a lot of time.

This aside, I’m still getting some critical errors that I’m monitoring closely. I’ve checked my connections and the coax is a home run. The connections are all tight, even the new ones on the outside. No splitters. T3 critical errors indicate that the problem is a CMTS communication issue back Xfinity, with the intermittent problem likely at the street. I don’t know if you have a newer bootfile for this brand new model (also recently released) that could address these errors.

It’s a new modem, and I was having issues with the previous one as well so I’m ruling out these supported modems as a culprit. I don’t want to be held random to your modems as a “solution” either.

Please address this without giving me the run around over and over again. Thank you. 

Here is the latest logs:

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
4 Locked 256QAM 411000000 Hz -1.3 dBmV 43.4 dB 0 0
12 Locked 256QAM 459000000 Hz -1.3 dBmV 40.4 dB 0 0
20 Locked 256QAM 507000000 Hz -1.3 dBmV 43.4 dB 0 0
28 Locked 256QAM 555000000 Hz -1.8 dBmV 40.9 dB 0 0
1 Locked 256QAM 393000000 Hz -1.4 dBmV 43.4 dB 0 0
2 Locked 256QAM 399000000 Hz -1.4 dBmV 43.4 dB 0 0
3 Locked 256QAM 405000000 Hz -1.4 dBmV 40.9 dB 0 0
5 Locked 256QAM 417000000 Hz -1.4 dBmV 40.9 dB 0 0
6 Locked 256QAM 423000000 Hz -1.4 dBmV 40.9 dB 0 0
7 Locked 256QAM 429000000 Hz -1.4 dBmV 40.9 dB 0 0
8 Locked 256QAM 435000000 Hz -1.6 dBmV 43.4 dB 0 0
9 Locked 256QAM 441000000 Hz -1.6 dBmV 40.9 dB 0 0
10 Locked 256QAM 447000000 Hz -1.5 dBmV 40.9 dB 0 0
11 Locked 256QAM 453000000 Hz -1.3 dBmV 43.4 dB 0 0
13 Locked 256QAM 465000000 Hz -1.3 dBmV 43.4 dB 0 0
14 Locked 256QAM 471000000 Hz -1.2 dBmV 43.4 dB 0 0
15 Locked 256QAM 477000000 Hz -1.3 dBmV 40.9 dB 0 0
16 Locked 256QAM 483000000 Hz -1.3 dBmV 40.9 dB 0 0
17 Locked 256QAM 489000000 Hz -1.3 dBmV 43.4 dB 0 0
18 Locked 256QAM 495000000 Hz -1.3 dBmV 40.9 dB 0 0
19 Locked 256QAM 501000000 Hz -1.3 dBmV 40.9 dB 0 0
21 Locked 256QAM 513000000 Hz -1.4 dBmV 40.9 dB 0 0
22 Locked 256QAM 519000000 Hz -1.3 dBmV 40.9 dB 0 0
23 Locked 256QAM 525000000 Hz -1.4 dBmV 40.9 dB 0 0
24 Locked 256QAM 531000000 Hz -1.5 dBmV 40.9 dB 0 0
25 Locked 256QAM 537000000 Hz -1.6 dBmV 40.9 dB 0 0
26 Locked 256QAM 543000000 Hz -1.7 dBmV 40.9 dB 0 0
27 Locked 256QAM 549000000 Hz -1.8 dBmV 40.9 dB 0 0
29 Locked 256QAM 561000000 Hz -1.9 dBmV 40.9 dB 0 0
30 Locked 256QAM 567000000 Hz -1.9 dBmV 40.9 dB 0 0
31 Locked 256QAM 573000000 Hz -1.9 dBmV 40.9 dB 0 0
32 Locked 256QAM 579000000 Hz -2.0 dBmV 40.4 dB 0 0
193 Locked OFDM PLC 690000000 Hz -3.2 dBmV 42.0 dB 37412729 0
194 Locked OFDM PLC 957000000 Hz -6.9 dBmV 40.0 dB 56558461 0


Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
18 Locked SC-QAM 22800000 Hz 6400000 38.0 dBmV
20 Locked SC-QAM 35600000 Hz 6400000 38.8 dBmV
19 Locked SC-QAM 29200000 Hz 6400000 38.3 dBmV
17 Locked SC-QAM 16400000 Hz 6400000 37.3 dBmV
43 Locked OFDMA 36200000 Hz 44400000 35.0 dBmV


10/03/2024 10:26:22 Critical No Ranging Response received - T3 time-out;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1;

/03/2024 08:08:50 Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1;

10/03/2024 08:08:50
Warning REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1;
10/03/2024 07:59:54 Warning

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1

10/03/2024 07:59:31 Error Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1;

10/03/2024 07:58:20
Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1;

10/03/2024 07:57:29
Warning Lost MDD Timeout;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1;

10/03/2024 07:57:26
Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1;

10/03/2024 07:57:21
Critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1;

10/03/2024 07:56:09
Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1;

10/03/2024 07:56:09
Warning REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided

13 Messages

1 month ago

Spent another hour plus with a call center. The agent actually told me to call the new modem manufacturer and it I wasn’t too happy, having to reexplain that this would make it two new modems in a row with same error messages and that the problem with the modem was unlikely as T3 tends to be more incoming line related. Asked to speak with a supervisor where I was put on extended hold again. Then finally reexplained things once again and this time the supervisor understood what I was saying and offered to send out a tech tomorrow.

Given that the last in-person tech couldn’t even understand why I wasn’t receiving full upload speeds, my expectations are understandably very low.

No one, especially more tech-savvy individuals who work with networking and computers should have to go through all of these layers of red tape nonsense. This kind of thing (outsourcing to people who don’t really care or are incompetent) can’t save that much money after going back and forth this much, and also reflects poorly on Xfinity/Comcast.

(edited)

13 Messages

1 month ago

Still waiting on tech but here’s the latest logs. No disconnects BUT it is an intermittent issue and I wonder after a certain amount of these critical alerts it floods the modem which causes them to reboot. I removed my MAC addresses but I think you get the picture. The US profile change is a new notice to me and not sure what to make out of it. Perhaps someone is on here reading this and trying to fix it on their end.:

10/04/2024 07:37:40 Notice US profile assignment change. US Chan ID: 43; Previous Profile: 11; New Profile: 12.;CM-MAC=

10/04/2024 07:30:10
Notice US profile assignment change. US Chan ID: 43; Previous Profile: 12; New Profile: 11.;CM-MAC=

10/04/2024 07:23:07
Critical No Ranging Response received - T3 time-out;CM-MAC=

10/04/2024 06:32:38
Critical No Ranging Response received - T3 time-out;CM-MAC=

10/04/2024 02:31:17
Critical No Ranging Response received - T3 time-out;CM-MAC=

10/03/2024 23:20:42
Critical No Ranging Response received - T3 time-out;CM-MAC

10/03/2024 22:30:11
Critical No Ranging Response received - T3 time-out;CM-MAC=

10/03/2024 20:25:26
Critical No Ranging Response received - T3 time-out;CM-MAC=

10/03/2024 19:59:44
Critical No Ranging Response received - T3 time-out;CM-MAC=



13 Messages

1 month ago

Comcast missed their tech appointment window between 2-4 PM while I waited around. I had other appointments to make including picking up my toddlers in another town.

While I was away, another tech showed up but I managed to get to him while I was pulling back at the house over an hour later. I gave him the details. He checked some lines running underground near the street and said the signals were good. He tightened the coax in the underground box. I told him my upload speeds and download speeds and he insisted that no customer modem could currently do that. I informed him I have a brand new Arris S34 and he seemed surprised. Showed him my modem logs which he didn’t seem particularly interested in seeing. He essentially (to paraphrase) told me that it tells him nothing.

He went to the house and he tightened the connection around a coax filter anyways (think it’s a MOCA filter?) although I don’t have any cable TV or DVR boxes.

My SNR was running from the low 40s to up to ~44 (sometimes higher) and are now almost ALL 43.4 dB exact. I assume him tightening the connections had something to do with this because I’ve never seen it before nor did I even realize that it was even possible.

However, the errors still exist. I asked him about the intermittent disconnections and he said it could be the result of someone else’s Internet in the neighborhood causing these issues, or what he referred to as “ingress.” He said he would check in with the local xfinity guy tomorrow morning and monitor what’s going on as he could probably determine any bad interference. And that’s it. He didn’t solve the underlying issue. Just tightened a few things.


10/04/2024 16:58:40
Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=

10/04/2024 16:58:40
Warning REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=

10/04/2024 16:58:36
Warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1

12/31/1969 19:00:49
Notice CMSTATUS:US_Diplexer_Mode_Change: [TLV-21.1], [5-85MHz].

12/31/1969 19:00:49
Notice CMSTATUS:DS_Diplexer_Mode_Change_Ignored: [TLV-21.3], [1002MHz].

12/31/1969 19:00:49
Notice CMSTATUS:DS_Diplexer_Mode_Change_Ignored: [TLV-21.2], [258MHz].

12/31/1969 19:00:49
Notice CMSTATUS:US_Diplexer_Mode_Change_Ignored: [TLV-9], [85MHz].

12/31/1969 19:00:45
Notice CMSTATUS:DS_Diplexer_Mode_Initialization: [108-1002MHz].

12/31/1969 19:00:45
Notice CMSTATUS:US_Diplexer_Mode_Initialization: [5-42MHz].

10/04/2024 16:57:08
Critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=

10/04/2024 16:54:23
Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=

10/04/2024 16:54:23
Warning REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=

10/04/2024 16:54:21
Warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1

10/04/2024 16:54:06
Notice CMSTATUS:US_Diplexer_Mode_Change: [TLV-21.1], [5-85MHz].

10/04/2024 16:54:06
Notice CMSTATUS:DS_Diplexer_Mode_Change_Ignored: [TLV-21.3], [1002MHz].

10/04/2024 16:54:06
Notice CMSTATUS:DS_Diplexer_Mode_Change_Ignored: [TLV-21.2], [258MHz].

10/04/2024 16:54:06
Notice CMSTATUS:US_Diplexer_Mode_Change_Ignored: [TLV-9], [85MHz].

10/04/2024 16:53:58
Error Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=

10/04/2024 16:46:50
Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=

10/04/2024 16:46:04
Warning Lost MDD Timeout;CM-MAC=

10/04/2024 16:46:03
Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=

10/04/2024 16:46:02
Warning Lost MDD Timeout;CM-MAC=

10/04/2024 16:46:01
Notice CM-STATUS message sent. Event Type Code: 21; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=

10/04/2024 16:45:57
Critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=

13 Messages

1 month ago

Here’s the stats in case it helps. You can see how the SNR looks pretty decent (or so I think) after he retightened some connections:

Procedure Status Comment
Acquire Downstream Channel 411000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
4 Locked 256QAM 411000000 Hz 2.7 dBmV 43.4 dB 0 0
12 Locked 256QAM 459000000 Hz 2.8 dBmV 43.4 dB 0 0
20 Locked 256QAM 507000000 Hz 2.8 dBmV 43.4 dB 0 0
28 Locked 256QAM 555000000 Hz 2.4 dBmV 43.4 dB 0 0
1 Locked 256QAM 393000000 Hz 2.9 dBmV 43.4 dB 0 0
2 Locked 256QAM 399000000 Hz 2.8 dBmV 43.4 dB 0 0
3 Locked 256QAM 405000000 Hz 2.8 dBmV 43.4 dB 0 0
5 Locked 256QAM 417000000 Hz 2.7 dBmV 43.4 dB 0 0
6 Locked 256QAM 423000000 Hz 2.8 dBmV 43.4 dB 0 0
7 Locked 256QAM 429000000 Hz 2.7 dBmV 43.4 dB 0 0
8 Locked 256QAM 435000000 Hz 2.7 dBmV 43.4 dB 0 0
9 Locked 256QAM 441000000 Hz 2.5 dBmV 43.4 dB 0 0
10 Locked 256QAM 447000000 Hz 2.7 dBmV 43.4 dB 0 0
11 Locked 256QAM 453000000 Hz 2.9 dBmV 43.4 dB 0 0
13 Locked 256QAM 465000000 Hz 2.9 dBmV 43.4 dB 0 0
14 Locked 256QAM 471000000 Hz 2.9 dBmV 43.4 dB 0 0
15 Locked 256QAM 477000000 Hz 2.8 dBmV 43.4 dB 0 0
16 Locked 256QAM 483000000 Hz 2.9 dBmV 43.4 dB 0 0
17 Locked 256QAM 489000000 Hz 2.8 dBmV 43.4 dB 0 0
18 Locked 256QAM 495000000 Hz 2.8 dBmV 43.4 dB 0 0
19 Locked 256QAM 501000000 Hz 2.8 dBmV 43.4 dB 0 0
21 Locked 256QAM 513000000 Hz 2.8 dBmV 40.9 dB 0 0
22 Locked 256QAM 519000000 Hz 2.8 dBmV 43.4 dB 0 0
23 Locked 256QAM 525000000 Hz 2.8 dBmV 43.4 dB 0 0
24 Locked 256QAM 531000000 Hz 2.7 dBmV 43.4 dB 0 0
25 Locked 256QAM 537000000 Hz 2.6 dBmV 43.4 dB 0 0
26 Locked 256QAM 543000000 Hz 2.5 dBmV 43.4 dB 0 0
27 Locked 256QAM 549000000 Hz 2.4 dBmV 40.9 dB 0 0
29 Locked 256QAM 561000000 Hz 2.3 dBmV 43.4 dB 0 0
30 Locked 256QAM 567000000 Hz 2.3 dBmV 43.4 dB 0 0
31 Locked 256QAM 573000000 Hz 2.3 dBmV 40.9 dB 0 0
32 Locked 256QAM 579000000 Hz 2.4 dBmV 43.4 dB 0 0
193 Locked OFDM PLC 690000000 Hz 1.3 dBmV 44.0 dB 1288635 0
194 Locked OFDM PLC 957000000 Hz -2.1 dBmV 42.0 dB 5650777 0


Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
20 Locked SC-QAM 35600000 Hz 6400000 35.3 dBmV
17 Locked SC-QAM 16400000 Hz 6400000 33.8 dBmV
19 Locked SC-QAM 29200000 Hz 6400000 34.8 dBmV
18 Locked SC-QAM 22800000 Hz 6400000 34.3 dBmV
43 Locked OFDMA 36200000 Hz 44400000 31.8 dBmV





13 Messages

1 month ago

Update: posted to Reddit since I’ve had 0 feedback or acknowledgment here:

https://www.reddit.com/r/Comcast_Xfinity/s/hY7HJyylJi

Additional update (posted on Reddit): noticed that the upstream power levels are consistently below Arris recommendations which are above 40+. Arris instructs techs to reach out to the cable providers in order to have the power increased. I brought this to an agent’s attention on Reddit and he confirmed that I was correct in this. But this may have nothing to do with the errors/disconnects that I have been receiving. Link to Arris’ documentation regarding S33 and S34 modems and power levels in the Reddit cross-post.

Xfinity has scheduled a supervisor tech to come out next week to take a closer look since the issues are still unresolved.

Official Employee

 • 

1.8K Messages

1 month ago

Hello user_rwc2zv, thank you for including such great detail in your post and for taking all of those steps on your end to try and find a solution to your intermittent connection issue. I hope your family is doing fine and everyone is healthy. I can only imagine what you've been going through, connection issues are always frustrating let alone going through it during those family emergencies. You've mentioned a few modems, so I'd like to review your account, confirm we have the correct device listed as active, check out your signal levels, and take any appropriate steps after. In order to get started can you please send a direct message to Xfinity Support with your full name and full address by clicking the chat icon in the top right? Here's the detailed steps to direct message us:

• Click "Sign In" if necessary

• Click the "Direct Message” icon (upper right corner of this page)

• Click the "New message" (pencil and paper) icon

• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list

• Type your message in the text area near the bottom of the window

• Press Enter to send your message

 

13 Messages

Two modems as of this year. The one I currently have connected is a new Arris s34 as of a few days ago. Great speeds, but still intermittent issues like before and mostly T3 critical notices every couple of hours, sometimes less. And lower than recommended power levels.

See below for recommended power levels and compare how they stack up to mine above (FTR they didn’t change after rebooting earlier today.)
https://arris.my.salesforce-sites.com/consumers/articles/General_FAQs/S33-Cable-Signal-Levels

(edited)

Expert

 • 

106.9K Messages

1 month ago

@user_rwc2zv @XfinityMarcos 

Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.

13 Messages

It’s just a waiting game at this point to see if the supervisor even recognizes the power is not within spec and needs adjustment along with these T3 issues. My understanding is that T3 and ingress can be a pain to try to resolve as it often involves numerous homes so I’m not holding my breath. Again, to be fair to xfinity I had a near perfect run when it came to staying online for at least 5 years.

13 Messages

20 days ago

10/16/24 Update: Comcast Executive relations reached out to me yesterday and apologized that I had gone through stuff. He mentioned someone would reach out to me about a watch I was told was completely free as well as the line charge that turns out wasn’t while I had waited on the phone regarding this issue (one issue led to another issue…) He also offered to send out another tech agent to look at the modem but I mentioned that I was already waiting for the tech supervisor and local installer to potentially work on power to the tap and imbalances they found here.

Meanwhile, I had received the 12 db Return Path Attenuator yesterday and installed it at the modem. Of course I had unplugged it and it rebooted. The Upstream Bonded Channel values are now in perfect range of 45-50 dBmV (except the OFDMA which I read elsewhere is supposedly normal) with what Arris recommends for S33 and S34 modems. Downstream values are still the same as before which is what I had wanted (versus an ordinary attenuator or splitter.) It appears DOCSIS 3.1 modems almost always require higher power levels but depends on the manufacturer. However the T3 errors are still occurring. I counted 16 T3 critical errors yesterday alone after installing this so nothing really changed. I don’t know what this entails or if it’s normal.

Channel ID Lock Status US Channel Type Frequency Width Power
20 Locked SC-QAM 35600000 Hz 6400000 47.0 dBmV
17 Locked SC-QAM 16400000 Hz 6400000 45.0 dBmV
19 Locked SC-QAM 29200000 Hz 6400000 46.0 dBmV
18 Locked SC-QAM 22800000 Hz 6400000 45.8 dBmV
43 Locked OFDMA 36200000 Hz 44400000 35.2 dBmV

Official Employee

 • 

2.5K Messages

@user_rwc2zv Thank you for that update. I will follow up next week to check in.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Official Employee

 • 

1.5K Messages

 

user_rwc2zv We wanted to follow up as promised to see how things are going on your end. 

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick
forum icon

New to the Community?

Start Here