Contributor
•
19 Messages
Arris S33 Intermitten Connection Issues - Need Help
I upgraded to a new Arris modem a couple months ago and i've been having to reset the modem on average 1-2 times per week. Today however, I've had to do it three times. This is not an issue with the connection, but clearly an issue with the modem specifically, or something else related to it and my service. We had a technician come out to our house several years ago who cleaned up all the lines and removed any other splitters and/or filters from the main box. There are no additional splitters or filters coming to the modem, the line goes directly from our connection on the side of the house, into the modem. Nothing has changed over the years.
Here is the event log
31/12/1969 16:00:38 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:00:38 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:15 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:20 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:37 |
3 | No Ranging Response received - T3 time-out;CM-MAC=<Edited: PII>CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:01:00 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:01:00 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:01:00 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:16 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:19 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:42 |
3 | No Ranging Response received - T3 time-out;CM-MAC=<Edited: PII>;CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:01:01 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:01:01 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:01:01 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:16 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:20 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:25 |
3 | No Ranging Response received - T3 time-out;CM-MAC=<Edited: PII>;CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:40 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:00:40 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:00:40 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:15 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:19 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:58 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:00:58 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:00:58 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:16 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:19 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:38 |
3 | No Ranging Response received - T3 time-out;CM-MAC=<Edited: PII>;CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:01:03 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:01:03 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:01:03 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:15 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:20 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:22 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:22 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:22 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:41 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:00:41 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:00:41 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:15 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:19 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:45 |
3 | No Ranging Response received - T3 time-out;CM-MAC=<Edited: PII>;CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:01:02 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:01:02 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:01:02 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:15 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:19 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:21 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:40 |
3 | No Ranging Response received - T3 time-out;CM-MAC=<Edited: PII>;CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:59 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:00:59 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:00:59 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:16 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:19 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:20 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:20 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:20 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:40 |
3 | No Ranging Response received - T3 time-out;CM-MAC=<Edited: PII>;CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:58 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:00:58 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:00:58 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
31/12/1969 16:00:15 |
3 | CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz. |
31/12/1969 16:00:20 |
3 | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<Edited: PII>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:22 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
31/12/1969 16:00:22 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
31/12/1969 16:00:22 |
3 | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz. |
31/12/1969 16:00:41 |
3 | No Ranging Response received - T3 time-out;CM-MAC=<Edited: PII>CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
31/12/1969 16:00:55 |
6 | Honoring MDD; IP provisioning mode = IPv6 |
31/12/1969 16:01:05 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
31/12/1969 16:01:05 |
3 | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
31/12/1969 16:01:05 |
3 | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
23/12/2022 14:54:31 |
6 | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=<Edited: PII>;CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
23/12/2022 14:54:36 |
5 | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=<Edited: PII>;CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
23/12/2022 14:54:36 |
5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=<Edited: PII>CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
23/12/2022 14:54:36 |
5 | Dynamic Range Window violation |
23/12/2022 14:54:36 |
5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=<Edited: PII>;CMTS-MAC=<Edited: PII>;CM-QOS=1.1;CM-VER=3.1; |
23/12/2022 14:54:36 |
5 | Dynamic Range Window violation |
23/12/2022 15:02:38 |
3 | Failed LAN WebGUI login attempt from 67.170.24.149 on 22/12/23 at 3:02 PM. |
23/12/2022 15:03:06 |
3 | Failed LAN WebGUI login attempt from 67.170.24.149 on 22/12/23 at 3:03 PM. |
23/12/2022 15:03:13 |
3 | Successful LAN WebGUI login from 67.170.24.149 on 22/12/23 at 3:03 PM. |
Downstream Channels
Channel ID | Lock Status | Modulation | Frequency | Power | SNR/MER | Corrected | Uncorrectables |
41 | Locked | QAM256 | 675000000 Hz | 3 dBmV | 38 dB | 7 | 0 |
13 | Locked | QAM256 | 495000000 Hz | 5 dBmV | 41 dB | 0 | 0 |
14 | Locked | QAM256 | 507000000 Hz | 5 dBmV | 41 dB | 0 | 0 |
15 | Locked | QAM256 | 513000000 Hz | 5 dBmV | 41 dB | 0 | 0 |
16 | Locked | QAM256 | 519000000 Hz | 5 dBmV | 41 dB | 0 | 0 |
17 | Locked | QAM256 | 525000000 Hz | 5 dBmV | 41 dB | 0 | 0 |
18 | Locked | QAM256 | 531000000 Hz | 4 dBmV | 41 dB | 0 | 0 |
19 | Locked | QAM256 | 543000000 Hz | 4 dBmV | 41 dB | 0 | 0 |
20 | Locked | QAM256 | 549000000 Hz | 4 dBmV | 41 dB | 0 | 0 |
21 | Locked | QAM256 | 555000000 Hz | 4 dBmV | 41 dB | 0 | 0 |
22 | Locked | QAM256 | 561000000 Hz | 4 dBmV | 41 dB | 0 | 0 |
23 | Locked | QAM256 | 567000000 Hz | 4 dBmV | 41 dB | 0 | 0 |
24 | Locked | QAM256 | 573000000 Hz | 4 dBmV | 40 dB | 0 | 0 |
25 | Locked | QAM256 | 579000000 Hz | 3 dBmV | 40 dB | 1 | 0 |
26 | Locked | QAM256 | 585000000 Hz | 3 dBmV | 40 dB | 1 | 0 |
27 | Locked | QAM256 | 591000000 Hz | 3 dBmV | 40 dB | 2 | 0 |
28 | Locked | QAM256 | 597000000 Hz | 3 dBmV | 40 dB | 1 | 0 |
29 | Locked | QAM256 | 603000000 Hz | 3 dBmV | 40 dB | 3 | 0 |
30 | Locked | QAM256 | 609000000 Hz | 3 dBmV | 40 dB | 1 | 0 |
31 | Locked | QAM256 | 615000000 Hz | 3 dBmV | 40 dB | 1 | 0 |
32 | Locked | QAM256 | 621000000 Hz | 3 dBmV | 40 dB | 1 | 0 |
33 | Locked | QAM256 | 627000000 Hz | 3 dBmV | 40 dB | 1 | 0 |
34 | Locked | QAM256 | 633000000 Hz | 3 dBmV | 39 dB | 4 | 0 |
35 | Locked | QAM256 | 639000000 Hz | 3 dBmV | 39 dB | 3 | 0 |
36 | Locked | QAM256 | 645000000 Hz | 3 dBmV | 39 dB | 8 | 0 |
37 | Locked | QAM256 | 651000000 Hz | 3 dBmV | 39 dB | 5 | 0 |
38 | Locked | QAM256 | 657000000 Hz | 3 dBmV | 39 dB | 6 | 0 |
39 | Locked | QAM256 | 663000000 Hz | 2 dBmV | 39 dB | 7 | 0 |
40 | Locked | QAM256 | 669000000 Hz | 3 dBmV | 39 dB | 5 | 0 |
42 | Locked | QAM256 | 681000000 Hz | 2 dBmV | 39 dB | 4 | 0 |
43 | Locked | QAM256 | 687000000 Hz | 2 dBmV | 39 dB | 6 | 0 |
44 | Locked | QAM256 | 693000000 Hz | 2 dBmV | 39 dB | 10 | 0 |
159 |
Locked | OFDM PLC | 722000000 Hz | 3 dBmV | 39 dB | 5519520 | 0 |
Upstream Channels
Channel ID | Lock Status | US Channel Type | Frequency | Width | Power |
1 | Locked | SC-QAM | 10400000 Hz | 3200000 | 42.0 dBmV |
2 | Locked | SC-QAM | 16400000 Hz | 6400000 | 41.5 dBmV |
3 | Locked | SC-QAM | 22800000 Hz | 6400000 | 42.5 dBmV |
4 | Locked | SC-QAM | 29200000 Hz | 6400000 | 42.5 dBmV |
5 | Locked | SC-QAM | 35600000 Hz | 6400000 | 42.5 dBmV |
6 | Locked | SC-QAM | 40400000 Hz | 3200000 | 44.5 dBmV |
m_designs
Contributor
•
19 Messages
2 years ago
Annnnnnd I just had to restart it, again. This is the 4th time today.
2
0
BruceW
Gold Problem Solver
•
26.3K Messages
2 years ago
The signal stats you posted all look good, but there are other stats that the modem does not report, and the event log indicates that the modem is having trouble communicating with Comcast. 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, 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 ($70-$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.
2
0
m_designs
Contributor
•
19 Messages
2 years ago
Updated Event Log
16:00:37
16:01:00
16:01:00
16:01:00
16:00:16
16:00:19
16:00:21
16:00:21
16:00:21
16:00:42
16:01:01
16:01:01
16:01:01
16:00:16
16:00:20
16:00:21
16:00:21
16:00:21
16:00:25
16:00:40
16:00:40
16:00:40
16:00:15
16:00:19
16:00:21
16:00:21
16:00:21
16:00:58
16:00:58
16:00:58
16:00:16
16:00:19
16:00:21
16:00:21
16:00:21
16:00:38
16:01:03
16:01:03
16:01:03
16:00:15
16:00:20
16:00:22
16:00:22
16:00:22
16:00:41
16:00:41
16:00:41
16:00:15
16:00:19
16:00:21
16:00:21
16:00:21
16:00:45
16:01:02
16:01:02
16:01:02
16:00:15
16:00:19
16:00:21
16:00:21
16:00:21
16:00:40
16:00:59
16:00:59
16:00:59
16:00:16
16:00:19
16:00:20
16:00:20
16:00:20
16:00:40
16:00:58
16:00:58
16:00:58
16:00:15
16:00:20
16:00:22
16:00:22
16:00:22
16:00:41
16:01:05
16:01:05
16:01:05
15:02:38
15:03:06
15:03:13
16:00:16
16:00:19
16:00:21
16:00:21
16:00:21
16:00:35
16:00:50
16:01:00
16:01:00
16:01:00
15:25:14
15:25:19
10:28:45
10:28:49
(edited)
0
0
m_designs
Contributor
•
19 Messages
2 years ago
So an update.
After chatting with Xfinity, a reset signal was sent to my modem. I'm not sure if that will resolve this issue so I went ahead and decided to return the modem. I purchased a Motorola MB8611 and installed it this morning. After activation, the internet was up and running fine for a few hours, then the modem reset, connection went down, and this is in the error log.
Thu Dec 29 2022
Thu Dec 29 2022
Thu Dec 29 2022
Thu Dec 29 2022
(edited)
1
0
EG
Expert
•
110K Messages
2 years ago
@m_designs
Your last two posts were marked as being "Private" by the forum software because they contain CM MAC and the CMTS MAC addresses. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. Please redact them and your posts will be made publically viewable again.
1
0
m_designs
Contributor
•
19 Messages
2 years ago
At the time of this post, the new Motorola MB8611 has failed five times since setting up and activating this morning. Similar persistent disconnection issue the S33 had, but worse. The one saving grace with the Motorola is that it automatically restarts itself to regain connection. I decided to try and install my older modem, the Arris SB6190 to try and at least have reliable connection, and after activation, would not work. The Xfinity App says it was activated and connected, but i was not getting any juice flowing.
Then I received a call from an overseas "advanced" technical support agent, who just asked me all the same basic questions just to confirm a tech needed to be sent on my scheduled appointment.
I have since reactivated the Motorola modem, hoping that it stays online for more than 30 minutes at a time.
0
0
m_designs
Contributor
•
19 Messages
2 years ago
Latest update, 1/6/23
on 12/29 I decided to attempt to install and reactivate my older SB6190 modem. After a successful activation, i was not getting any internet. No idea why - it just wouldn't work. Rather than having no internet at all, i decided to give the Motorola MB8611 another shot. After another successful activation, i experienced no issues.
on 12/31 i had a field tech support agent come out and inspect the lines. He didn't see anything wrong, and even spoke with an area node support tech who said the area has been good. He replaced a few fittings and inspected the main box just to be safe and said that the signals in and out have been some of the best he's seen lately. Since reactivation, I haven't had any issues until yesterday morning, and then again this morning. Both instances, the modem failed it's upstream connection, following details:
Since yesterday, the modem has failed connection three times in the past 24 hours.
Fri Jan 6 2023
Fri Jan 6 2023
Fri Jan 6 2023
Fri Jan 6 2023
0
0