1 Message
Randomly dropping connection
I have a Motorola MG8702, ever since they did an area upgrade my internet random drops. Not at the modem level, just during use of the internet. I game and I get disconnected from the game server randomly. Thought it might be because my PC is hard wired but my Xbox is wireless and it has the same problem. We will play together and loses server connection at the same time, even happens when we are playing different games. Need some help and advise
Startup Sequence
Startup Step Status Comment
Acquire Downstream Channel 567000000 Hz Locked
Upstream Connection OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
Connection Status
System Up Time 3 days 01h:54m:32s
Network Access Allowed
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 20 567.0 -8.0 42.1 13 0
2 Locked QAM256 1 453.0 -5.1 44.5 0 0
3 Locked QAM256 2 459.0 -6.6 43.6 0 0
4 Locked QAM256 3 465.0 -6.7 43.4 9 0
5 Locked QAM256 4 471.0 -6.1 43.8 63 0
6 Locked QAM256 5 477.0 -4.8 44.7 9 0
7 Locked QAM256 6 483.0 -5.5 44.3 0 0
8 Locked QAM256 7 489.0 -6.8 43.3 0 0
9 Locked QAM256 8 495.0 -6.9 43.1 0 0
10 Locked QAM256 9 501.0 -6.4 43.5 0 0
11 Locked QAM256 10 507.0 -5.7 44.0 0 0
12 Locked QAM256 11 513.0 -6.1 43.8 0 0
13 Locked QAM256 12 519.0 -7.3 42.7 0 0
14 Locked QAM256 13 525.0 -7.6 42.5 0 0
15 Locked QAM256 14 531.0 -7.3 42.7 0 0
16 Locked QAM256 15 537.0 -6.8 43.1 0 0
17 Locked QAM256 16 543.0 -7.1 42.8 0 0
18 Locked QAM256 17 549.0 -8.5 41.8 0 0
19 Locked QAM256 18 555.0 -8.8 41.5 0 0
20 Locked QAM256 19 561.0 -8.2 41.8 10 0
21 Locked QAM256 21 573.0 -7.7 42.3 12 0
22 Locked QAM256 22 579.0 -8.4 41.7 0 0
23 Locked QAM256 23 585.0 -8.4 41.5 0 0
24 Locked QAM256 24 591.0 -8.4 41.5 0 0
25 Locked QAM256 25 597.0 -8.5 41.5 0 0
26 Locked QAM256 26 603.0 -8.1 41.7 0 0
27 Locked QAM256 27 609.0 -8.3 41.5 0 0
28 Locked QAM256 28 615.0 -8.8 41.2 0 0
29 Locked QAM256 29 621.0 -9.0 41.0 0 0
30 Locked QAM256 30 627.0 -9.4 40.6 0 0
31 Locked QAM256 31 633.0 -8.7 41.2 0 0
32 Locked QAM256 32 639.0 -8.8 41.1 0 0
33 Locked OFDM PLC 193 957.0 -14.4 36.7 -1795432741 13
Upstream Bonded Channels
Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked SC-QAM 17 5120 16.4 42.8
2 Locked SC-QAM 18 5120 22.8 41.5
3 Locked SC-QAM 19 5120 29.2 43.8
4 Locked SC-QAM 20 5120 35.6 47.0
Event Log
Time Priority Description
12:05:28
Thu Feb 15 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
12:06:09
Thu Feb 15 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 193; 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
20:02:40
Thu Feb 15 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
20:05:16
Thu Feb 15 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
20:39:32
Thu Feb 15 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
20:45:37
Thu Feb 15 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
00:49:18
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
00:52:39
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
05:33:23
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
05:36:26
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
09:01:27
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
09:03:22
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
13:53:07
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
13:55:18
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
15:41:18
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
15:45:16
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
17:47:06
Fri Feb 16 2024 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;
20:40:38
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
20:44:57
Fri Feb 16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
00:57:22
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
00:59:36
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
07:23:34
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
07:26:50
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
10:13:12
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
10:24:25
Sat Feb 17 2024 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;
10:24:25
Sat Feb 17 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
10:29:31
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
10:33:37
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
13:03:40
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
13:05:21
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
14:45:02
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; 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;
14:47:16
Sat Feb 17 2024 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; 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;
EG
Expert
•
111K Messages
1 year ago
@HorrificScorez
Please redact all of the CM MAC and the CMTS MAC addresses from your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".
0
0
EG
Expert
•
111K Messages
1 year ago
OK. Your post is public again. That said, the downstream power is borderline low / weak (way out of spec on the OFDM PLC channel) and it may be intermittently fluctuating even lower out of spec . That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
Good luck with it !
(edited)
0
0
XfinityAmandaB
Official Employee
•
2.3K Messages
1 year ago
@HorrificScorez Thank you so much for your post on your connection issues. We can help a few things first the Motorola MG8702 is rated on our end to support up to 945Mbps if you are currently on a speed that is higher than that you may be overloading the modem. You can check this page here to see all of our supported devices and the speeds we know they can support on our network. https://www.xfinity.com/support/devices/ If your modem is receiving more speed than it can support that can cause a few issues. Slow connection during normal usage intermittent disconnects in connection, your modem resetting or timing out. If you are on a speed lower than 945Mbps you can check the coax connection to the modem from the wall and make sure there are not any punctures kinks cuts or any damage that may create connection issues and ensure the connections are finger tight. If that all looks good, and you are speed is capable of being supported by your modem let me know.
0
EG
Expert
•
111K Messages
1 year ago
That not quite how things work.....
0
0
EG
Expert
•
111K Messages
1 year ago
@HorrificScorez
Did you get a chance to see if any of those tips apply ?
0
0