Contributor
•
17 Messages
Frequent disconnects continue after replacing cable modem
I was having very frequent disconnects with my previous cable modem that was several years old. It was disconnecting several times a day every day and taking several minutes to reconnect.
I thought maybe it was going bad. So, I purchased a new S33 modem.
I saw an improvement. Now it only disconnects for short periods a few days a week, but this is still and issue.
It appears there is a line issue and the new modem is just handling and working through the issue better than the old one.
What can be done about this?
This is what I see in the logs:
Startup Procedure | ||
---|---|---|
Procedure | Status | Comment |
Acquire Downstream Channel | 375000000 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 | 375000000 Hz | 10 dBmV | 39 dB | 89619 | 121103 |
5 | Locked | QAM256 | 381000000 Hz | 10 dBmV | 39 dB | 166153 | 184609 |
6 | Locked | QAM256 | 387000000 Hz | 10 dBmV | 39 dB | 171033 | 215367 |
7 | Locked | QAM256 | 393000000 Hz | 10 dBmV | 39 dB | 155710 | 175093 |
8 | Locked | QAM256 | 399000000 Hz | 10 dBmV | 39 dB | 154190 | 182482 |
9 | Locked | QAM256 | 405000000 Hz | 10 dBmV | 39 dB | 161087 | 197392 |
10 | Locked | QAM256 | 411000000 Hz | 10 dBmV | 39 dB | 139461 | 166624 |
11 | Locked | QAM256 | 417000000 Hz | 10 dBmV | 39 dB | 147065 | 181036 |
12 | Locked | QAM256 | 423000000 Hz | 10 dBmV | 39 dB | 142726 | 173932 |
13 | Locked | QAM256 | 429000000 Hz | 10 dBmV | 39 dB | 133730 | 171793 |
14 | Locked | QAM256 | 435000000 Hz | 10 dBmV | 39 dB | 129211 | 153313 |
15 | Locked | QAM256 | 441000000 Hz | 10 dBmV | 39 dB | 129786 | 161413 |
16 | Locked | QAM256 | 447000000 Hz | 9 dBmV | 39 dB | 131674 | 171814 |
17 | Locked | QAM256 | 453000000 Hz | 9 dBmV | 39 dB | 116681 | 134997 |
18 | Locked | QAM256 | 459000000 Hz | 9 dBmV | 38 dB | 126767 | 165061 |
19 | Locked | QAM256 | 465000000 Hz | 9 dBmV | 38 dB | 130574 | 158511 |
20 | Locked | QAM256 | 471000000 Hz | 9 dBmV | 38 dB | 109564 | 130799 |
21 | Locked | QAM256 | 477000000 Hz | 9 dBmV | 38 dB | 111438 | 144032 |
22 | Locked | QAM256 | 483000000 Hz | 9 dBmV | 38 dB | 104566 | 140556 |
23 | Locked | QAM256 | 489000000 Hz | 9 dBmV | 38 dB | 99370 | 137081 |
24 | Locked | QAM256 | 495000000 Hz | 9 dBmV | 38 dB | 98874 | 122404 |
25 | Locked | QAM256 | 501000000 Hz | 9 dBmV | 38 dB | 95285 | 140825 |
26 | Locked | QAM256 | 507000000 Hz | 9 dBmV | 38 dB | 91153 | 125956 |
27 | Locked | QAM256 | 513000000 Hz | 9 dBmV | 37 dB | 88901 | 112090 |
28 | Locked | QAM256 | 519000000 Hz | 9 dBmV | 37 dB | 91957 | 139472 |
29 | Locked | QAM256 | 525000000 Hz | 9 dBmV | 36 dB | 79854 | 113664 |
30 | Locked | QAM256 | 531000000 Hz | 9 dBmV | 36 dB | 82811 | 114426 |
31 | Locked | QAM256 | 537000000 Hz | 9 dBmV | 36 dB | 84354 | 118559 |
32 | Locked | QAM256 | 543000000 Hz | 9 dBmV | 36 dB | 78596 | 110309 |
33 | Locked | QAM256 | 549000000 Hz | 9 dBmV | 37 dB | 77171 | 110411 |
34 | Locked | QAM256 | 555000000 Hz | 9 dBmV | 39 dB | 69863 | 110749 |
48 | Locked | OFDM PLC | 685000000 Hz | 8 dBmV | 39 dB | 2297451631 | 118941 |
Upstream Bonded Channels | ||||||
---|---|---|---|---|---|---|
Channel ID | Lock Status | US Channel Type | Frequency | Width | Power | |
1 | Locked | SC-QAM | 10400000 Hz | 3200000 | 43.5 dBmV | |
2 | Locked | SC-QAM | 16400000 Hz | 6400000 | 46.5 dBmV | |
3 | Locked | SC-QAM | 22800000 Hz | 6400000 | 46.5 dBmV | |
4 | Locked | SC-QAM | 29200000 Hz | 6400000 | 46.5 dBmV | |
5 | Locked | SC-QAM | 35600000 Hz | 6400000 | 55.0 dBmV | |
6 | Locked | SC-QAM | 40400000 Hz | 3200000 | 55.0 dBmV |
Current System Time:Tue Sep 6 09:39:32 2022
6/9/2022
07:34:16 5 Dynamic Range Window violation
6/9/2022
08:55:30 3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;
6/9/2022
08:55:30 5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;
6/9/2022
08:55:30 5 Dynamic Range Window violation
6/9/2022
08:55:30 5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;
6/9/2022
08:55:30 5 Dynamic Range Window violation
6/9/2022
08:55:30 5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;
6/9/2022
08:55:30 5 Dynamic Range Window violation
6/9/2022
08:55:30 5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;
6/9/2022
08:55:30 5 Dynamic Range Window violation
6/9/2022
08:55:30 5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;
6/9/2022
08:55:30 5 Dynamic Range Window violation
6/9/2022
08:55:31 3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;
6/9/2022
08:55:31 5 RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=;
6/9/2022
08:55:31 5 Dynamic Range Window violation
6/9/2022
08:55:31 3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;
6/9/2022
09:12:27 3 Successful LAN WebGUI login from on 22/09/06 at 9:12 AM.
Current System Time:Tue Sep 6 09:22:27 2022
flatlander3
Problem Solver
•
1.5K Messages
3 years ago
Yep. That's a mess. Downstream high. Upstream pushing too much to get out. Uncorrectable errors all over the place. You need a tech to check the line out, but in the mean time while you are waiting, take a look here: https://forums.xfinity.com/conversations/your-home-network/internet-troubleshooting-tips/602dae4ac5375f08cde52ea0
You are looking for splitters, connector problems, bends, kinks in the line.....etc
0
0
rancho100
Contributor
•
17 Messages
3 years ago
I don't have TV service. So it is only one Comcast device plugged in.
The cable comes in from outside to a closet that splits to each room, but since there is no service connected to other rooms, it just goes has a connector to attach it to the one room with the cable modem.
0
0
flatlander3
Problem Solver
•
1.5K Messages
3 years ago
It could be a problem upstream from your place if your connectors are good. In that case, you don't pay for the tech visit and it's Xfinity's problem. I'm surprised it's not spontaneously rebooting all the time from the high upstream. There is something funky going on.
You probably have to chat with them (autobot) to schedule a tech. I see they removed their phone number from here: https://www.xfinity.com/support/internet#get-started
0
0
rancho100
Contributor
•
17 Messages
3 years ago
The old modem would freeze and I would need to unplug it and reconnect it several times per week.
This one has still manages to stay online 99% of the time and it resets itself without manual intervention.
0
0
rancho100
Contributor
•
17 Messages
3 years ago
I just tried moving the cable modem and router so that I could plug it directly into the line that comes in from outside so that it would not have to pass though multiple cables and another wall jack
This is what it looks like now. Is this much better or does this indicate that the problem is coming from outside?
What should it look like when it's working well?
The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.
Current System Time:Wed Sep 7 10:03:04 2022
0
0
rancho100
Contributor
•
17 Messages
3 years ago
After moving it back to the original location it's showing 0s again. It may just be temporary though.
2
0
flatlander3
Problem Solver
•
1.5K Messages
3 years ago
Better.
From the 1st troubleshooting link above:
Downstream power:
Gateways and EMTAs -7dBmV +7dBmV
Downstream Signal to Noise Ratio 35dB -
Upstream Power Level +35dBmV +50dBmV
Upstream Signal to Noise Ratio 31dB
So, you're a bit high on downstream power. You also still got un-correctable errors. A few are OK over time. You got a lot. Upstream looks better an isn't pushing into the 55+dBmV range.
If you still have dropout issues, or your gear is rebooting with just a straight connection, you just have the line in from the street and a connector left for a tech to test. If it's working fine, then keep an eye on it for a few days. The values are just a snapshot in time and may vary quite a bit. You can try taking the connectors apart and scuffing the copper connector up with sand paper a bit to remove oxidation. Maybe it will clean up.
Uncorrectables just force a TCP/IP re-transmit. It's not ideal, but you might not notice anything as a human. They happen pretty fast.
*edit: might have crossed in the middle there. I didn't see the 2nd one. That one looks better, but let it run over time to see what it says.
(edited)
0
0
rancho100
Contributor
•
17 Messages
3 years ago
The uncorrectables at 0 did not last very long.
I have just sent a direct message to Xfinity Support.
How do they contact me?
Current System Time:Fri Sep 9 09:14:58 2022
0
0
rancho100
Contributor
•
17 Messages
3 years ago
I just rechecked and I see Xfinity Support replied to the message.
It is kind of hard to follow it, when I don't get any kind of notification or email so I know they replied without revisiting the web page to check on it.
0
0