New Contributor
•
3 Messages
Started Unicast Maintenance Ranging - No Response received - T3 time-out
Hello,
I recently had a very friendly Cox service tech come to my home in response to my packet loss problem. The problem presented 3 days ago with high severity (my internet access went from very good to outright terrible).
In my initial service phone call I was told that my "signal was low". We replaced many of the box co-ax settings and fiddled with the house wiring a bit and ended up getting an excellent signal (currently -.6 dBmV) but I'm still experiencing packet loss; we did some research together and ran across this old thread:
http://forums.cox.com/forum_home/internet_forum/f/5/t/659.aspx
Looking at my modem logs I'm getting the following:
| Time | Priority | Code | Description |
| 2013-11-20 00:38:40 | 3-Critical | R005.0 | Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 2013-11-20 00:33:33 | 6-Notice | I401.0 | TLV-11 - unrecognized OID |
| 1970-01-01 00:00:41 | 5-Warning | D003.0 | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=00:25:f2:92:0a:29; |
| 1970-01-01 00:00:26 | 3-Critical | R001.0 | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out |
| 1970-01-01 00:00:16 | 3-Critical | R002.0 | No Ranging Response received - T3 time-out |
| 1970-01-01 00:00:08 | 6-Notice | M571.1 | Ethernet link up - ready to pass packets |
| 2013-11-20 00:32:42 | 6-Notice | M573.0 | Modem Is Shutting Down and Rebooting... |
| 2013-11-20 00:32:42 | 3-Critical | R004.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o |
| 2013-11-20 00:32:10 | 3-Critical | R005.0 | Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 2013-11-20 00:15:47 | 6-Notice | I401.0 | TLV-11 - unrecognized OID |
| 1970-01-01 00:00:39 | 5-Warning | D003.0 | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=00:25:f2:92:0a:29; |
| 1970-01-01 00:00:27 | 3-Critical | R001.0 | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out |
| 1970-01-01 00:00:17 | 3-Critical | R002.0 | No Ranging Response received - T3 time-out |
| 1970-01-01 00:00:08 | 6-Notice | M571.1 | Ethernet link up - ready to pass packets |
| 2013-11-20 00:14:57 | 6-Notice | M573.0 | Modem Is Shutting Down and Rebooting... |
| 2013-11-20 00:14:57 | 3-Critical | R004.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o |
| 2013-11-20 00:14:24 | 3-Critical | R005.0 | Started Unicast Maintenance Ranging - No Response received - T3 time-out |
I have no desire to replace my cable modem (a Motorola Surfboard) because I seriously doubt that will clear my problem. From what I've been able to glean from forum boards is that the issue is upstream from me.
Related Content
Closed
1
0
Closed
3
0
Closed
2
0
Closed
0
0
Closed
1
0
ChrisL
Former Moderator
•
7.1K Messages
0
0
Kermut
New Contributor
•
3 Messages
Chris thank you for responding to my post. It's taken me about 10 minutes to write this response because my connection keeps dropping. The tech did not try a test modem. Is there anyway I can get Cox to mail me a test modem to save both of us the hassle of having one of your techs come back?
Thanks!
0
0
ChrisL
Former Moderator
•
7.1K Messages
0
0
Cory_H
New Contributor
•
3 Messages
Same exact issue, multiple times per day (no set time).
Errors generally look like this:
Other errors, which seem to be a lack of response from Cox's systems:
Motorola SBG901 modem was purchased less than a year ago so I'm highly questionable about responses of "incompatible" or "outdated". Problems only started about 2 months ago. Other forums have indicated this is not a modem issue.
Would really like to find a solution as the modem reboot occurs during work, Netflix, etc. and on some systems (e.g. PS3), a hard-reboot of that device is required as well to reconnect. Total pain in the as*.
Thanks.
0
0
ChrisL
Former Moderator
•
7.1K Messages
When I look at your modem from this end it is reporting back signal levels that are out of specification suggesting there may be a signal or equipment problem. Are there any cable splitters you could try bypassing to see if there is an improvement?
0
0
Kermut
New Contributor
•
3 Messages
Chris,
I purchased a new DOCSIS 3.0 SB6141 modem from Amazon and it's working like a charm- BUT
I am still seeing the T3 timeout in the modem log reports every 3-10 minutes. I've been doing some research and I'm pretty sure that you guys have a problem on your end; the difference is that with the extra channels the modem is able to better compensate
http://volpefirm.com/docsis_timout_descriptions/
This makes infinitely more sense to me as an explanation for what's going on then simply saying my modem went "bad".
I'll keep you updated as to how the signal performs as I'm pretty busy and can't take the time to stress test the connection (streaming video etc.).
0
0
Health_Edge
Valued Contributor III
•
4.2K Messages
You guys might want to start your own threads. Its highly unlikely that 3 seperate people, in likly different geographic locations, with 3 different modems, are having the same problem. Same symtoms, yes, but a T3 is a very common symptom of different kinds of signal problems with different causes. It would be like if you all got flat tires, with different cars and tires, in different states. You didnt hit the same pot hole.
I would suggest a new thread with signal levels and any info you can provide about the wiring from the street to your modem.
0
0
ChrisL
Former Moderator
•
7.1K Messages
The connection is actually looking a lot better form this end. A few T3 events are common, let me know how the connection seems overall.
0
0