Slow real time upload speed - conflicting speed test results
I'm experiencing slow real time upload speeds. The speed test on Cox website have conflicting results. I've had 8 techs out to my house over the last 4 months and the issue has not been resolved. I am experiencing the same exact issues as usernoah82. We are both in Arizona. Here is his thread.http://forums.cox.com/forum_home/internet_forum/f/5/t/13025.aspx9.3KViews0likes34CommentsPaying for 300 mbps, not even getting 20. What gives?
Hi forum, for the past 2 days I have been getting less than "optimal" speeds to say the least. It took me about 20 seconds to open up this page, so thats saying something. Anyways, Im paying for 300/30 speeds, but getting less than advertised Router is: ARRIS DG2460 I know its not my PC because A) Its wired, and B) My phone cant load anything when connected to WiFi and C) My smart TV refuses to connect due to a bad connection. I assure you my pc is 10/100/1000 Ethernetas well as my router. I have done nothing to the router except change the name and the passwords on the dual band networks. Ive reset my router by unplugging it for an hour, resetting though the direct ip connection, and evem through cox. If this keeps going, I might switch back to centurylink, because as unreliable as they are, at least they give me my speeds.9.2KViews0likes10CommentsPacket Loss and Latency Spikes
This is not the first time this is happened (it happens periodically), but I am having issues with packet loss and disconnects between my modem and the ISP (hop 2). They are intermittent and very annoying. I pay $75 a month for fast internet, and I am the only person who uses it, yet I have constant problems. I had these issues with the old Cox-issed Cisco modem and my current Surfboard SB6183. Same issues with three different routers as well (Apple AirPort Extreme, Netgear Nighthawk X6, Linksys WRT1900AC). It has to be on Cox's end, but I get zero help when I call in and talk to support. They always ask me stupid questions (have you reset the modem, have you checked your router, have you tried connecting directly to the modem via ethernet, etc.) and say everything looks fine on their end. I had a tech out last month and he pulled a filter/splitter off and replaced it and said things were fixed. I was at work when he came and my housemate said that he was here for about 10 minutes. Below is a screenshot of Pingplotter, the status page of my modem, and the event log of my modem. http://i.imgur.com/1Gnp1a5.png Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 73 813000000 Hz 8.7 dBmV 40.2 dB 9 65 2 Locked QAM256 74 819000000 Hz 9.1 dBmV 40.3 dB 23 48 3 Locked QAM256 75 825000000 Hz 8.9 dBmV 40.3 dB 17 56 4 Locked QAM256 76 831000000 Hz 9.1 dBmV 40.2 dB 43 133 5 Locked QAM256 77 837000000 Hz 9.4 dBmV 40.3 dB 15 84 6 Locked QAM256 78 843000000 Hz 9.8 dBmV 40.1 dB 11 67 7 Locked QAM256 79 849000000 Hz 9.7 dBmV 40.5 dB 13 60 8 Locked QAM256 80 855000000 Hz 9.6 dBmV 40.3 dB 18 69 9 Locked QAM256 89 909000000 Hz 8.8 dBmV 40.3 dB 15 55 10 Locked QAM256 90 915000000 Hz 8.7 dBmV 40.3 dB 38 61 11 Locked QAM256 91 921000000 Hz 8.7 dBmV 40.3 dB 24 98 12 Locked QAM256 92 927000000 Hz 9.2 dBmV 40.5 dB 38 31 13 Locked QAM256 93 933000000 Hz 8.8 dBmV 40.3 dB 22 81 14 Locked QAM256 94 939000000 Hz 8.2 dBmV 40.1 dB 49 107 15 Locked QAM256 95 945000000 Hz 7.7 dBmV 39.9 dB 18 57 16 Locked QAM256 96 951000000 Hz 8.2 dBmV 40.0 dB 12 69 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 37300000 Hz 36.9 dBmV 2 Locked ATDMA 1 2560 Ksym/sec 19400000 Hz 34.8 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 24300000 Hz 35.3 dBmV 4 Locked ATDMA 3 5120 Ksym/sec 30800000 Hz 36.0 dBmV Current System Time:Mon Jan 02 20:18:17 2017 Time Priority Description Mon Jan 02 20:02:24 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:45:13 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:44:45 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:44:44 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:43:15 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:40:31 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:39:48 2017 Notice (6) TLV-11 - unrecognized OID;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Jan 02 19:38:47 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Mon Jan 02 19:14:32 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 14:49:12 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Jan 01 12:18:24 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Sun Jan 01 12:06:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:08 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:04 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 07:45:18 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 04:12:00 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:36 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:26 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 01:04:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 00:34:59 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 22:08:29 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:37:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:57 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:44 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:29:30 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:21:46 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:04:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 18:26:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 17:06:43 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 14:38:58 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:22:19 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:20:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 09:14:17 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 20:11:54 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:32:03 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:31:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 14:19:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:53:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:32:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:06:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:44:52 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:16:42 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 09:43:45 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 08:47:55 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 23:01:39 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:37:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:10:05 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:09:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:05:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:04:38 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 12:16:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 10:44:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 04:02:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:35:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:46 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 20:58:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 14:04:29 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:26:04 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:25:50 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:26:12 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:24:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:36 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:18:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:29:10 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:27:38 2016 Critical (3) Resetting the cable modem due to docsDevResetNow Tue Dec 27 14:13:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 14:06:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 13:57:24 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 12:15:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 11:34:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 09:26:31 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 17:42:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:59 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:45 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 14:20:37 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 13:40:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:39:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 04:37:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 00:05:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 14:36:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 09:44:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0;8.6KViews0likes24CommentsMail for Windows 10
Dear Madam or Sir: I hope you are doing well today. Today, something significant happened to my client application called “Windows Live Mail”, where I am no longer able to check my domain @Cox.Net email account. I called the Cox Communications Help Desk and we decided I would need to figure-out how to configure “Mail for Windows 10”, since it is new and everything was working fine on the Cox Communications email servers. In addition, I am able to login at Cox Communications “My Connection” and check my domain @Cox.Net email account along with “Personalized Folders”. Please feel free to share with the Cox Communications Help Desk the following settings for configuring “Mail for Windows 10”. 1) Open “Mail for Windows 10” in a small window. 2) Open operating system Windows 10 “Settings” in a small window. 2a) Click “Accounts” 2b) Click “Email & App Accounts” 2c) View “Email, Calendar, and Contacts” 2d) Click “Add an Account” 2e) Scroll Down & Click “Advanced Setup” 2f) Click “Internet Email” 2g) Enter Email Address = AccountName@Cox.Net 2h) Enter User Name = AccountName 2i) Enter Password = {@Cox.Net Password} 2j) Enter Account Name = AccountName again 2k) Enter Send your message using this name = Mr\Ms. YourName 2l) Enter Incoming Email Server = pop.cox.net:995 2m) Enter Account Type = POP3 2n) Enter Outgoing (SMTP) Email Server = smtp.cox.net:465 2o) [CHECK] Outgoing Server Requires Authentication 2p) [CHECK] Use The Same Username And Password For Sending Email 2q) [CHECK] Require SSL For Incoming Email 2r) [CHECK] Require SSL For Outgoing Email 2s) Click “Sign-In” 2t) Click “Done” Now I am able to check my domain @Cox.Net email account. However, I communicated to Microsoft Corporation that I am not able to import “Personalized Folders” or “Contacts” from my domain @Cox.Net email account as of 1/23/2017. Would you please tell me how to import “Personalized Folders” or “Contacts” from my domain @Cox.Net email account? Thank you, for your time and consideration of my request. Respectfully,6.1KViews0likes1CommentLow Upload speeds.
basically through exhaustive testing on multiplecomputers routers and switchs i still only receive 6-9mbps upload on testmy.net and real uploads to youtube google cloud and dropbox. My download speeds are fine, Called tier 2 support ans said its likely a issue with my sb6190 since all signal reading good and speedtest to cox and speedtest.net are fine and requested i try a new modem.5.4KViews0likes14Comments90% + Packet Loss & Rubberbanding, Lag Spikes, connection losses to multiple game servers and streaming clients
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 10.0.1.1 - 0 | 600 | 600 | 0 | 18 | 334 | 0 | | 10.75.168.1 - 0 | 600 | 600 | 7 | 28 | 331 | 9 | | ip68-4-11-184.oc.oc.cox.net - 0 | 600 | 600 | 7 | 29 | 350 | 10 | | ip68-4-11-16.oc.oc.cox.net - 0 | 600 | 600 | 8 | 27 | 377 | 14 | | 68.1.1.61 - 0 | 600 | 600 | 10 | 33 | 373 | 10 | | xe-7-3-2.edge2.LosAngeles9.Level3.net - 0 | 600 | 600 | 10 | 34 | 360 | 13 | | 4.69.133.202 - 95 | 600 | 35 | 16343 | 20149 | 22510 | 17372 | | 192.205.37.145 - 0 | 600 | 600 | 13 | 44 | 374 | 18 | | cr1.la2ca.ip.att.net - 0 | 600 | 600 | 13 | 38 | 368 | 17 | | 12.122.90.33 - 0 | 600 | 600 | 12 | 33 | 316 | 13 | | No response from host - 100 | 600 | 0 | 0 | 0 | 0 | 0 | |________________________________________________|______|______|______|______|______|______| WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com ) Here is a sample of a 20 minute test to a blizzard server while playing overwatch. 95% packet loss to the specific IP. Multiple calls to cox with no resolution. Not even an offer to change my route. I was told that the department in charge of fixing my issue is unreachable by me as a paying customer and as well as the employees of cox not being able to contact this so called department about my problem. Super frustrating that the phone representatives take us paying and knowledgeable customers as idiots and claim that there is nothing they can do to resolve an issue multiple people are having. This is a last chance effort on my part to see if someone is smart enough to help me with this issue as I have been a loyal customer for several years.5.3KViews0likes15CommentsUnable to send e-mails, but I can still receive them.
Webmail works fine, but using outlook, windows live mail, or my android e-mail client will give me the same problem. Yes I have checked and double checked the ports and checked authentication when needed. I'm been on the phone with 3 different reps and even a tier 2 customer support agent. This started happening 3 weeks ago, and I made no changes whatsoever. Cox told me basically if webmail is working, then its fine. I need easier access to my email rather than going to webmail. Anyone know a fix for this? Thank you!4.6KViews0likes6CommentsConnection keeps dropping
For the last few days the internet at our house keeps cutting off. If we do nothing it will eventually reconnect however resetting the modem via unplugging it seems to cause the connection to refresh faster. We have tried directly wiring a computer to the modem but the connect drops anyway so we can rule out the router. When the connection drops all of the lights on the modem turn off except for the power light and then it will eventually go through same process it does when manually reset. Sometimes the lights for send/receive blink for a long while before going solid and connecting. What is causing this issue? It makes it difficult to get any work done with this kind of service interruption. Note: Modem is a Motorolla SB6141 Router is a Linksys N131714KViews0likes7CommentsHave 300mbps plan but only get 50mbps
I purchased the ultimate a while ago and have only been getting max about 50-60 mbps without anyone else on the internet. I've restarted the internet many times and tested the internet on many devices over Ethernet but not luck :/. Router: Asus rt n16 Modem: Netgear cm7003.8KViews0likes3CommentsOklahoma City / Edmond - Upload Power Levels Unstable - Causing T3 Timeout / Outages
I am near 14140 Broadway Ext, in Edmond, OK. I believe we are having a partial service interruption going on 3 days. I have humored tech support up to and including re-flashing my firmware on my modem. I can't rule out being a traffic increase relation, i.e. the neighbors are home in the evening, but the issues were prevalent all day Friday. Event Logs: Sat Oct 10 07:21:37 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 04:59:36 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 02:51:26 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 00:35:43 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 00:35:28 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 22:29:08 2015 Warning (5) Dynamic Range Window violation Fri Oct 09 22:28:33 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 22:28:09 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 21:39:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 21:38:49 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 14:52:12 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 14:51:29 2015 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.0;CM-VER=3.0; Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 50 819000000 Hz -0.1 dBmV 38.4 dB 305 574 2 Locked QAM256 49 813000000 Hz 0.0 dBmV 38.5 dB 427 699 3 Locked QAM256 51 825000000 Hz 0.3 dBmV 38.6 dB 238 512 4 Locked QAM256 52 831000000 Hz 0.5 dBmV 38.9 dB 151 443 5 Locked QAM256 53 837000000 Hz 0.1 dBmV 38.9 dB 159 157 6 Locked QAM256 54 843000000 Hz -1.4 dBmV 38.3 dB 140 106 7 Locked QAM256 55 849000000 Hz -1.6 dBmV 38.3 dB 194 293 8 Locked QAM256 56 855000000 Hz -2.0 dBmV 38.2 dB 274 417 9 Locked QAM256 57 861000000 Hz -2.5 dBmV 38.3 dB 255 531 10 Locked QAM256 58 867000000 Hz -2.9 dBmV 38.3 dB 452 638 11 Locked QAM256 59 873000000 Hz -2.4 dBmV 38.3 dB 415 568 12 Locked QAM256 60 879000000 Hz -2.8 dBmV 38.1 dB 223 433 13 Locked QAM256 61 885000000 Hz -3.0 dBmV 38.1 dB 172 415 14 Locked QAM256 62 891000000 Hz -3.0 dBmV 38.2 dB 106 182 15 Locked QAM256 63 897000000 Hz -2.7 dBmV 38.3 dB 121 130 16 Locked QAM256 64 903000000 Hz -4.1 dBmV 37.8 dB 42417 51328 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 2560 Ksym/sec 22600000 Hz 47.0 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 27500000 Hz 47.0 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 34000000 Hz 48.0 dBmV 4 Locked ATDMA 4 2560 Ksym/sec 38900000 Hz 47.5 dBmV Tech support was useless today though, they can't escalate till a technician has been on site. Funnily enough the technician has been on site 2 times now. This latest issues though has been on going issue for at least 3 days. Help Desk Ticket Reference: #2942900 Checked with my neighbors, two are experiencing it, a third didn't report any issues and I found three other forum posts, exhibiting the same or similar behavior in my area. Atypical error seen in logs: Started Unicast Maintenance Ranging - No Response received - T3 time-out; My Steps to Reproduce: Saturate your upload bandwidth 100% for 1 to 2 minutes consistently. Time out occurs, the modem may go offline, but the connection is definitely lost. Power levels at the time of upload are approaching 52.0+. It's definitely something new on Cox's end as this has only been an issue for about 72 hours. Any form of upload saturation disconnects the modem, so all connectivity is interrupted. A house full of Netflix users is not a big deal, but the minute I upload something to a FTP or play Destiny utilizing P2P hosting, the whole internet goes offline. I have some time stamps of occurrence, I set my computer to test upload in 5 minute intervals using the newer/unbiased speed test website: http://www.testmy.net Speedtest.net is not really seeing any issue so I looked for alternatives. Packet loss is 0%, unless a T3 time out is just about to occur then we start seeing it go up in %. That's expected since a timeout is in progress. The correlation is that just before disconnection, upload speeds / bandwidths are low. Examples: Fri Oct 09 2015 @ 10:26:16 pm - Upload Speed - 4.59 Mb/s (avg is normally 11.5 Mb/s) Fri Oct 09 22:29:08 2015 Warning (5) Dynamic Range Window violation Fri Oct 09 22:28:33 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 22:28:09 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Further Details: Motorola SB6183, 16xDown, 4xUp, Firmware Version: SB6183-9.2.0.0-GA-04-37-NOSH Firmware reflashed, multiple restarts/resets, removed the router from the equation, checked all fittings, last service visit "replaced" some fittings, not sure what else, they didn't communicate to my wife what they had done. They were here visiting, despite Cox finally admitting to a local outage.3.3KViews0likes6Comments