Reply
Contributor
Posts: 15
Registered: ‎03-17-2004

No Ranging Response received - T3 time-out Error

I get this error every day.

Tech support (Phone)---NO HELP.

3-Critical R02.0 No Ranging Response received - T3 time-out

Modem logs SB 5100

Software Version: SB5120-2.14.0.7-SCM00-NOSH
Hardware Version: 4
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4

Signal
Frequency 627000000 Hz
Signal to Noise Ratio 33 dB
QAM 256
Network Access Control Object ON
Power Level 2 dBmV 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


Upstream Value
Channel ID 2
Frequency 30992000 Hz
Ranging Service ID 1079
Symbol Rate 2.560 Msym/s
Power Level 58 dBmV


My connection does a slow decline over a day or two. I reboot the modem and all is well for a few hours. I am ready to put my modem on a timer and reboot every day.

Any solutions
Regular Problem Solver
Posts: 2,846
Registered: ‎11-02-2003

Re: No Ranging Response received - T3 time-out Error

Navy....
Your UPstream level is WAY high...right at the "break-off" point to sync loss......UPstream power should normal in the upper-30s to upper 40s, with anything over 50 considered suspect...
BTW....Your SNR is right at the "edge" for QAM256, too.....33dB is considered MINIMUM for the new architecture...SNR much below 30dB could start your modem randomly rebooting, trying to find a good signal.....Have you checked ALL your coax connections - inside and OUT? Are they all clean, tight and DRY? Same with all coax runs....any splits, cracks, sharp bends/kinks/pinches? If you come through the "inspection" clean, you probably should call Comcast and have them come out and do a COMPLETE signal/noise level check....and be sure to have the tech report the numbers he/she finds back to YOU prior to leaving the site...Good luck!
Regular Contributor
Posts: 94
Registered: ‎10-03-2003

Re: No Ranging Response received - T3 time-out Error

you are not alone.

050405183058 3-Critical R02.0 No Ranging Response received - T3 time-out
050405182709 3-Critical R02.0 No Ranging Response received - T3 time-out
050405181458 3-Critical R02.0 No Ranging Response received - T3 time-out
050405174516 3-Critical R02.0 No Ranging Response received - T3 time-out
050405170913 3-Critical R02.0 No Ranging Response received - T3 time-out
050405165852 3-Critical R02.0 No Ranging Response received - T3 time-out
050405164716 3-Critical R02.0 No Ranging Response received - T3 time-out
050405164715 3-Critical R02.0 No Ranging Response received - T3 time-out
050405164511 3-Critical R02.0 No Ranging Response received - T3 time-out
050405164509 3-Critical R02.0 No Ranging Response received - T3 time-out
050405161847 3-Critical R02.0 No Ranging Response received - T3 time-out
050405161335 3-Critical R02.0 No Ranging Response received - T3 time-out
050405160739 3-Critical R02.0 No Ranging Response received - T3 time-out
050405151709 3-Critical R02.0 No Ranging Response received - T3 time-out
050405151058 3-Critical R02.0 No Ranging Response received - T3 time-out
050405150808 3-Critical R02.0 No Ranging Response received - T3 time-out
050405150134 3-Critical R02.0 No Ranging Response received - T3 time-out
050405143859 3-Critical R02.0 No Ranging Response received - T3 time-out
050405134633 3-Critical R02.0 No Ranging Response received - T3 time-out
050405133708 3-Critical R02.0 No Ranging Response received - T3 time-out
050405124642 3-Critical R02.0 No Ranging Response received - T3 time-out
050405124641 3-Critical R02.0 No Ranging Response received - T3 time-out
050405122334 3-Critical R02.0 No Ranging Response received - T3 time-out
050405122212 3-Critical R02.0 No Ranging Response received - T3 time-out
050405120659 3-Critical R02.0 No Ranging Response received - T3 time-out
050405120658 3-Critical R02.0 No Ranging Response received - T3 time-out
050405120404 3-Critical R02.0 No Ranging Response received - T3 time-out
050405120009 3-Critical R02.0 No Ranging Response received - T3 time-out
050405111810 3-Critical R02.0 No Ranging Response received - T3 time-out
050405110641 3-Critical R02.0 No Ranging Response received - T3 time-out
050405101235 3-Critical R02.0 No Ranging Response received - T3 time-out
050405095452 3-Critical R02.0 No Ranging Response received - T3 time-out
050405093940 3-Critical R02.0 No Ranging Response received - T3 time-out
050405093939 3-Critical R02.0 No Ranging Response received - T3 time-out
050405093615 3-Critical R02.0 No Ranging Response received - T3 time-out
050405093614 3-Critical R02.0 No Ranging Response received - T3 time-out
050405093146 3-Critical R02.0 No Ranging Response received - T3 time-out
050405092922 3-Critical R02.0 No Ranging Response received - T3 time-out
050405090546 3-Critical R02.0 No Ranging Response received - T3 time-out
050405090545 3-Critical R02.0 No Ranging Response received - T3 time-out
050405090214 3-Critical R02.0 No Ranging Response received - T3 time-out
050405083636 3-Critical R02.0 No Ranging Response received - T3 time-out
050405082739 3-Critical R02.0 No Ranging Response received - T3 time-out
050405082738 3-Critical R02.0 No Ranging Response received - T3 time-out
050405074812 3-Critical R02.0 No Ranging Response received - T3 time-out
050405074811 3-Critical R02.0 No Ranging Response received - T3 time-out
050405062822 3-Critical R02.0 No Ranging Response received - T3 time-out
050405061314 3-Critical R02.0 No Ranging Response received - T3 time-out
050405060944 3-Critical R02.0 No Ranging Response received - T3 time-out
050405052817 3-Critical R02.0 No Ranging Response received - T3 time-out
050405051832 3-Critical R02.0 No Ranging Response received - T3 time-out
050405051831 3-Critical R02.0 No Ranging Response received - T3 time-out
050405045258 3-Critical R02.0 No Ranging Response received - T3 time-out
050405033916 3-Critical R02.0 No Ranging Response received - T3 time-out
050405031855 3-Critical R02.0 No Ranging Response received - T3 time-out
050405031712 3-Critical R02.0 No Ranging Response received - T3 time-out
050405023303 3-Critical R02.0 No Ranging Response received - T3 time-out
050405011551 3-Critical R02.0 No Ranging Response received - T3 time-out
050405005506 3-Critical R02.0 No Ranging Response received - T3 time-out
050405003758 3-Critical R02.0 No Ranging Response received - T3 time-out
050405002907 3-Critical R02.0 No Ranging Response received - T3 time-out
050405001510 3-Critical R02.0 No Ranging Response received - T3 time-out
050405001248 3-Critical R02.0 No Ranging Response received - T3 time-out
050405000838 3-Critical R02.0 No Ranging Response received - T3 time-out
050404235120 3-Critical R02.0 No Ranging Response received - T3 time-out
050404235119 3-Critical R02.0 No Ranging Response received - T3 time-out
050404233828 3-Critical R02.0 No Ranging Response received - T3 time-out
050404233808 3-Critical R02.0 No Ranging Response received - T3 time-out
050404233151 3-Critical R02.0 No Ranging Response received - T3 time-out
050404231944 3-Critical R02.0 No Ranging Response received - T3 time-out
050404231943 3-Critical R02.0 No Ranging Response received - T3 time-out
050404231047 3-Critical R02.0 No Ranging Response received - T3 time-out
050404230342 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
050404230340 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
050404230340 7-Information 7 I500.0 Registration Completed
050404230340 7-Information SEC: Co-Signer CVC from configuration file was verified
050404230339 7-Information B401.0 Authorized
050404230339 7-Information REGISTRATION COMPLETE - Waiting for Operational status
050404230339 7-Information 7 D509.0 Retrieved TFTP Config SUCCESS
050404230339 7-Information Registration file - downloaded
050404230338 7-Information Trying to download Configuration file ...
050404230338 7-Information 7 D507.0 Retrieved Time....... SUCCESS
050404230338 7-Information Time of day - retrieved
700101000014 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
700101000014 7-Information DHCP - parameters acquired
700101000010 7-Information 7 T500.0 Acquired Upstream .......... SUCCESS
700101000010 7-Information Trying to register through CMTS...
700101000010 7-Information SYNCHRONIZED - 711000000 Hz , ucd 3
700101000008 7-Information Starting Ranging On Channel 3
700101000004 7-Information Downstream Locked - Collecting Upstream Information
700101000004 7-Information 7 T501.0 Acquired Downstream (711000000 Hz)........ SUCCESS
700101000002 7-Information Scanning frequency 711000000Hz
700101000001 7-Information Trying to synchronize ...
700101000001 7-Information Vendor Cold Start
050404215401 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=17800BE Info:0005)
050404213047 3-Critical R02.0 No Ranging Response received - T3 time-out
050404212924 3-Critical R02.0 No Ranging Response received - T3 time-out
050404211547 3-Critical R02.0 No Ranging Response received - T3 time-out
050404211546 3-Critical R02.0 No Ranging Response received - T3 time-out
050404211525 3-Critical R02.0 No Ranging Response received - T3 time-out
Event Log has reached maximum size. Older log entries are lost.

Status | Signal | Addresses | Configuration | Logs | Help
© Copyright 1997-2000
Regular Contributor
Posts: 94
Registered: ‎10-03-2003

Re: No Ranging Response received - T3 time-out Error

Frequency 711000000 Hz
Signal to Noise Ratio 34 dB
QAM 256
Network Access Control Object ON
Power Level 0 dBmV
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
Upstream Value
Channel ID 3
Frequency 24000000 Hz
Ranging Service ID 479
Symbol Rate 2.560 Msym/s
Power Level 53 dBmV


i wonder how come you dont work at comcast? cuz all the technicians that come to my house cant see a problem
Connection Expert
EG
Posts: 43,023
Registered: ‎12-24-2003
Connection Expert
EG
Posts: 43,023
Registered: ‎12-24-2003

Re: No Ranging Response received - T3 time-out Error

Eight year old thread closed.