NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM1000V2 and comcast, CM1000 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol
I've been battling disconnects, from 2-10 a day, packet loss, slow speeds. Playing World of Warcraft or Call of Duty becomes unplayable due to normal 50-60ms speeds going to 1100-2000ms+. I've spen...
Your main channels have some correct and un-correcables.
I see the OFDMA channel has tons. This should be near zeros. something the ISP should help you resolve. Something to check the coax cable line and remove any splitters. Check all jack fittings and such.
Have the ISP check the signal up to the modem as well. Power on the line is a bit on the low side but in spec.
CAT6 UTP is fine.
What is the distance between the modem and router?
What brand and model router are you using with the CM modem?
Distance between modem and router is about 2.5 feet. Model of router is: tp-link AX1500 Wi-Fi 6 router.
Archer AX1500
AX1500 Wi-Fi 6 Router
Lets increase the distance to 6 feet between the modem and router.
Ok so the tech came out from Xfinity. Found a small "kink" in my cable (didn't looks like much tbh). Also removed a splitter. Was stable all of yesterday after he left. Today it is back to normal, stable then for no reason speeds drop and online gaming pings go up to 600-2000ms. I explained to him and showed him that my "time on the modem" is 9 hours ahead of where it should be. He said that does not matter that I'm getting a perfect signal to my modem, and if I continue having issues it's the Netgear modem and that I should consider renting one from xfinity.
Replaced the ethernets to Cat6 and moved the modem.
Todays error log :2022-10-21, 20:05:33 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 31 32 34 36 37 38 39 40 41 42 43 44 45 46 47 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-
2022-10-21, 20:05:32 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;
2022-10-21, 20:05:25 Warning (5) MDD message timeout;CM-
2022-10-21, 20:02:01 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
2022-10-21, 20:01:46 Notice (6) CM-STATUS message sent. EveCM-MAC=08:36:c9:ce:1a:80;CMTS-MAC=
2022-10-21, 20:01:45 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 20:01:30 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 20:01:30 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 20:01:14 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 20:01:13 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 20:01:02 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
2022-10-21, 19:59:04 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 19:58:50 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;
2022-10-21, 19:58:49 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;
2022-10-21, 19:58:47 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 31 32 34 36 37 38 39 40 41 42 43 44 45 46 47 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=0
2022-10-21, 19:58:46 Warning (5) MDD message timeout;CM-MAC=
2022-10-21, 19:58:46 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 19:58:46 Warning (5) MDD message timeout;CM-MAC=
2022-10-21, 19:57:59 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 19:57:44 Warning (5) MDD message timeout;CM-MAC=
2022-10-21, 19:57:39 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 19:57:38 Warning (5) MDD message timeout;CM-MAC=
2022-10-21, 19:57:29 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 19:57:16 Warning (5) MDD message timeout;CM-MAC=
2022-10-21, 19:57:00 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;
2022-10-21, 19:56:43 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=
2022-10-21, 19:56:40 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
2022-10-21, 19:56:11 Warning (5) MDD message timeout;CM-MAC=
2022-10-21, 19:55:46 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
2022-10-21, 19:55:27 Warning (5) MDD message timeout;CM-MAC=CMTS-MAC=
2022-10-21, 19:55:11 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;C
2022-10-21, 19:55:00 Warning (5) MDD message timeout;CM-MAC;CMTS-MAC=
2022-10-21, 19:54:22 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=
2022-10-21, 19:52:40 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; 2022-10-21, 19:47:21 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1
2022-10-21, 19:47:19 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=
2022-10-21, 19:46:01 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=
2022-10-21, 19:42:19 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=
2022-10-21, 19:41:44 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=
2022-10-21, 19:41:40 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=Might do a factory reset on the CM modem and set it up from scratch.
Though those logs are mostly for channel 48 and OFDMA notices and nothing critical. Possible something on the ISP side that doesn't service OFDMA maybe. Other wise looks ok.
Might ask the ISP to remove the modems association with there service. Then re-add it and ensure it's go the right config file sent down.
Try connecting to the modem only with a wired PC for a duration to see if problem is seen here as well. If not, then possible your wifi router could be at play here. Tthen you might try and change this item out and try a different one as well. If the problem still continues, rent the ISP modem for a while and see if the problem continues or not. if not, then possible the CM modem could be faulty.