Skip to main content

    Support

    Offers

jdlail's profile
jdlail
1st Topic
1st Reply

New Poster

 • 

4 Messages

Sunday, March 10th, 2024 11:14 PM

Closed

Upstream power too low?

My internet connection drops out about once a day.

I have an Arris T25 (customer owned).

I only have Internet and voice service, but back in the day when I had Cable TV, Internet and Voice, I had signal problems for my TV. My wiring is early 90s. Comcast installed PPC-TM-U/U Active Return. This supports MOCA, but I have never had a MOCA network.

I see quite a few range time outs and MDD time outs with error code 4 and other log entries with event type code 16 and 2.

Below are my downstream and upstream. stats. Is my upstream power just too low? Could this be resolved in some way?

 

Question

 • 

Updated 

1 year ago

105

1

0

jdlail

New Poster

 • 

4 Messages

1 year ago

If it is helpful, here is a photo of the PPC-TM-U/U Active Return

3

0

XfinityKatie

Official Employee

 • 

744 Messages

@jdlail Thank you for taking the time to reach out and make this post so we can help with your connection. We want to make sure that you are able to enjoy your servies with us free of interruption, so we'd love to help with this! If your upstream power is too high, that can cause issues and interfere with your connection. When your connection drops, is this happening around the same time every day, or is it at random times? Are you experiencing this across all of your devices? Is this the same experience over WiFi and ethernet?

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

1 year ago

0

jdlail

New Poster

 • 

4 Messages

Thank you for your response.

The drops are mostly random during the day (not often at night). Since the modem reboots, it's across all devices, wired and Ethernet. Once it finishes it fairly long reboot, things are normal again.

Below is the log file:

Date Time Event ID Event Level Description
3/8/2024 10:06 67061602 6 DS profile config update. DS Chan ID: 193.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/8/2024 15:16 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/9/2024 15:50 74010100 6 CM-STATUS message sent. Event Type Code: 5; Chan ID: 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/9/2024 20:09 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:06 67061602 6 DS profile config update. DS Chan ID: 193.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:19 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:19 74010100 6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:21 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:21 74010100 6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:22 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:22 74010100 6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:26 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:26 74010100 6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 10:36 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 11:53 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 13:58 74010100 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 15:19 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/10/2024 17:59 74010100 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/11/2024 7:06 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/11/2024 23:28 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/11/2024 23:29 82000400 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/11/2024 23:29 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 0:53 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 0:53 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 9:20 74010100 6 CM-STATUS message sent. Event Type Code: 2; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 9:20 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 9:20 74010100 6 CM-STATUS message sent. Event Type Code: 1; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 10:06 67061602 6 DS profile config update. DS Chan ID: 193.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 11:02 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 11:08 74010100 6 CM-STATUS message sent. Event Type Code: 5; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 11:11 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 11:30 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 11:30 74010100 6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:26 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:26 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:53 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:53 74010100 6 CM-STATUS message sent. Event Type Code: 5; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:54 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:54 74010100 6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:54 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:55 74010100 6 CM-STATUS message sent. Event Type Code: 1; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:55 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:55 74010100 6 CM-STATUS message sent. Event Type Code: 5; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:55 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:56 74010100 6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:57 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:57 74010100 6 CM-STATUS message sent. Event Type Code: 1; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:58 84020200 5 Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 12:58 74010100 6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3/12/2024 17:22 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

1 year ago

0

XfinityPaula

Official Employee

 • 

1.5K Messages

@jdlail With the events mostly being random and more during the day it would be beneficial to set up a repair visit. Correcting one level can impact another level and have you going in circles trying to figure it out. The technician can check the signals along with the lines and any splitters that may be connected and the main outside connection. Please send us a direct message with your name and service address. From there we will verify your account, check the levels from this side and set up the appointment as needed. 

To send a direct message, please click on the chat icon in the top-right corner of the screen, and select "Xfinity Support" to initiate a live chat. 
Click "Sign In" if necessary
Click the "direct messaging" icon or https://comca.st/3J0ir1l
Click the "New message" (pencil and paper) icon
Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "Xfinity Support" graphic replaces the "To:" line
Type your message in the text area near the bottom of the window
Press Enter to send it

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

1 year ago

forum icon

New to the Community?

Start Here