Constant T3/4 errors
Constant outages for the last several months, T3 and T4 errors in the logs each time. Never had issues except when maintenance was performed, then a round of cox trucks came in the area and we've had constant issues since. Replaced the modem without improvement, Motorola worked with me for weeks and came to the resolution Cox needs to get their stuff together and fix it. Tech came out and the only issue he saw was the signal was a little too hot, so we put a damper on the line and that didn't help anything. Motorola then said constant T3/T4 errors would cause a modem reboot in a last ditch effort to establish connection, something primarily with T4 errors and reprovisioning attempts. All my attempts to reach out to Cox has been laughable, they immediately want to reboot the modem (its always been rebooting when I call or chat) or send a tech to my home and bill me for cable replacement - brand new RG6U that worked fine for years. Never had issues till one of their techs messed something up down the line. Now it reboots several times a day and night, and our work from home keeps getting interrupted. Last speed test results 38ms ping, 383.6 down 9.8 up, and 3 ms jitter. Speeds are fine till it cuts out. No complaints otherwise. What do I need to do to get someone to fix this junk?1.1KViews0likes12Comments
Dynamic Window Range Violations, MDD message timeout, T3 / T4 timeouts
I recently purchased a new modem from Cox since I was experiencing constant interruptions and found a ton of T3/T4 errors with the old (really old) modem. A tech support rep suggested that perhaps the modem was old and throwing errors. I purchased the Arris Touchstone at the Cox store, and moved it to a dedicated cable outlet. It is connected directly to the cable line, with no splitters (that I can see), and attached to an Apple Airport Extreme. I still experience slow down and drops, which are most noticeableduring Skype video calls which I need to do for work, but there are fewer T3/T4 errors now than there was with the old modem. My event log on my modem shows constant errors (I have deleted out my MAC address, if that makes any difference). As you can see, the event log actually runs out of space, because of all the errors. Weirdly, ON 8/2, there were few errors and the internet was being used as normal. This is a very annoying issue and prevents my family from using the internet as normal because of the slowdown in service. Does anyone have a thought on how to proceed to amend this issue? 8-5-2017, 7:7:46 Warning(5) "MDD message timeout;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-4-2017, 16:15:26 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-4-2017, 15:41:21 Warning(5) "MDD message timeout;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-4-2017, 14:9:21 Warning(5) "Dynamic Range Window violation" 8-4-2017, 13:4:14 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-4-2017, 13:3:44 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-4-2017, 13:2:49 Warning(5) "Dynamic Range Window violation" 8-4-2017, 8:7:39 Warning(5) "MDD message timeout;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-4-2017, 8:7:36 Warning(5) "Dynamic Range Window violation" 8-4-2017, 1:14:47 Error(4) "DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-4-2017, 1:14:36 Warning(5) "Dynamic Range Window violation" 8-3-2017, 19:0:58 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 19:0:32 Warning(5) "Dynamic Range Window violation" 8-3-2017, 17:53:19 Warning(5) "MDD message timeout;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 17:53:19 Warning(5) "Dynamic Range Window violation" 8-3-2017, 14:27:45 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 14:27:38 Warning(5) "Dynamic Range Window violation" 8-3-2017, 14:27:15 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 14:27:0 Warning(5) "Dynamic Range Window violation" 8-3-2017, 12:55:14 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 12:54:44 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 12:52:14 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 12:51:44 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 12:50:14 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 12:49:44 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 11:56:33 Warning(5) "Dynamic Range Window violation" 8-3-2017, 11:51:40 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 11:51:10 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-3-2017, 11:48:10 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-2-2017, 5:49:12 Warning(5) "Dynamic Range Window violation" 8-2-2017, 5:49:11 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-2-2017, 5:49:7 Warning(5) "MDD message timeout;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-2-2017, 5:49:7 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:5:7 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:4:37 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:4:20 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:3:50 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:3:33 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:3:3 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:2:45 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:2:15 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:1:58 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:1:28 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:1:10 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 20:0:40 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 19:59:45 Warning(5) "Dynamic Range Window violation" 8-1-2017, 19:8:7 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 19:8:5 Warning(5) "Dynamic Range Window violation" 8-1-2017, 14:57:52 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 14:57:22 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 14:54:46 Warning(5) "Dynamic Range Window violation" 8-1-2017, 14:23:56 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 14:23:26 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1;" 8-1-2017, 14:21:11 Warning(5) "Dynamic Range Window violation"2.6KViews0likes4Comments
Connection Dropping Randomly
I don't know what is going on with Cox internet, but my connection is dropping randomly for the last several days and it's not my equipment. There are no splitters in the room where the modem is located. I've tried getting help from @CoxHelp account on Twitter and those people kept insisting it's my equipment when I know it isn't. Here are the most recent logs/info from my Surfboard 6121 modem:3.6KViews0likes9Comments
Connection Dropping Randomly
I don't know what is going on with Cox internet, but my connection is dropping randomly for the last several days and it's not my equipment. There are no splitters in the room where the modem is located. I've tried getting help from @CoxHelp account on Twitter and those people kept insisting it's my equipment when I know it isn't. Here are the most recent logs/info from my Surfboard 6121 modem:
