Observer

No Ranging Response received - T3 time-out

I have been having issues for the past 6+ months with losing internet connection.  I could go 2-3 days without losing connection, or I could lose connection 2-3 times in the matter of a few hours.  I have called TWC many times and all they say is that everything looks fine on their end.  I own my modem (SB6141) and my own router (Netgear Nighthawk X6 R8000).  Each time I lose connection, I can restore it by power cycling the modem (I usually power cycle the modem and router to be safe).

 

I recently started looking at the modem logs, although I don't really know enough to understand what they are telling me.  I've read countless blog posts and websites trying to figure out the solution but with no luck.

 

Does anybody have a potential solution for this?  I have attached the signal specs from my modem as well as the logs (I did a reset to default on my modem today so that's why the logs are so short).

 

Any help is much, much appreciated.  Thanks!

 

DownstreamBonding Channel Value
Channel ID10 11 12 13 14 15 16 
Frequency591000000 Hz 597000000 Hz 603000000 Hz 609000000 Hz 615000000 Hz 621000000 Hz 627000000 Hz 633000000 Hz 
Signal to Noise Ratio38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 37 dB 
Downstream ModulationQAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
-5 dBmV  -5 dBmV  -5 dBmV  -5 dBmV  -5 dBmV  -5 dBmV  -6 dBmV  -6 dBmV  

 

UpstreamBonding Channel Value
Channel ID26 25 27 28 
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID13063 13063 13063 13063 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level42 dBmV 41 dBmV 43 dBmV 43 dBmV 
Upstream Modulation[3] QPSK
[3] 16QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[3] 16QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID10 11 12 13 14 15 16 
Total Unerrored Codewords141553986 140560632 140569787 140578321 140553961 140556002 140556385 140569705 
Total Correctable Codewords13 12 15 18 30 28 18 
Total Uncorrectable Codewords605 1365 1304 1399 1578 730 1450 1516 

 

TimePriorityCodeMessage

Jun 17 2016 11:14:533-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 11:14:536-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 11:14:535-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:313-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

 

 

 

 

Everyone's Tags (2)
26 REPLIES 26
Expert

Re: No Ranging Response received - T3 time-out

resetting the modem cleared out historical/ vital information.. Repost the signal level and error log pages in a couple hours.

 

 I'll bet you have a router problem, either theres a time server issue or the wireless is locking up due to interference...

 There could also be coax side issues. causing the latter

 

Observer

Re: No Ranging Response received - T3 time-out

Thanks, MsRaye!  I'll post the logs again after the issue occurs again.

 

I'm surprised you think it might be the router, since when the issue occurs I am able to get internet back by only resetting the Modem.  Isn't the T3 error an error in communication between my modem and the ISP?

Expert

Re: No Ranging Response received - T3 time-out

repost levels and log BEFORE the problem occurs and stuff gets reset/cleared out


@jmartin207 wrote:

Thanks, MsRaye!  I'll post the logs again after the issue occurs again.

 

I'm surprised you think it might be the router, since when the issue occurs I am able to get internet back by only resetting the Modem.  Isn't the T3 error an error in communication between my modem and the ISP?


yes a T3 is a modem to head end issue but that doesn't cause a lockup.... A T4 will reset the modem

 

 I'll bet you can reset this by resetting the router only.

 

Observer

Re: No Ranging Response received - T3 time-out

Ok will do. I just checked the logs again now and nothing new since the original post.

The globe (internet) indicator on the modem remains lit when this issue occurs. I have tried only resetting the router when this happens and once the router reboots I still have no internet. In all of the previous logs I reviewed, I never noticed a T4.

I'll keep checking the logs and will re-post them once they include new records. Thanks!
Expert

Re: No Ranging Response received - T3 time-out

something in the router is off, possibly the time server.. Is the router set to autodetect wan settings?

Do you have the NTS on and the correct time zone?

 

Observer

Re: No Ranging Response received - T3 time-out

I tried taking a screenshot and uploading it but I can't figure out how to upload.

 

My WAN Setup page on my router shows this:

Disable Port Scan and DoS Protection (unchecked)

Default DMZ Server - 192.168.1.0 (unchecked)

Respond to Ping on Internet Port (unchecked)

Disable IGMP Proxying (CHECKED)

MTU Size (in bytes) 1500

NAT Filtering - Disable SIP ALG (Secured radio button is checked)

 

For NTS...I haven't been able to find that in any of the router pages.  The Wireless Setup page shows Region: North America, but that is the only thing I've seen related to geography/time zone.  It's grayed out so I can't change it.  I even googled and don't see anything come up about Netgear R8000 NTS.  Any idea where I can find it?

 

Observer

Re: No Ranging Response received - T3 time-out

I found the time settings in the Security menu (I didn't know what NTS was so had to google it Smiley Happy ). I just changed it to Eastern - do you think that will help?

 

However, I just checked the time on my modem and my modem time is an hour behind (maybe it doesn't adjust for daylight savings?).  Do you think the different time between the two could be an issue?

Expert

Re: No Ranging Response received - T3 time-out


@jmartin207 wrote:

I found the time settings in the Security menu (I didn't know what NTS was so had to google it Smiley Happy ). I just changed it to Eastern - do you think that will help?

 

However, I just checked the time on my modem and my modem time is an hour behind (maybe it doesn't adjust for daylight savings?).  Do you think the different time between the two could be an issue?


Ok, that's good, No DST EST changes on TWC, doesn't matter

 

As for one item, you may want to click the disable DOS protection so that DOS protect is disabled

 

Observer

Re: No Ranging Response received - T3 time-out

I clicked to disable DOS protect.

 

The disconnect issue happened again a little while ago. Here are the logs from the modem:

TimePriorityCodeMessage

Jun 17 2016 17:51:523-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 17:51:516-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 17:51:515-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 14:21:083-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 14:21:086-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 14:21:085-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 11:14:533-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 11:14:536-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 11:14:535-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:313-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;