× NETGEAR would like to hear from you about specific features so we can improve your experience. To participate in this survey please click HERE.
Reply

Constant ping issues/lag/disconnects

lancer586
Aspirant

Constant ping issues/lag/disconnects

Hey guys,

 

Lately i been experiencing tons of ping, lag issues, random disconnects. I just recently switched from xfinity internet to wowway because there was a really good package deal that had faster speeds and cheaper price. I spoke with a wowway rep and they told me that their end looks good and that maybe i should restart modem and do a full power down and whatnot. I even went and replaced my cm700 and upgraded to the cm1000 and still no fix. Before i have a tech come out and check my lines because they said if it is on my end i would be charged a fee, i want to know your guys opinion first. I looked up event logs and there are just a bunch of errors,critical, and warnings! Here is a copy of my event log and upstream and downstream.

 

2021-08-09, 07:39:57Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:39:35Warning (5)MDD message timeout;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:39:18Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:39:18Notice (6)TLV-11 - unrecognized OID;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:39:18Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:39:16Notice (6)Honoring MDD; IP provisioning mode = IPv4
2021-08-09, 07:38:53Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:49Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:49Warning (5)MDD message timeout;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:49Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:48Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:43Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:42Warning (5)MDD message timeout;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:40Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:28Warning (5)MDD message timeout;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:06Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:05Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:04Notice (6)TLV-11 - unrecognized OID;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:04Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:52Notice (6)Honoring MDD; IP provisioning mode = IPv4
2021-08-09, 07:38:33Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:29Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:23Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:07Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:06Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:06Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:05Warning (5)MDD message timeout;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:38:04Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 07:15:02Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 06:31:42Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 06:31:40Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 06:31:37Warning (5)MDD message timeout;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 06:30:47Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 06:30:37Warning (5)MDD message timeout;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 06:30:33Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 06:30:33Warning (5)MDD message timeout;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 06:30:28Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;
2021-08-09, 06:29:26Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:84:91:8c;CMTS-MAC=00:01:5c:6e:f6:63;CM-QOS=1.1;CM-VER=3.1;

 

Model: CM1000|Ultra-High Speed Cable Modem—DOCSIS® 3.1 Ready, CM700|High Speed Cable Modem—DOCSIS 3.0
Message 1 of 6
plemans
Guru

Re: Constant ping issues/lag/disconnects

Do you also have  copy of the cable connections page? 

A couple things you can do to reduce the chance you'll get charged. 

1. connect directly to the modem. remove the router to ensure it is indeed a modem/line issue. 

2. move the modem to right where the coax enters the home. This prevents wiring in the home from being the issue.

3. remove any splitters, amplifiers, or signal attenuators from the line. 

4. check the link for kinks, damage, bad/old/corroded/loose connections and replace them if you have them. 

 

Basically you want to limit as much as possible what in the home can cause the issue. If you've already replaced the modem and both had issues, it tends to suppor the case that its not the modem. Not saying 100% it isn't because random chance is a "B" but its reduced. 

Current setup: CM2000-> RBKE963B-> Trendnet TEG-S380-> GS716T-> pi-hole
also in AP setup: RAXE500->EAX80
1.4gig download/50mbps upload from Xfinity
We’re members of the public helping out on our own time.
Message 2 of 6
lancer586
Aspirant

Re: Constant ping issues/lag/disconnects

For some reason its not letting me post the cable connection page.

Message 3 of 6
plemans
Guru

Re: Constant ping issues/lag/disconnects

Click on "choose file" and add it one file at a time. 

Current setup: CM2000-> RBKE963B-> Trendnet TEG-S380-> GS716T-> pi-hole
also in AP setup: RAXE500->EAX80
1.4gig download/50mbps upload from Xfinity
We’re members of the public helping out on our own time.
Message 4 of 6
lancer586
Aspirant

Re: Constant ping issues/lag/disconnects

ok here is the cable connection.

Message 5 of 6
plemans
Guru

Re: Constant ping issues/lag/disconnects

You have quite a few errors in your lines. coupled with your logs it tends to indicate line issues. 

check the line for damage, kinks, old/cheap/loose/corroded connections and replace them if you do. 

remove any splitters, amplifiers, or signal attenuators

Current setup: CM2000-> RBKE963B-> Trendnet TEG-S380-> GS716T-> pi-hole
also in AP setup: RAXE500->EAX80
1.4gig download/50mbps upload from Xfinity
We’re members of the public helping out on our own time.
Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 690 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 6E