Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Constant Internet Disconnects Modem T3-T4 errors
We've been having serious internet disconnect errors for 2 months. I have tried every manual reset and requested that Cox reset our connection twice a week. I have not called for service.
I have run all the standard diagnostics with the modem, connected it directly to a laptop with ethernet, and there are no local hardware issues. We have 3 devices that connect wirelessly - 1 apple, 1 windows, and 1 android. All experience the wi-fi outages.
Here is the most recent router log from the Netgear wireless gateway that I bought FROM COX :
| Time | Priority | Description |
| Fri Jun 17 08:54:58 2016 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jun 17 08:54:23 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jun 17 08:53:40 2016 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jun 17 08:51:17 2016 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Fri Jun 17 08:42:05 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jun 17 06:16:56 2016 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jun 17 06:16:21 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Mon Jun 13 08:53:03 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Mon Jun 13 08:52:24 2016 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sat Jun 11 12:12:25 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jun 10 10:06:49 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 13:41:38 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 13:40:34 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 13:38:58 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 13:38:53 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 13:38:35 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 13:38:24 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 13:38:21 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 13:38:15 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 13:37:16 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 10:35:37 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time Out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jun 05 10:33:02 2016 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Sun Jun 05 09:13:30 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Sat Jun 04 12:03:39 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jun 02 14:08:53 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Mon May 30 07:32:56 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Mon May 30 07:31:07 2016 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Sun May 29 20:12:44 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;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 Ranging Response received - T3 time-out;CM-MAC=08:bd:43:60:62:64;CMTS-MAC=00:13:5f:07:0a:78;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Notice (6) | WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT |
Is this a Cox problem that you can fix remotely? I'm ready to throw all the e-hardware off the deck into the ocean.
Tecknowhelp
Valued Contributor II
•
Can't fix T3/T4 errors remotly. Usually a signal issue, with T4 often being caused by downstream SNR problems. What are your signal levels? For specifics, what model Netgear gateway do you have?
Also, do you have any wired computers? Do they also lose internet?
Last, do you see the wireless network disappear or get very weak signal when the wireless problem happens?
0
0
DerrickW
Valued Contributor
•
We can troubleshoot these issues you're having with the disconnects, we'll need to take a closer look at what's going on. Can you send an email with the account information to cox.help@cox.com? We'll get this figured out.
0
0
pesmith79
New Contributor
•
Hi,
If you live in the Northpointe area of Pensacola you don't have internet right now. I just got off the phone with Cox tech support and it might be a few more days or so before we get our internet back. We've been out since about 10:00 am on Friday.
The main stations on the television work but no On Demand or WiFi. Hopefully nobody is depending on their Homelife or Cox home phone because they are based around an internet connection.
0
0
Tecknowhelp
Valued Contributor II
•
Outage wouldn't cause T4..it would cause a outage.
0
0
pesmith79
New Contributor
•
I know, it has caused an outage. Thanks
It's intermittent. It might come on for 30 seconds every 3 minutes or so.
Just venting!
0
0
Tecknowhelp
Valued Contributor II
•
Venting is fine, you just might want to make your own thread to post the details. If there is a issue in a certain area that will have service bad for several days, then that is a important thing to trend. Creating your own thread brings more attention to it then posting on others.
0
0