9 Messages
Constant connection drops throughout the day, is it related to interference in the line?
For the last few weeks I've been having intermittent connection issues (both wired and wireless). I have tried most of the basic troubleshooting steps (restarting the modem and router, checking the coax cable to the modem, switching to just my modem, etc.). After viewing the logs of my modem, I believe it has something to do with my downstream bonded channels. The SNR, power and uncorrected errors on channel 34 have me convinced it might be a interference issues, but I'm not a expert on the matter.
I have a Motorola MB8600 for reference. I will post my Software and Connection settings as well as a few of my Event Logs. Any and all help/advice is appreciated!
06:55:56 Wed May 1 2024 |
Warning (5) | MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:56:11 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:56:18 Wed May 1 2024 |
Warning (5) | MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:56:26 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:57:55 Wed May 1 2024 |
Warning (5) | MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:57:56 Wed May 1 2024 |
Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:58:12 Wed May 1 2024 |
Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:Fixed Initial, 5-42MHz. | |||
06:58:14 Wed May 1 2024 |
Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. | |||
06:58:14 Wed May 1 2024 |
Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. | |||
06:58:14 Wed May 1 2024 |
Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz. | |||
06:58:20 Wed May 1 2024 |
Notice (6) | Honoring MDD; IP provisioning mode = IPv6 | |||
06:58:28 Wed May 1 2024 |
Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. | |||
06:58:28 Wed May 1 2024 |
Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. | |||
06:58:31 Wed May 1 2024 |
Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. | |||
06:58:35 Wed May 1 2024 |
Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. | |||
06:58:35 Wed May 1 2024 |
Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. | |||
06:58:35 Wed May 1 2024 |
Critical (3) | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 85MHz. | |||
06:58:36 Wed May 1 2024 |
Critical (3) | UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:58:41 Wed May 1 2024 |
Notice (6) | Honoring MDD; IP provisioning mode = IPv6 | |||
06:58:49 Wed May 1 2024 |
Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. | |||
06:58:49 Wed May 1 2024 |
Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. | |||
06:58:49 Wed May 1 2024 |
Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. | |||
06:58:51 Wed May 1 2024 |
Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=0;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:58:53 Wed May 1 2024 |
Notice (6) | DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:59:04 Wed May 1 2024 |
Critical (3) | UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:59:04 Wed May 1 2024 |
Warning (5) | RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:59:06 Wed May 1 2024 |
Critical (3) | UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:59:19 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:59:19 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:59:19 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 21; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:59:38 Wed May 1 2024 |
Warning (5) | MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
06:59:55 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
07:00:00 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
07:02:04 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
07:05:08 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; | |||
07:06:20 Wed May 1 2024 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Software | |||||||||||||||||||||||||||
|
Connection | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
XfinityKei
Official Employee
•
1.4K Messages
1 year ago
Hi @user_le7bgy I'm sorry to hear about your connection drops. I use my internet daily, and I understand how inconvenient it can be when the internet is dropping. Thanks for letting us know about the troubleshooting steps you have performed. I am happy to take a closer look at your account and network to help from my side. Can you please direct message me your first and last name along with your full service address so that I can assist you further?
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
0
0
EG
Expert
•
110.1K Messages
1 year ago
@user_le7bgy @XfinityKei
Please circle back here and post any possible solutions for the issue here in these open 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.
0
0
user_le7bgy
9 Messages
1 year ago
I spoke to tech support and they can see my network issues, but an onsite tech is needed to investigate further. One is scheduled to come onsite tomorrow. I will update once I get the verdict from them.
2
user_le7bgy
9 Messages
1 year ago
Field Tech came onsite today. He did remove a few excess cables leading into my apartment, since I don't use them. The main problem is the RG-59 cable leading into my apartment from the main box.
He will be back on Wednesday with help to replace the faulty cabling, which should fix my internet issue. I will update once it is complete.
1
0
EG
Expert
•
110.1K Messages
1 year ago
Whoa.... RG59..... That stuff is ancient and not good for today's modern cable plants / systems.
1
0
EG
Expert
•
110.1K Messages
1 year ago
Yes. And it's not just the loss factor, but the noise shielding is not very good either. Good luck !
0
0
user_le7bgy
9 Messages
1 year ago
Ok the cabling replacement has been complete by the field techs. They said there's some extra maintenance that needs to be done as well later today or tomorrow, but they replaced the old RG-59.
I'll have to monitor my connection over the next few days before I can say its fixed.
1
0
EG
Expert
•
110.1K Messages
1 year ago
@user_le7bgy Good luck !
0
0
user_le7bgy
9 Messages
1 year ago
Quick update from the last time. After the field tech replaced the old RG-59 cable, I was still having intermittent connection drops. Same as before, bad power and SNR on my modem's downstream channel 34. It improved slightly, but still not within desired ranges.
I placed another support case for today. When the field tech came back out (same guy), he said that the maintenance crew he scheduled to replace old equipment running from my apartment to the street never did it.
So he had them do it just now, not really sure what they replaced, but they were on the roof. Also side note, my upstairs neighbor was having the same issue as me according to the field tech and he believes that this time the issue is fixed. With the work the maintenance crew did today, I am a bit more hopeful that this time the issue is resolved. I'll have to monitor my network for another few days before I can confidently say it is though.
He also gave me his supervisor's phone number for a direct line in case I have more issues.
(edited)
2
0
EG
Expert
•
110.1K Messages
1 year ago
Thanks for that latest update. Fingers crossed ! 🤞
0
0
user_le7bgy
9 Messages
11 months ago
After monitoring my network for over a week, I can confirm that the field tech replacing all of the old cabling in my apartment and the one's leading to the street fixed the connection drops.
Took a little longer than I hoped, but at least it's fixed now.
0
EG
Expert
•
110.1K Messages
11 months ago
Glad you got it squared away !
0
0