MDD timeout / Sync failure - causing disconnects every day or two?

I just moved from Colorado to Connecticut (I have/had Comcast cable internet in both locations).

I had no issues w/ stable internet in Colorado with my Arris Surfboard SB6141 (9 years old).

When I installed the same modem in CT, I was seeing frequent T3 and T4 timeouts and disconnects multiple times a day.

I purchased a new Arris Surfboard S33 (thinking the issues could be due to the old cable modem) and installed it a few days ago.

Well guess what... the S33 is also running into T3 timeouts, MDD timeouts and sync failures... although less frequently (seems to occur every day or 2).

Originally, I had the older SB6141 connected directly to the incoming cable (i.e. no splitters).

Currently, I have the S33 feeding off of a single splitter (but based on the similarities with the SB1641 I don't think the splitter/wiring is the issue here).

Here are the S33's status/logs...

Can someone help me out here?

Information
Standard Specification Compliant	DOCSIS 3.1
Hardware Version	V1.0
Software Version	TB01.03.001.11_051722_212.S3
Cable Modem MAC Address	REDACTED
Serial Number	REDACTED

Startup Procedure
Procedure	Status	Comment
Acquire Downstream Channel	417000000 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	QAM256	417000000 Hz	0 dBmV	41 dB	49602	12510
1	Locked	QAM256	399000000 Hz	0 dBmV	41 dB	61928	16987
2	Locked	QAM256	405000000 Hz	0 dBmV	41 dB	60564	16540
3	Locked	QAM256	411000000 Hz	0 dBmV	41 dB	57189	14826
5	Locked	QAM256	423000000 Hz	0 dBmV	41 dB	50149	12015
6	Locked	QAM256	429000000 Hz	0 dBmV	41 dB	44994	10562
7	Locked	QAM256	435000000 Hz	0 dBmV	41 dB	41842	9864
8	Locked	QAM256	441000000 Hz	0 dBmV	41 dB	37274	8943
9	Locked	QAM256	447000000 Hz	0 dBmV	41 dB	33213	7878
10	Locked	QAM256	453000000 Hz	0 dBmV	41 dB	29558	7170
11	Locked	QAM256	459000000 Hz	0 dBmV	41 dB	26714	6513
12	Locked	QAM256	465000000 Hz	0 dBmV	41 dB	23109	5939
13	Locked	QAM256	471000000 Hz	0 dBmV	41 dB	21049	5411
14	Locked	QAM256	477000000 Hz	0 dBmV	41 dB	18489	5112
15	Locked	QAM256	483000000 Hz	1 dBmV	41 dB	16993	4750
16	Locked	QAM256	489000000 Hz	0 dBmV	41 dB	16584	4457
17	Locked	QAM256	495000000 Hz	0 dBmV	41 dB	15951	4461
18	Locked	QAM256	501000000 Hz	0 dBmV	41 dB	15861	4232
19	Locked	QAM256	507000000 Hz	0 dBmV	41 dB	15239	4205
20	Locked	QAM256	513000000 Hz	0 dBmV	41 dB	15650	4088
21	Locked	QAM256	519000000 Hz	0 dBmV	41 dB	16634	4156
22	Locked	QAM256	525000000 Hz	0 dBmV	41 dB	18266	4498
23	Locked	QAM256	531000000 Hz	0 dBmV	41 dB	19047	4510
24	Locked	QAM256	537000000 Hz	0 dBmV	40 dB	20614	5150
25	Locked	QAM256	543000000 Hz	0 dBmV	41 dB	21148	4907
26	Locked	QAM256	549000000 Hz	0 dBmV	40 dB	22405	5275
27	Locked	QAM256	555000000 Hz	0 dBmV	40 dB	23080	5125
28	Locked	QAM256	561000000 Hz	0 dBmV	40 dB	22065	5313
29	Locked	QAM256	567000000 Hz	0 dBmV	41 dB	21029	5057
30	Locked	QAM256	573000000 Hz	0 dBmV	40 dB	20669	5040
31	Locked	QAM256	579000000 Hz	0 dBmV	41 dB	19511	4796
32	Locked	QAM256	585000000 Hz	0 dBmV	40 dB	18425	4561
193	Locked	OFDM PLC	690000000 Hz	0 dBmV	39 dB	771410373	5410
194	Locked	OFDM PLC	957000000 Hz	-1 dBmV	39 dB	663439026	1068

Upstream Bonded Channels
Channel ID	Lock Status	US Channel Type	Frequency	Width	Power
1	Locked	SC-QAM	16400000 Hz	6400000	55.8 dBmV
2	Locked	SC-QAM	22800000 Hz	6400000	55.0 dBmV
3	Locked	SC-QAM	29200000 Hz	6400000	57.0 dBmV
4	Locked	SC-QAM	35600000 Hz	6400000	56.8 dBmV

Date Time	Event Level	Description
17/8/2024 17:51:47	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 17:52:13	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
17/8/2024 17:52:13	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
17/8/2024 17:52:13	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
17/8/2024 17:53:49	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 17:54:26	6	Honoring MDD; IP provisioning mode = IPv6
17/8/2024 17:54:35	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
17/8/2024 17:54:35	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
17/8/2024 17:54:35	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
17/8/2024 17:54:37	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 17:54:37	6	DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 17:54:45	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:28:06	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:28:15	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
17/8/2024 20:28:15	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
17/8/2024 20:28:16	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
17/8/2024 20:28:57	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:29:49	6	Honoring MDD; IP provisioning mode = IPv6
17/8/2024 20:30:03	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:30:05	3	DHCP failed - RS sent, no RA received;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:30:06	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:31:32	5	Lost MDD Timeout;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:31:53	3	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:31:54	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
17/8/2024 20:31:54	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
17/8/2024 20:31:54	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
17/8/2024 20:32:17	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:32:57	6	Honoring MDD; IP provisioning mode = IPv6
17/8/2024 20:33:06	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
17/8/2024 20:33:06	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
17/8/2024 20:33:08	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
17/8/2024 20:33:09	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:12	6	DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:12	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:12	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:13	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:13	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:19	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:30	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:33	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:35	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:33:35	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:34:21	3	Successful LAN WebGUI login from 24.60.255.102 on 24/08/17 at 8:34 PM.
17/8/2024 20:34:36	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:34:37	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:34:37	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:34:41	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:34:57	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:35:47	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:41:53	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:43:24	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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:50:14	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:52:45	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:53:35	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:53:37	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:54:42	6	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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 20:55:56	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:03:16	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:15:07	6	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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:15:28	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:15:43	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:21:10	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:34:05	6	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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:37:37	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:41:09	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:41:56	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:43:33	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:48:10	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:55:28	6	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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
17/8/2024 21:59:23	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
18/8/2024 04:40:14	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:15:58	3	Successful LAN WebGUI login from 24.60.255.102 on 24/08/19 at 9:15 AM.
19/8/2024 09:36:07	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:37:05	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:37:12	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
19/8/2024 09:37:12	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
19/8/2024 09:37:13	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
19/8/2024 09:39:00	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:40:08	5	Lost MDD Timeout;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:40:10	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
19/8/2024 09:40:10	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
19/8/2024 09:40:10	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
19/8/2024 09:40:16	3	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:44:15	5	Lost MDD Timeout;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:45:33	3	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:45:35	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
19/8/2024 09:45:35	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
19/8/2024 09:45:35	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
19/8/2024 09:48:07	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:48:11	6	Honoring MDD; IP provisioning mode = IPv6
19/8/2024 09:48:19	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
19/8/2024 09:48:19	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
19/8/2024 09:48:21	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
19/8/2024 09:48:22	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:48:23	6	DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 09:48:30	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
19/8/2024 11:10:58	3	Successful LAN WebGUI login from 24.60.255.102 on 24/08/19 at 11:10 AM.

Responses

BruceW

Gold Problem Solver

•

26K Messages

3 months ago

... Arris Surfboard SB6141 ... Arris Surfboard S33 ...

Note that the SB6141 is no longer an approved device, while the S33 is a recommended device. See the "All Compatible Devices" link near the bottom of https://www.xfinity.com/support/devices (at the moment it points to https://assets.xfinity.com/assets/dotcom/projects/cix-4997_compatible-devices/2024-07-18_Full-List-of-Compatible-Devices.pdf, but this changes from time to time).

The downstream power levels and SNR values posted are pretty much perfect, but the upstream power levels are out of spec (too high), which is consistent with the timeout and sync errors in the event log. Network connection problems like this are often due to poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power.

If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you can't find the problem or you'd rather have Comcast take care of it and an employee does not respond to your message here, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. It's not likely they can fix the problem remotely. If not, insist they send a tech out to identify the cause and correct it.

If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit (approx $100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

(edited)

XfinityOrlandoM

Official Employee

•

1.4K Messages

3 months ago

@user_np741m

Thanks for reaching out to us, I am a customer as well would not be happy if my connection periodically dropped. Are awesome Xfinity app https://www.xfinity.com/apps is a great tool to troubleshoot your services if the service issues cannot be resolved via that remote troubleshooting our awesome app will schedule a technician to come out to fix the issues.

Have you tried disconnecting the splitter and running your cable line directly into the modem to rule out the possibilities of the splitter going bad, I had get a new splitter as I have my TV service and Internet running through one coax outlet?

user_np741m

2 Messages

3 months ago

Update... so we had a Comcast tech come out and take a look at things and he confirmed that the upstream power was too high.

He removed the only splitter on the incoming line (which was a brand new -3.5dB splitter that I had installed with the intention of running a MoCA network) and was able to get the upstream power down to ~48dBmV and said things were now looking "good" but that I wouldn't be able to put the splitter back on.

When I objected and said that at least 1 (probably 2) splitters would be necessary for me to run a MoCA network, he basically shrugged and said that maybe something could be done at the neighborhood box to improve/lower upstream power levels to a point where I could add splitter(s) (he said that signal levels could be "rebalanced" in some way).

He said that he would submit a ticket for another tech to come out and check out the neighborhood box to see if "rebalancing" was possible (this was last Thursday and to my knowledge, nothing has happened yet).

Looking at things over the last few days (after the tech came out and removed the splitter) upstream power levels do seem better around ~48dBmV but I have seen them as high as 51dBmV. However, we are STILL getting multiple disconnects a day along with T3/T4 timeouts.

Here are some recent logs from the cable modem (S33v2):

Date Time	Event Level	Description
4/9/2024 17:32:52	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:34:52	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:37:02	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:38:00	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:38:02	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:38:02	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:38:08	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
4/9/2024 17:38:08	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
4/9/2024 17:38:09	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
4/9/2024 17:38:14	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:38:19	6	Honoring MDD; IP provisioning mode = IPv6
4/9/2024 17:38:29	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
4/9/2024 17:38:29	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
4/9/2024 17:38:30	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
4/9/2024 17:38:31	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:38:32	6	DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:38:39	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:40:03	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:41:59	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:42:53	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:42:53	6	CM-STATUS message sent. Event Type Code: 6; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:43:01	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
4/9/2024 17:43:01	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
4/9/2024 17:43:02	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
4/9/2024 17:43:07	6	Honoring MDD; IP provisioning mode = IPv6
4/9/2024 17:43:24	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:43:27	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
4/9/2024 17:43:27	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
4/9/2024 17:43:28	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
4/9/2024 17:43:29	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:43:30	6	DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:43:37	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:55:04	5	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 17:55:04	5	Dynamic Range Window violation
4/9/2024 18:22:01	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:22:59	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:22:59	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:23:07	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
4/9/2024 18:23:07	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
4/9/2024 18:23:07	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
4/9/2024 18:23:12	6	Honoring MDD; IP provisioning mode = IPv6
4/9/2024 18:23:20	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
4/9/2024 18:23:20	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
4/9/2024 18:23:20	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
4/9/2024 18:23:21	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:23:23	6	DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:23:30	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:28:10	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:28:24	5	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:28:24	5	Dynamic Range Window violation
4/9/2024 18:32:19	6	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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:32:23	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:32:24	6	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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:32:24	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
4/9/2024 18:37:19	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 08:28:09	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 08:28:15	6	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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 08:28:38	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 08:34:28	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 08:38:44	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 10:48:03	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 10:48:19	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 10:53:13	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 10:56:07	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 10:59:40	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 11:10:59	6	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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 11:18:13	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:18:51	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:19:47	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:19:48	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:19:49	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:19:51	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:19:51	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:19:57	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
5/9/2024 12:19:57	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
5/9/2024 12:19:58	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
5/9/2024 12:20:16	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:20:39	6	Honoring MDD; IP provisioning mode = IPv6
5/9/2024 12:20:47	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
5/9/2024 12:20:47	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
5/9/2024 12:20:48	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
5/9/2024 12:20:49	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:20:51	6	DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:20:58	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:32:36	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:33:27	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:33:35	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:33:36	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:33:42	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
5/9/2024 12:33:42	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
5/9/2024 12:33:43	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz.
5/9/2024 12:33:52	3	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:34:06	6	Honoring MDD; IP provisioning mode = IPv6
5/9/2024 12:34:15	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
5/9/2024 12:34:15	3	CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
5/9/2024 12:34:15	3	CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
5/9/2024 12:34:17	6	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:34:18	6	DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 12:34:25	3	UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
5/9/2024 16:02:13	3	Successful LAN WebGUI login from 24.60.255.102 on 24/09/05 at 4:02 PM.

Another thing that is relevant... we started asking the neighbors if they have issues w/ Comcast internet and we have heard back from almost everyone (who has Comcast) that they have connectivity issues as well and have had issues for YEARS. One neighbor was so fed up that they switched from Comcast and to Starlink!

So it seems like this issue might be an issue with Comcast's equipment/cable coming into the neighborhood.

No idea what can be done about the issue now and am starting to lose hope that Comcast will be able to resolve this issue.

Anyone have any suggestions about what to do next?

XfinityJorge

Official Employee

•

1.7K Messages

user_np741m Hey there! Thanks for the update and we are happy you reached back out. Let us dig a little deeper to see what is in moment after the visist. We appreciate your time and patience on this! Please send us a DM so we can get started. 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

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

3 months ago

Your Home Network

user_np741m

MDD timeout / Sync failure - causing disconnects every day or two?

Was this helpful?

BruceW

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

XfinityOrlandoM

user_np741m

XfinityJorge

New to the Community?