Contributor
•
17 Messages
intermittent desyncs and disconnects getting worse
Suddenly in the last few weeks I've been experiencing intermittent desyncs and brief disconnects.
Prior to this time, I couldn't tell you when I last had issues beyond the rare widespread service outage.
The current issues seem "streaky", in that I can go hours with no issues at all, then suddenly I'm plagued with them every few minutes for an hour or two or more.
In the last couple of days it seems to be much worse, though that's anecdotal as I have not been keeping detailed logs throughout this period.
Any insight into what the problem might be is greatly appreciated!
Cable Modem: MB8600
DOWNSTREAM
Channel | Lock Status | Modulation | Channel ID | Freq. (MHz) | Pwr (dBmV) | SNR (dB) | Corrected | Uncorrected |
1 | Locked | QAM256 | 42 | 405 | 11.3 | 43.9 | 10990 | 7838 |
2 | Locked | QAM256 | 1 | 453 | 9.8 | 43.3 | 6608 | 4570 |
3 | Locked | QAM256 | 2 | 459 | 10.1 | 43.3 | 5841 | 5463 |
4 | Locked | QAM256 | 3 | 465 | 10 | 43.3 | 4687 | 4230 |
5 | Locked | QAM256 | 4 | 471 | 9.7 | 43 | 5681 | 5055 |
6 | Locked | QAM256 | 5 | 477 | 9.7 | 43 | 5040 | 4881 |
7 | Locked | QAM256 | 6 | 483 | 9.8 | 43.1 | 3735 | 3075 |
8 | Locked | QAM256 | 7 | 489 | 10 | 43.1 | 4345 | 4589 |
9 | Locked | QAM256 | 8 | 495 | 10 | 43 | 4661 | 4774 |
10 | Locked | QAM256 | 9 | 507 | 10.3 | 43 | 3739 | 3728 |
11 | Locked | QAM256 | 10 | 513 | 10.6 | 43.4 | 3161 | 3373 |
12 | Locked | QAM256 | 11 | 519 | 10.3 | 43.1 | 2966 | 2546 |
13 | Locked | QAM256 | 12 | 525 | 10.4 | 43.2 | 3453 | 4104 |
14 | Locked | QAM256 | 13 | 531 | 10.8 | 43.2 | 2894 | 3577 |
15 | Locked | QAM256 | 14 | 537 | 10.3 | 43 | 2399 | 2162 |
16 | Locked | QAM256 | 15 | 543 | 10.2 | 42.9 | 2904 | 3006 |
17 | Locked | QAM256 | 16 | 549 | 10.1 | 42.9 | 2468 | 2673 |
18 | Locked | QAM256 | 17 | 555 | 9.7 | 42.9 | 2421 | 2185 |
19 | Locked | QAM256 | 18 | 561 | 9.5 | 42.6 | 2624 | 2995 |
20 | Locked | QAM256 | 19 | 567 | 9.4 | 42.6 | 2036 | 1849 |
21 | Locked | QAM256 | 20 | 573 | 9 | 42.2 | 2316 | 2209 |
22 | Locked | QAM256 | 21 | 579 | 8.9 | 42 | 3043 | 3079 |
23 | Locked | QAM256 | 22 | 585 | 8.7 | 41.9 | 2114 | 1783 |
24 | Locked | QAM256 | 23 | 591 | 8.3 | 41.6 | 2143 | 1762 |
25 | Locked | OFDM PLC | 37 | 690 | 9 | 40.5 | 179160725 | 2617 |
26 | Locked | QAM256 | 38 | 429 | 10.7 | 43.5 | 6607 | 5157 |
27 | Locked | QAM256 | 39 | 435 | 10.4 | 43.5 | 7377 | 5386 |
28 | Locked | QAM256 | 40 | 441 | 10.2 | 43.3 | 8370 | 6682 |
29 | Locked | QAM256 | 41 | 447 | 10 | 43.3 | 5849 | 4980 |
30 | Locked | QAM256 | 43 | 411 | 11.2 | 43.8 | 9415 | 7302 |
31 | Locked | QAM256 | 44 | 417 | 10.9 | 43.7 | 9452 | 6359 |
32 | Locked | QAM256 | 45 | 423 | 10.7 | 43.5 | 9770 | 6912 |
Channel | Lock Status | Channel Type | Channel ID | Symb. Rate (Ksym/sec) | Freq. (MHz) | Pwr (dBmV) |
1 | Locked | SC-QAM | 1 | 5120 | 35.6 | 46.5 |
2 | Locked | SC-QAM | 2 | 5120 | 29.2 | 46.5 |
3 | Locked | SC-QAM | 3 | 5120 | 22.8 | 46.5 |
4 | Locked | SC-QAM | 4 | 5120 | 16.4 | 46.5 |
5 | Locked | SC-QAM | 5 | 1280 | 39.6 | 47.3 |
EVENT LOG
Note that the first two lines here correspond to a reboot of the modem, I left out the prior lines from the reboot assuming they were fairly standard, but can easily add that if necessary.
Time | Priority | Description |
19:38:42 Wed Oct 18 2023 |
Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-QOS=1.1;CM-VER=3.1; |
19:38:42 Wed Oct 18 2023 |
Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-QOS=1.1;CM-VER=3.1; |
19:38:48 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
19:38:48 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
19:38:48 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
19:38:48 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
19:38:48 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
19:38:48 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
19:38:48 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
19:38:48 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
19:38:48 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
19:38:48 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
19:38:52 Wed Oct 18 2023 |
Critical (3) | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
21:18:23 Wed Oct 18 2023 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
21:18:24 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
21:18:24 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
21:18:24 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
21:18:24 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
21:18:28 Wed Oct 18 2023 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
21:18:29 Wed Oct 18 2023 |
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-QOS=1.1;CM-VER=3.1; |
21:18:33 Wed Oct 18 2023 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
21:18:34 Wed Oct 18 2023 |
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-QOS=1.1;CM-VER=3.1; |
21:18:38 Wed Oct 18 2023 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
21:18:39 Wed Oct 18 2023 |
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-QOS=1.1;CM-VER=3.1; |
21:18:42 Wed Oct 18 2023 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
21:18:49 Wed Oct 18 2023 |
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-QOS=1.1;CM-VER=3.1; |
21:19:38 Wed Oct 18 2023 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
21:19:55 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
21:19:55 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
21:21:45 Wed Oct 18 2023 |
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-QOS=1.1;CM-VER=3.1; |
21:29:40 Wed Oct 18 2023 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
21:29:43 Wed Oct 18 2023 |
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-QOS=1.1;CM-VER=3.1; |
21:31:50 Wed Oct 18 2023 |
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-QOS=1.1;CM-VER=3.1; |
21:36:29 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
21:36:29 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
21:36:29 Wed Oct 18 2023 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
21:36:29 Wed Oct 18 2023 |
Warning (5) | Dynamic Range Window violation |
21:36:30 Wed Oct 18 2023 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
user_71gucl
Contributor
•
17 Messages
2 years ago
Additional logging from overnight:
Wed Oct 18 2023
Wed Oct 18 2023
Thu Oct 19 2023
Thu Oct 19 2023
Thu Oct 19 2023
Thu Oct 19 2023
0
0
EG
Expert
•
110.3K Messages
2 years ago
This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless.
The downstream power is high / strong. It may be over-driving the front-end receiver circuit of the modem. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
Is there a drop amplifier on the coax cable line leading to the modem ? If so, try removing / bypassing it and see. If not, you can try installing a -6 dB forward path-only attenuator pad such as this one on the coax port on the rear of the modem to knock that power level down and see;
https://www.amazon.com/FPA6-54-Forward-Attenuator-DOCSIS-Internet/dp/B08KTRC3XZ
It won't affect the upstream power level which is within spec. Good luck !
1
0
EG
Expert
•
110.3K Messages
2 years ago
You're welcome ! Please do post back here with how it goes, thanks.
1
0
EG
Expert
•
110.3K Messages
2 years ago
@user_71gucl
Thanks for the update. Fingers crossed ! 🤞
1
0
user_71gucl
Contributor
•
17 Messages
1 year ago
About a month ago I report a similar issue here; thanks to forum user EG I found what I thought was the work-around (attenuator for downstream power), but in the last couple of days the problems have returned and are at least as bad (if not worse) than previously.
Original forum post for reference: https://forums.xfinity.com/conversations/your-home-network/intermittent-desyncs-and-disconnects-getting-worse/6530a1f0e05b5f65da02f615
Here are event logs (Motorola MB8600) from the last 24hrs, excluding "Notice" log level events:
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Wed Nov 29 2023
Thu Nov 30 2023
Thu Nov 30 2023
Thu Nov 30 2023
Thu Nov 30 2023
Thu Nov 30 2023
Thu Nov 30 2023
Downstream channel status:
Upstream channel status:
Fingers crossed one of you wizards has another miracle in store...
1
0
user_71gucl
Contributor
•
17 Messages
1 year ago
Just to rule out at least one possibility, I got a newer cable modem yesterday (Arris S33), but it quite clearly has not helped.
Updated Connection status and Logs from the last ~hour or so below...
09:30:51
09:30:52
09:30:52
09:30:52
09:30:52
09:30:52
09:30:52
09:30:53
09:30:54
09:30:54
09:36:12
09:36:12
09:36:12
09:36:14
09:36:17
09:36:32
09:37:04
09:37:04
09:37:06
09:54:34
09:55:56
09:55:56
09:55:56
09:56:04
09:56:08
10:13:08
10:13:08
10:13:08
10:13:09
10:13:13
10:13:13
10:13:13
10:13:26
10:13:33
0
0
user_71gucl
Contributor
•
17 Messages
1 year ago
This is starting to feel like a personal blog...
I took a look at the Comcast installed box on the side of my house, and while everything looks ok there, I did find an unnecessary splitter; I've removed it, hoping it might help the signal strength (if that's even the issue at this point), but it unfortunately hasn't seemed to help at all.
More event logs from this afternoon:
11:00:40
11:00:51
11:18:06
12:10:30
13:39:52
13:39:52
13:39:52
13:39:52
13:39:52
15:23:23
15:24:12
15:24:12
15:24:12
15:24:22
15:24:37
15:24:37
15:24:38
15:24:39
15:24:39
15:24:39
15:24:39
15:24:39
15:24:39
15:24:39
15:24:39
15:24:41
15:24:42
15:24:42
2
0
user_71gucl
Contributor
•
17 Messages
1 year ago
For anyone still following along at home, Justin kindly took a look at what he could remotely, and determined that my own signals as well as some neighbors in the area "don't look solid", so we agreed to have a technician come out to have a look. That should happen mid-day on this Tuesday the 5th, after which I'll follow-up here with what we've learned.
Thanks for your time and help today, Justin!
0
0
user_71gucl
Contributor
•
17 Messages
1 year ago
tl/dr: things are better
Last night and again this morning I received a call from Comcast Tech Support; apparently my issue had been escalated to their team. Both people I spoke with indicated "something" had been investigated and corrected, and asked if my service was now working properly. I tried to explain to both that my issue was intermittent; and, while on the phone with them things were normal, I didn't necessarily have any expectation that things would continue to be normal given the recent history. I do not wish to speak unkindly to those who were tasked with these follow-up calls, but I got the feeling they were primarily interested in cancelling the in-person tech appointment, which we ultimately agreed to do. Assuming the issue actually has been corrected by someone/something, then they obviously were calling for the right reason.
In both cases I asked for an explanation of what had been done, and in neither did I get much of an answer; this morning's call the support person simply said that some "signal" had been sent and that now everything looked good... I did attempt to explain that initial investigation by Justin indicated that my issue was apparent not just for me specifically but also in neighboring homes as well, which to me spoke to wider issue. Nevertheless, I couldn't seem to get any further information, though perhaps the person I was speaking with simply didn't have details on precisely what was done. I'm mentioning all of this solely for the future person who searches for resolution to a similar problem, and I'm sorry you won't find much here beyond "be persistent with your need for help and hope support is able to find 'something' to correct".
Nevertheless, things have been stable for at least the last 24hrs, so that's a step in the right direction. Thanks again to Justin for initiating, investigating, and escalating.
(edited)
1
0
user_71gucl
Contributor
•
17 Messages
1 year ago
Well, the joke's on me (again).
Beginning again this morning are more T3 timeouts, Dynamic Range Window violations, Unicast Maintenance Ranging, etc.
Can't believe I let myself be talked into cancelling the on-site tech appointment, which would have conveniently been this morning.
Hopefully I can have one rescheduled relatively quickly.
More to come...
0
0
user_71gucl
Contributor
•
17 Messages
1 year ago
On-site tech was here today.
He found a loose connection at the pole near my house, and replaced it; he explained this can happen naturally over time depending on climate, weather conditions, etc.
He additionally noticed the connection to the box on the outside of my house (the coax from the pole to the house) was slightly degraded as well, and went ahead and replaced this connection; similarly to the above, this apparently can be a natural phenomenon over time and he didn't seem particularly surprised by it.
Unfortunately, within a half hour of him leaving, my modem is once again logging some t3 time out events and unicast maintenance ranging errors. I have not yet personally experienced the same loss-of-connectivity issues I've been having, but I assume the logging is not a good sign and it's only a matter of time...
Will keep monitoring and escalate again if today's visit hasn't found the true source of the errors.
1
0
user_71gucl
Contributor
•
17 Messages
1 year ago
On-site tech #2 was here this afternoon (an hour early, bonus points for him!).
He was not aware another tech had already been to look into this issue, so I went through all of the history I could recall as well as what I understood had been done the day before.
He put some monitoring equipment on the inside line to the cable modem, and then again outside at the box on the side of my house, and saw nothing wrong with any of the signals/power/noise/etc.
He could think of no other reason I would be experiencing the issues I've been seeing, except for the possibility that the cable modem was overheating, so moved it to a location with better ventilation. I did explain that this was a new modem, that I had replaced it in the last week or two, and that even with the prior modem I had experienced the same set of problems/errors.
In any event, as things were "normal" while he was here, he was out of options.
In the hour or so after he left, I captured these from the modem's event logs:
14:30:28
14:30:28
14:30:28
14:30:28
14:30:28
14:30:28
14:30:28
14:30:28
14:30:28
14:30:30
14:30:31
14:30:31
14:44:11
14:45:15
14:45:18
14:47:23
14:49:48
14:53:40
14:53:40
14:53:40
14:53:50
14:53:56
14:53:59
14:54:08
Connectivity has been normal for the hour following the last logged event above, and I expect it to be fine until whatever gremlin is causing the periodic issues wakes up and wreaks some more havoc.
I've since been in touch with support once again, and they've arranged for another on-site tech visit for this coming Tuesday morning, so I will once again follow-up here afterwards.
0
0
user_71gucl
Contributor
•
17 Messages
1 year ago
I was off by one day, the follow-up on-site appointment was today (Monday).
Today's visit was the best by far, by a Comcast employee (as opposed to the consultants that are often used); he immediately acknowledged there were myriad signal problems in the area, and never even bothered coming in my house. He had also arranged ahead of time for a partner employee with a bucket truck to arrive with him! As at least an initial step, they reran a new coax line from the top of the pole near my house to the xfinity box on the side the house, and had me reattach a signal attenuator to the cable modem (the first on-site tech removed mine......and he kept it). Signal levels once again look good, and I will continue to monitor over the next few days.
The tech stated that while this should definitely help my recent issues, it will not necessarily completely solve them, as the signal issues in the area could still cause widespread/periodic problems; ultimately they made need to continue to do similar work as they did for me today at other residences/businesses in the area (that is, if I or enough other people keep escalating issues).
Will try to report back here in a few days with an update.
BIG thanks to today's techs, Wes and DJ.
1
0
user_71gucl
Contributor
•
17 Messages
1 year ago
Things have been significantly better, almost perfect.
I've had a single error (a t3 time-out) since the techs were here on Monday, so an enormous improvement overall.
I'll obviously continue to monitor, and will re-escalate if/when things become problematic again, but for the time being things are "good".
Thanks again to all the support personnel (both online and in person) who have helped!
0
0