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
•
Internet Keeps dropping out
I have motorola surfboard sbg6580.
It seem like my internet and wireless keep coming and going. I had a tech out here, but still does not seem like it has gotten any better. This is from my event log, but I do not know what this mean or if I can fix anything on my side of it.
| Wed Jul 24 21:05:50 2013 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 24 09:06:33 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 24 09:05:56 2013 | Warning (5) | Dynamic Range Window violation |
| Wed Jul 24 09:05:52 2013 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 24 09:05:51 2013 | Error (4) | Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Wed Jul 24 09:05:51 2013 | Error (4) | Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.0;CM-VER=3.0; |
| Wed Jul 24 02:16:25 2013 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Tue Jul 23 20:11:47 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Tue Jul 23 09:26:00 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Mon Jul 22 16:39:49 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Mon Jul 22 10:13:23 2013 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Mon Jul 22 00:41:31 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Sat Jul 20 17:11:32 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Sat Jul 20 00:55:05 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Fri Jul 19 11:07:53 2013 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jul 19 09:14:18 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Fri Jul 19 03:46:07 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Thu Jul 18 11:18:29 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Wed Jul 17 22:07:57 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
EdwardH
Valued Contributor
•
The information from the logs is showing issues when it initially getting a connection but the signal levels do not show problems for the tier of service there. When you see the connection drop are the lights changing on the modem or is the status on the computer/device changing losing the network name or stating limited connectivity or local connectivity only?
0
0
Justinal81
New Contributor
•
Wifi drops off for a minute. I changed the channel to see if that would help. I it seems like the wifi just goes and goes.
Justin
0
0
gatormom
New Contributor
•
Hello,
I have been with Cox for a little over a week. And it seems since the second day we had service our internet speeds would come and go. I have a router installed between my modem and PC (not one of the Cox routers) and I have had to reset it several times (multiple times a day). I inspected the routers log files and I noticed we were getting hit with multiple attempts at somebody running a port sniffer on our IP address. When the attack happens it slows down (almost down to 0) the internet and most times I have to reset my router.
"Jul 26 08:54:27 ","SYN-ACK port scan attack from WAN (ip:192.210.54.242) detected."
"Jul 26 08:28:43 ","SYN-ACK port scan attack from WAN (ip:223.4.92.41) detected."
"Jul 26 08:21:14 ","SYN-ACK port scan attack from WAN (ip:178.124.139.201) detected."
"Jul 26 08:13:22 ","SYN-ACK port scan attack from WAN (ip:178.124.139.201) detected."
"Jul 26 08:04:33 ","SYN-ACK port scan attack from WAN (ip:178.124.139.201) detected."
"Jul 26 07:58:18 ","Xmas port scan attack from WAN (ip:74.125.227.118) detected."
"Jul 26 07:58:08 ","Xmas port scan attack from WAN (ip:74.125.227.118) detected."
"Jul 26 07:57:58 ","Xmas port scan attack from WAN (ip:74.125.227.118) detected."
"Jul 26 07:57:48 ","Xmas port scan attack from WAN (ip:74.125.227.118) detected."
"Jul 26 07:57:38 ","Xmas port scan attack from WAN (ip:74.125.227.118) detected."
"Jul 26 07:57:28 ","Xmas port scan attack from WAN (ip:74.125.227.118) detected."
"Jul 26 07:57:18 ","Xmas port scan attack from WAN (ip:74.125.227.118) detected."
Have made several calls to Cox and was given no solution (except that they told me if I enrolled in their home networking program for 9.99 a month they would look into it). They did suggest I send my log files to the abuse group but that does not make my problem go away.
They told me that since I have a router installed between my pc and modem I made my network more susceptible to outside attacks??????????? Ummmm yeah that makes sense Cox! Well in bizzaro world it does.
I have tried two different routers and still have the problem. I have run the modem directly into my PC and I still have the problem.
I hope this is not something Cox thinks I will just take for the money I am paying them.
Just a FYI if this is something similar to you
0
0
Justinal81
New Contributor
•
Doing so research on my end... This is what I think is going on. It sounds like a problem on the line, the dhcp renew warning invalid response and the missing bp configuration settings and dynamic range window sounds like it could be corrupt or missing data coming from cox. The might have to rerun the line to your house or put some kind of noise filter on it. I have had cox come out and check the line and connections with no issues.
Justin Bruster
0
0