Visitor
•
3 Messages
Spotty Connection
I keep losing internet and my event log has constant problems on. I don't really follow what the problem is but I believe there's something wrong with my cables.
can anyone give me some suggestions?
| 06:07:25 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:09:10 Sun May 2 2021 |
Warning (5) | MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:09:16 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; 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; | |||
| 06:09:17 Sun May 2 2021 |
Warning (5) | MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:09:36 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; 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; | |||
| 06:09:41 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; 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; | |||
| 06:09:46 Sun May 2 2021 |
Warning (5) | MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:09:57 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; 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; | |||
| 06:10:08 Sun May 2 2021 |
Warning (5) | MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:10:20 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; 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; | |||
| 06:44:08 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:44:35 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:45:05 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:45:50 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:50:46 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 06:51:19 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:19:29 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:19:56 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:25:32 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:26:02 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:38:00 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:38:28 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:39:52 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:40:21 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:50:01 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:50:05 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:50:28 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:50:45 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:55:29 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:56:04 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:56:51 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; | |||
| 07:57:21 Sun May 2 2021 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |



EG
Expert
•
117.1K Messages
5 years ago
Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
What is the exact make and model number of the modem ?
Is this a WiFi connection ?
1
user_60cfd6
Visitor
•
3 Messages
5 years ago
3
0
hanks424
Contributor
•
27 Messages
5 years ago
Same issue here. Modem restarts, thousands of uncorrectable codewords, TVs all go blank, lots of T3s, SNR 42 dB. We have no splitters, just an EVO1 amp installed by Comcast many years ago.
Took 1 week to get service call, tech called me and said everything looks OK on his end, if he came out there would be a service charge. Same thing happened 18 months ago and finally corrected by Maintenance (pole top amp several blocks away). We live in an area with many people gone for the summer, hence not a lot of complaints.
The tech told me if he cannot see the problem he cannot refer to maintenance. So you are out of luck if you have a transient issue. This is unacceptable.
(edited)
0
0
hanks424
Contributor
•
27 Messages
5 years ago
Downstream Bonded Channels
Channel
Lock Status
Modulation
Channel ID
Frequency
Power
SNR / MER
Unerrored Codewords
Correctable Codewords
Uncorrectable Codewords
1
Locked
QAM256
5
501000000 Hz
3.2 dBmV
42.6 dB
4234931542
13066
7829
2
Locked
QAM256
1
477000000 Hz
2.7 dBmV
42.2 dB
4233194262
16776
8234
3
Locked
QAM256
2
483000000 Hz
2.8 dBmV
42.3 dB
4233204104
17701
7443
4
Locked
QAM256
3
489000000 Hz
3.0 dBmV
42.5 dB
4233217133
16125
8082
5
Locked
QAM256
4
495000000 Hz
3.0 dBmV
42.5 dB
4233233740
14433
7164
6
Locked
QAM256
6
507000000 Hz
3.4 dBmV
42.7 dB
4233252693
8991
7077
7
Locked
QAM256
7
513000000 Hz
3.4 dBmV
42.7 dB
4233265481
11522
7204
8
Locked
QAM256
8
519000000 Hz
3.6 dBmV
42.7 dB
4233280305
8039
7210
9
Locked
QAM256
9
525000000 Hz
3.7 dBmV
42.9 dB
4233302779
8303
6771
10
Locked
QAM256
10
531000000 Hz
3.9 dBmV
42.9 dB
4233320977
7503
6498
11
Locked
QAM256
11
537000000 Hz
3.9 dBmV
42.9 dB
4233335796
6478
6411
12
Locked
QAM256
12
543000000 Hz
3.9 dBmV
42.8 dB
4233344877
9811
6591
13
Locked
QAM256
13
555000000 Hz
4.0 dBmV
42.9 dB
4233355612
6130
6184
14
Locked
QAM256
14
561000000 Hz
4.1 dBmV
43.1 dB
4233370709
5793
6192
15
Locked
QAM256
15
567000000 Hz
4.0 dBmV
42.9 dB
4233387466
5212
6225
16
Locked
QAM256
16
573000000 Hz
4.1 dBmV
42.8 dB
4233399534
5571
6156
17
Locked
QAM256
17
579000000 Hz
4.1 dBmV
42.8 dB
4233414759
4777
6192
18
Locked
QAM256
18
585000000 Hz
4.3 dBmV
43.0 dB
4233412664
4861
5945
19
Locked
QAM256
19
591000000 Hz
4.6 dBmV
42.9 dB
4233420012
4629
6136
20
Locked
QAM256
33
423000000 Hz
1.9 dBmV
41.8 dB
4233368161
36471
9058
21
Locked
QAM256
34
429000000 Hz
1.9 dBmV
41.9 dB
4233384489
33229
8892
22
Locked
QAM256
35
435000000 Hz
1.9 dBmV
41.8 dB
4233398829
33249
8588
23
Locked
QAM256
36
441000000 Hz
2.0 dBmV
42.0 dB
4233403091
38881
11124
24
Locked
QAM256
37
453000000 Hz
2.2 dBmV
41.8 dB
4233427937
25907
8083
25
Locked
QAM256
38
459000000 Hz
2.2 dBmV
41.8 dB
4233446741
26902
7975
26
Locked
QAM256
39
465000000 Hz
2.5 dBmV
41.9 dB
4233465384
21660
8043
27
Locked
QAM256
40
471000000 Hz
2.4 dBmV
42.0 dB
4233478000
22561
7935
28
Locked
QAM256
42
399000000 Hz
2.0 dBmV
42.0 dB
4233468534
39600
11336
29
Locked
QAM256
43
405000000 Hz
1.9 dBmV
41.8 dB
4233511178
37224
9812
30
Locked
QAM256
44
411000000 Hz
1.7 dBmV
41.9 dB
4233494322
40201
10798
31
Locked
QAM256
45
417000000 Hz
1.7 dBmV
41.8 dB
4233509511
33985
8856
32
Not Locked
Unknown
0
0 Hz
0.0 dBmV
0.0 dB
0
0
0
0
0
hanks424
Contributor
•
27 Messages
5 years ago
THE Problem continues. Second service call scheduled.
Time Priority Description
2021-07-04, 12:55:54 Notice (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;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2021-07-04, 06:57:43 Critical (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;
2021-07-04, 06:57:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2021-07-04, 06:57:43 Critical (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;
2021-07-04, 06:57:42 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2021-07-04, 06:57:40 Critical (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;
2021-07-04, 06:46:10 Critical (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;
2021-07-04, 06:46:08 Critical (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;
2021-07-04, 06:46:03 Critical (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;
2021-07-03, 10:14:29 Critical (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;
2021-07-03, 10:14:27 Critical (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;
2021-07-03, 09:14:24 Critical (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;
2021-07-03, 09:14:23 Critical (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;
2021-07-03, 08:16:37 Critical (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;
2021-07-03, 07:43:51 Critical (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;
2021-07-03, 06:14:05 Critical (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;
2021-07-02, 11:49:37 Critical (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;
2021-07-02, 11:49:37 Critical (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;
2021-07-02, 07:49:40 Critical (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;
2021-07-02, 06:39:52 Critical (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;
2021-07-01, 09:15:16 Critical (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;
2021-07-01, 09:12:38 Critical (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;
2021-07-01, 08:50:04 Critical (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;
2021-07-01, 08:50:04 Critical (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;
2021-07-01, 08:26:33 Critical (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;
2021-07-01, 08:26:27
(edited)
2
0
hanks424
Contributor
•
27 Messages
5 years ago
Why can't Xfinity resolve this? It's like pulling teeth to get a tech out. "As long as your service is 'working' we won't send a tech"
I have never had an issue like this; been customer since 1996. you are out of luck if you have a transient issue
BTW, Xfinity reports that my modem is not visible.
(edited)
0
0
hanks424
Contributor
•
27 Messages
5 years ago
Connection just dropped again today. Does anyone from Infinity monitor this board?
5
0
hanks424
Contributor
•
27 Messages
5 years ago
Closed Firefox and started Chrome -- Same result... NO Icons
This is crazy
1
0
hanks424
Contributor
•
27 Messages
5 years ago
Yes I can view my profile but no icon for chat. I have a second tech scheduled in a few days. Here's what will happen - they will measure signal, tell me nothing wrong, can't defer to maintenance until they can see problem. He may hit us with a service charge (which I will never pay). After he leaves, the problem will continue until someone takes the initiative to troubleshoot intermittents on the node.
Again, look at the T3 timeouts, and high SNRs, modem resets, etc. This is not rocket science.
I have wasted way too much time with Xfinity on this matter. Look at the results I have posted in this thread... FEEDBACK??
1
0
hanks424
Contributor
•
27 Messages
5 years ago
2
021-07-06, 15:09:13
Notice (6)
CM-STATUS message sent. Event Type Code: 8; Chan ID: 7; DSID: N/A; MAC Addr: N/A; CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2021-07-06, 15:08:45
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-CM-QOS=1.1;CM-VER=3.1;
2021-07-06, 15:08:29
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=
2021-07-06, 15:08:28
Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-;CM-VER=3.1;
2021-07-06, 15:08:28
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;-VER=3.1;
2021-07-06, 10:34:59
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MACVER=3.1;
2021-07-06, 10:34:59
Warning (5)
Dynamic Range Window violation
0
0
hanks424
Contributor
•
27 Messages
5 years ago
Comcast Jen: UPDATE Problem is fixed.
2nd tech replaced an old damaged service drop (see photo) and fitted a new passive splitter. PROBLEM FIXED. Tech very attentive and should be given a raise!
The first tech never bothered to show up, calling me the morning of the appointment, telling me (remotely) the service looks good, and there would be a service charge if he didn't find a problem and I should cancel the appointment. He could have cared less about intermittent dropped connections. Because of him we had to endure another week of poor service and almost switched providers. The difference between the two techs was night and day. I pity Xfinity customers who are unlucky enough to get the original tech.
ComcastJen You should show my comments to management. Because of the great work of the second tech I am happy to recommend Xfinity.
(edited)
5
0