1 Message
Arris S33 Frequent Disconnects
Just moved into a new apartment. My S33 is frequently rebooting, the light going amber, then blinking green, then solid blue. Online chat sent a restart signal but that did not resolve the issue. Any help understanding what is happening.
Connection Status
|
Downstream Bonded Channels |
||||||||||||||
|
Channel ID |
Lock Status |
Modulation |
Frequency |
Power |
SNR/MER |
Corrected |
Uncorrectables |
|||||||
|
44 |
Locked |
QAM256 |
645000000 Hz |
-6 dBmV |
42 dB |
551486 |
370121 |
|||||||
|
13 |
Locked |
QAM256 |
459000000 Hz |
-6 dBmV |
43 dB |
40 |
0 |
|||||||
|
14 |
Locked |
QAM256 |
465000000 Hz |
-6 dBmV |
42 dB |
4209 |
3838 |
|||||||
|
15 |
Locked |
QAM256 |
471000000 Hz |
-6 dBmV |
43 dB |
9 |
0 |
|||||||
|
16 |
Locked |
QAM256 |
477000000 Hz |
-6 dBmV |
43 dB |
6 |
0 |
|||||||
|
17 |
Locked |
Unknown |
483000000 Hz |
-6 dBmV |
0 dB |
1642 |
52449 |
|||||||
|
18 |
Locked |
QAM256 |
489000000 Hz |
-6 dBmV |
30 dB |
477856 |
52449 |
|||||||
|
19 |
Locked |
QAM256 |
495000000 Hz |
-6 dBmV |
43 dB |
3 |
0 |
|||||||
|
20 |
Locked |
QAM256 |
501000000 Hz |
-6 dBmV |
43 dB |
3 |
0 |
|||||||
|
21 |
Locked |
QAM256 |
507000000 Hz |
-6 dBmV |
43 dB |
3 |
0 |
|||||||
|
22 |
Locked |
QAM256 |
513000000 Hz |
-6 dBmV |
43 dB |
3 |
0 |
|||||||
|
23 |
Locked |
QAM256 |
519000000 Hz |
-6 dBmV |
40 dB |
5 |
0 |
|||||||
|
24 |
Locked |
Unknown |
525000000 Hz |
-6 dBmV |
0 dB |
6292492 |
3229 |
|||||||
|
25 |
Locked |
Unknown |
531000000 Hz |
-6 dBmV |
0 dB |
552398 |
0 |
|||||||
|
26 |
Locked |
QAM256 |
537000000 Hz |
-6 dBmV |
0 dB |
26250943 |
0 |
|||||||
|
27 |
Locked |
QAM256 |
543000000 Hz |
-7 dBmV |
34 dB |
30782 |
3229 |
|||||||
|
28 |
Locked |
QAM256 |
549000000 Hz |
-6 dBmV |
43 dB |
10 |
0 |
|||||||
|
29 |
Locked |
QAM256 |
555000000 Hz |
-6 dBmV |
41 dB |
20 |
0 |
|||||||
|
30 |
Locked |
QAM256 |
561000000 Hz |
-6 dBmV |
41 dB |
1 |
0 |
|||||||
|
31 |
Locked |
QAM256 |
567000000 Hz |
-6 dBmV |
31 dB |
3233016 |
1877736 |
|||||||
|
32 |
Locked |
QAM256 |
573000000 Hz |
-6 dBmV |
32 dB |
483806 |
62005 |
|||||||
|
33 |
Locked |
QAM256 |
579000000 Hz |
-6 dBmV |
35 dB |
4872 |
12 |
|||||||
|
34 |
Locked |
QAM256 |
585000000 Hz |
-6 dBmV |
43 dB |
3 |
0 |
|||||||
|
35 |
Locked |
QAM256 |
591000000 Hz |
-6 dBmV |
40 dB |
3 |
0 |
|||||||
|
36 |
Locked |
QAM256 |
597000000 Hz |
-6 dBmV |
38 dB |
3 |
0 |
|||||||
|
37 |
Locked |
Unknown |
603000000 Hz |
-6 dBmV |
0 dB |
0 |
472869 |
|||||||
|
38 |
Locked |
Unknown |
609000000 Hz |
-6 dBmV |
0 dB |
0 |
3718208 |
|||||||
|
39 |
Locked |
QAM256 |
615000000 Hz |
-6 dBmV |
35 dB |
2169045 |
261614 |
|||||||
|
40 |
Locked |
QAM256 |
621000000 Hz |
-6 dBmV |
28 dB |
17506479 |
23307554 |
|||||||
|
41 |
Locked |
QAM256 |
627000000 Hz |
-6 dBmV |
37 dB |
2784607 |
1915042 |
|||||||
|
42 |
Locked |
QAM256 |
633000000 Hz |
-6 dBmV |
37 dB |
1344618 |
479970 |
|||||||
|
43 |
Locked |
QAM256 |
639000000 Hz |
-6 dBmV |
35 dB |
2850674 |
4635800 |
|||||||
|
193 |
Locked |
OFDM PLC |
722000000 Hz |
-4 dBmV |
43 dB |
17890430 |
418 |
|||||||
|
194 |
Locked |
OFDM PLC |
957000000 Hz |
-5 dBmV |
42 dB |
20724401 |
302 |
|||||||
|
pstream Bonded Channels |
||||||||||||||
|
Channel ID |
Lock Status |
US Channel Type |
Frequency |
Width |
Power |
|||||||||
|
1 |
Locked |
SC-QAM |
16400000 Hz |
6400000 |
46.8 dBmV |
|||||||||
|
2 |
Locked |
SC-QAM |
22800000 Hz |
6400000 |
47.3 dBmV |
|||||||||
|
3 |
Locked |
SC-QAM |
29200000 Hz |
6400000 |
47.5 dBmV |
|||||||||
|
4 |
Locked |
SC-QAM |
35600000 Hz |
6400000 |
47.8 dBmV |
|||||||||
Event Log
|
19/2/2025 |
5 |
MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
6 |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 40; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
5 |
MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
6 |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 40; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
Successful LAN WebGUI login from 76.28.134.185 on 25/02/19 at 4:55 PM. |
|
19/2/2025 |
6 |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
5 |
MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
6 |
CM-STATUS message sent. Event Type Code: 2; Chan ID: 26; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
5 |
MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
UCD invalid or channel unusable;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
6 |
Overriding MDD IP initialization parameters; IP provisioning mode = IPv4 |
|
19/2/2025 |
5 |
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
5 |
ToD request sent - No Response received;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
6 |
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
6 |
DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
3 |
UCD invalid or channel unusable;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
4 |
D31 Secure software download can't start, Time of Day has not completed. |
|
19/2/2025 |
5 |
MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
6 |
SW Download INIT - Via Config file d11_m_s33_gigx2nocert_c01.cm |
|
19/2/2025 |
5 |
MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
|
19/2/2025 |
6 |
CM-STATUS message sent. Event Type Code: 2; Chan ID: 24 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1; |
BruceW
Gold Problem Solver
•
26.2K Messages
1 day ago
The downstream power levels, SNR values, and error counts are scattered in an odd way. Some are in spec, and some are not. The event log indicates a problem with the link between your modem and Comcast's network. Network connection problems 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.
0
0