Constant Internet Disconnects Every 5 Mins Due to Dynamic Range Window Violation
Hello. I've been having a lot of trouble with my Cox internet lately due to constant internet drops. The internet has been so unstable that it disconnects about every 5 minutes making my home internet useless. When checking the router logs I noticed that the message consistent with the drops are noted by "Dynamic Range Window Violation". As per the advice of the online Cox Support representative, I replaced my modem/router setup; did not improve/solve the problem. During the disconnects, the UPSTREAM LED constantly blinks indicating that there may be some trouble with the upstream channels bonding. Currently using a NETGEAR CM500 modem connected directly to the wall without a splitter. I appreciate any and all help!! Sample Event Log: 2017-6-26, 22:49:15 Warning (5) Dynamic Range Window violation 2017-6-26, 22:49:46 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2017-6-26, 22:50:00 Warning (5) Dynamic Range Window violation 2017-6-26, 22:50:46 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2017-6-26, 22:50:46 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2017-6-26, 22:50:46 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2017-6-26, 22:51:45 Warning (5) Dynamic Range Window violation 2017-6-26, 22:52:31 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2017-6-26, 22:52:32 Warning (5) Dynamic Range Window violation 2017-6-26, 22:52:46 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2017-6-26, 22:53:15 Warning (5) Dynamic Range Window violation Sample Connection Status1.8KViews0likes0CommentsIntermittent Email send/receive failures with POP3 - Again, for weeks
I posted this a couple weeks ago, have received no responses, and discovered it was deleted. So I'm posting it again. Don't delete it again...please solve it. For the past few weeks now, I've been experiencing the infamous & intermittent email send/receive failures, like many other customers in these forums have reported. My system specs: Windows 10 Pro x64 MS Windows Defender active, no other security packages MS Outlook Cox Internet Preferred package with the Cox provided DOCSYS 3.0 NetGear N450 modem/router My issues: For several weeks, my various Cox email accounts have intermittent problems sending or receiving emails through Outlook 2007. When receiving emails, I'll get the Outlook pop-up error window stating: ------------------------------------------------------------------- "Task 'myemailaddress' - Receiving' reported error (0x800CCC92 or some other error code) : 'The operation timed out waiting for a response from the receiving (POP) server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP)." ------------------------------------------------------------------- This issue happens consistently, several times a day with all my Cox email accounts...then emails will suddenly work again...then the issue reappears, rinse & repeat...it's an ongoing cycle of working/not working throughout the day for the past few weeks now. I don't bother calling Support about this because they usually blame Outlook and do nothing. It's not an Outlook problem. Everything works great, when it works...then this sudden issue pops once or twice a year, as so many other customers have been reporting. And as mentioned by other customers, Cox somewhat acknowledges that they know about this problem with email and it's been kicked upstairs for a harder look. In the past, I've reset my Outlook settings for the Cox emails, tried different settings and ports according to the Cox email support docs, and even deleted my Cox email account profiles within Outlook and recreated them (in case they were corrupted). Nothing has worked. This happens regularly, so please Cox...don't ask the usual questions about using Webmail, trying another computer, etc. We know, and you know, this has been a persistent, recurring issue with Cox email accounts for many years and these suggestions don't work or fix anything. Usually, Cox Support hems & haws and says they're working on it...or they wrongly blame Outlook...and nothing gets resolved. After repeated complaints to report the issue, they'll usually reset or do something to solve the issue. So I'm adding my issue & complaint here to be resolved also. Please fix this email issues ASAP. Thank you.8.8KViews0likes17CommentsInternet shutting off
So whenever I turn on my Xbox and play online, eventually my wifi will turn off. The router will still be on, but the wifi light shuts off and we lose wifi throughout the whole house. The wifi will only turn off when the xbox is connected online. Any explanation why this happens?1.2KViews0likes1CommentKindle tv connect complaint
Dear cox I have iPods and Amazon tablets, however I prefer the dozen kindle fire and fire hd and fire HDX tablets. Coffee and watching channels on the back deck is very enjoyable. Please fix your cox tv connect app as again it has changed all will not work on the newer kindle HDX tablets. Says must update but not in the app store anymore. I sell and recommend these tablets to tons of cox customers. They enjoy the cox service so much more with the convenience of the tv connect app and now they have lost it.1.8KViews0likes1CommentSTILL HAVING PROBLEMS WITH MY INTERNET AFTER 6 MONTHS OF NO ONE REALLY FIXING IT!!! HELP???
THESE ARE MY LEVELS.....THEY GIVE ME FLUCTUATING UPLOAD AND DOWNLOAD SPEEDS. I HAVE THE ULTIMATE PACKAGE, AND YET HAVE FAILED TO SEE THE ULTIMATE SPEEDS!..... BELOW IS THE LEVELS AND MY EVENT LOG! Procedure Status Comment Acquire Downstream Channel 939000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK ^1/5D1F5F68/132003 Security Enable BPI+ Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR 1 Locked QAM256 94 939000000 Hz 10.1 dBmV 38.3 dB 2 Locked QAM256 93 933000000 Hz 9.7 dBmV 38.6 dB 3 Locked QAM256 95 945000000 Hz 10.3 dBmV 38.2 dB 4 Locked QAM256 96 951000000 Hz 10.4 dBmV 38.6 dB 5 Locked QAM256 89 909000000 Hz 9.1 dBmV 37.9 dB 6 Locked QAM256 90 915000000 Hz 9.1 dBmV 38.2 dB 7 Locked QAM256 91 921000000 Hz 9.3 dBmV 38.1 dB 8 Locked QAM256 92 927000000 Hz 9.0 dBmV 37.5 dB Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 35102000 Hz 41.5 dBmV 2 Locked TDMA and ATDMA 1 2560 Ksym/sec 20202000 Hz 41.8 dBmV 3 Locked TDMA and ATDMA 2 2560 Ksym/sec 23402000 Hz 41.8 dBmV 4 Locked ATDMA 3 5120 Ksym/sec 28202000 Hz 41.8 dBmV AND HERE IS MY EVENT LOG Time Priority Description 2015-12-16, 02:35:00.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:34:18.0 Notice (6) TLV-11 - unrecognized OID;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:34:18.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:21:18.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:20:36.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:19:26.0 Critical (3) Resetting the cable modem due to docsDevResetNow 2015-12-16, 02:19:17.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:19:00.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 01:29:20.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 01:28:38.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 01:16:24.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-15, 17:28:11.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-15, 03:44:10.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-14, 13:46:42.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-13, 17:35:00.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-13, 17:34:17.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-13, 16:48:05.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-13, 14:37:02.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 22:43:11.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 12:51:40.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 08:10:20.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 08:10:20.0 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 08:10:20.0 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 02:07:32.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-11, 09:20:53.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-10, 17:28:06.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-10, 13:15:53.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-09, 23:43:36.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 4 (Side-Band Channel:N/A) - Reason:INIT Time Not Established Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:N/A) - Reason:INIT3.8KViews0likes2Commentstrash folder
This just started happening to me. I lost hundreds of trash files. I need to stop this and since it just recently happened there must be some way to stop it. Cox please fix this. Forum: Internet Forum Posted: 30 Jun 2014 Post Subject: trash folder Post author: lucky when I delete emails to the trash folder, the next day the folder automatically dumps. how can I keep trash folder from doing this so I can delete trash folder manually?0Views0likes0Comments