dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
74733
share rss forum feed

QuasiTime

join:2003-05-28
Playa Del Rey, CA

[Connectivity] No Ranging Response received - T3 time-out

Recently my Comcast connection has gone out of wack. Basically I'm getting intermittent packetloss to my gateway, which is "24.1.156.1". During these times, my upstream powerlevel goes up to around 49-51 dBmV (normal of 47), but my downstream SNR stays pretty normal at 37 dB.

During these problematic periods, my cable modem has trouble establishing "SEND" synch (when power-cycled), whereas normally it has no issue synching up. In addition, the packetloss I notice also occurs to the cable modem's internal address of 192.168.100.1, so both the default gateway (24.1.156.1) and 192.168.100.1 (cable modem) experience packetloss pretty much simultaneously, anywhere from 25-40%. This makes the connection unusable.

There are about 40 messages of "No Ranging Response received - T3 time-out" in my cable modem log file per day. A new one is generated every time the connectivity issues occur. I've looked up this error here on the boards, and it seems to basically boil down to a physical connection issue somewhere between the cable modem and the "CMTS".

How do I get Comcast to address this? I scheduled a tech to come out. The morning they were supposed to come out, they called me and told me my connection looked fine from their end. This is because the problem is intermittent, I tried explaining this to them. Add to that the fact that I live in an apartment complex. They informed me that multiple customers from my apartment complex called in to schedule tech visits, but cancelled since the problem "cleared up". Well...the problem didn't go away, and I'm sure they will be receiving calls again. I'm just frustrated at having to "prove" there is a problem to Comcast. So far my connection has been unusable since the 18th. Anyone have suggestions/advice? It would be much appreciated.



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:10

1 edit

Re: [Connectivity] No Ranging Response received -

You shouldn't notice any change with your upstream at 49-51.
If it goes over 55, you may.

What modem and firmware do you have? Is it leased?

When you called Tech Support, did they say anything about checking your modem for errors?
--
Write me up for 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/


QuasiTime

join:2003-05-28
Playa Del Rey, CA

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

Motorola SB5120
Firmware: 2.14.0.7-SCM00-NOSH

When I call Comcast, they say my modem looks fine. This can't be correct though, since my log file is filled with error messages.



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:10

From their standpoint, your signal levels are not going out of range, thus their statement: "modem looks fine".

I will say that Motorolas are notorious hypochondriacs with T3 timeouts and in general with their logs.

Do you lease the 5120?
--
Write me up for 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/


QuasiTime

join:2003-05-28
Playa Del Rey, CA
reply to QuasiTime

I purchased the 5120 on my own in July...you think it's the modem? But then there's the fact that multiple customers at my complex reported the problem over the weekend.



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:10

1 edit

I don't believe the modem is the issue, however, I'm not pleased with the 5120's performance.
--
Write me up for 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/


QuasiTime

join:2003-05-28
Playa Del Rey, CA

What modem do you recommend I try?



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:10

Of course it is my opinion, but I recommend: Linksys BEFCMU10 v4

»Extreme & BEFCMU10 v4

»Got New Modem- It the New LINKSYS MODEM VERSION!!
Note in that thread my post on identifying a "v3" from a "v4".
--
Write me up for 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/


QuasiTime

join:2003-05-28
Playa Del Rey, CA
reply to QuasiTime

Thanks for the info. I'm going to assume it's not the modem as this point, since I am not the only one experiencing trouble at the complex...

Any more suggestions?



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:10

There is nothing on your end.



Oregonian
Premium
join:2000-12-21
West Linn, OR
reply to QuasiTime

I'm seeing the same thing here in Oregon. I haven't noticed any problem with performance or Internet downtime, though



KyleMI

@flint01.mi.comcast.n

I'm having exactly the same problem. I live in Flint, Michigan. I've called numerous times to get exactly the same responses as you have. I really don't know what else to do about this. It's been going on for nearly a month now.

051123015815 7-Information Synchronization LOST
051123015815 3-Critical R03.0 Ranging Requests Retries exhausted
051123015813 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015812 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015811 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015810 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015809 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015807 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015806 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015805 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015804 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015803 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015801 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015800 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015759 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015758 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015757 3-Critical R02.0 No Ranging Response received - T3 time-out
051123015731 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
051123015729 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL


genesat

join:2002-07-02
Port Huron, MI
reply to QuasiTime

I was having this problem too, just started recently. Any chance you have a router, and it has a MAC clone feature? Turning that off made the T3 error stop appearing in my modem log, and I haven't lost sync again yet.


a1smith

join:2005-01-10
reply to QuasiTime

Re: [Connectivity] No Ranging Response received - T3 time-out

I'm on Comcast and have the same modem:

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

I see multiple T3 entries per day but am not losing synch and not rebooting.

Looking at the number of T3 entries in my log: 1/14 - 10, 1/12 - 5, 1/9 - 4, 1/6 - 16, 1/5 - 2

I had an SB3100 before this modem and it would reboot after receiving too many T3's in a row. With the SB3100 there was a time when I rarely saw the T3 messages, maybe 1-2 years ago? So, it seems like something changed, not sure what.

Here are my signal levels:

Down: 39 dB @ 7 dBmV
Up: 51 dBmV

Scree has a SB5120 signal monitor that you can use to log your signal levels at »home.comcast.net/~scree/ Maybe that will help.



genesat2

@500ash01.tn.comcast.
reply to QuasiTime

Re: [Connectivity] No Ranging Response received -

Disregard what I posted before. It went out again later tonight, so it was just coincidence that changing that had appeared to fix it for me. This outage did let me have the chance to go ask some neighbors I know who have Comcast if theirs were going out. Turns out they were going out at the same time, and Comcast is suppose to be sending a bucket truck out soon because the whole node is having problems.



Uald

@500ash01.tn.comcast.
reply to QuasiTime

Well, seems that bucket truck didn't help me. I have a line tech coming out later this week. The problem seems to be getting worse though (internet went out and came back 7 times in the last hour), which should in theory make it easier for them to find when they come out I hope. My signal appears fine - right up to the time the connection goes out my modem reports 33 SNR at -0.4 to .6 signal strength with a upstream power level of 39db.

Just this over and over:
Time Not Established Critical (3) No Ranging Response received - T3 time-out

Then this:
Mon Jan 16 16:46:07 2006 Critical (3) Init RANGING Critical Ranging Request Retries exhausted

Then the modem loses sync. Anybody have an idea of what piece of equipment of theirs might be having problems?


crobby

join:2005-10-30
Ypsilanti, MI

I am having a similar problem in Ypsilanti, MI. My signal levels are all good...
SNR 35.1 dB
Received Signal Strength: 8.6 dBmV
Upstream Power: 35.2 dBmV

My connection will be tooling along great until about 7:00 PM the past few nights, then poof.....nothing. The modem's lights are all still on, but I can not get to anyplace on the internet. I'm already not using Comcast's DNS servers due to numerous problems before now.

I see the same error message in my cable modem Event log...
Started Unicast Maintenance Ranging - No Response received - T3 time-out 16:36:07 - 12/30/2005 16:32:08 - 01/26/2006 544

The 544 is the number of occurances...seems like a lot to me.

The outages tend to last between 1 and 10 min based on my observations. I don't touch a thing and magically, I can get to the internet again.

I haven't managed to run traceroutes while in one of these outages yet...tonight hopefully (or hopefully not if the problem is "fixed").

Talking with Comcast has been useless to this point (chat, email, phone--all suck). Anything you have found out would be great!!

Thanks in advance!
Chad


iceman2011

join:2006-01-27
Elk Grove Village, IL

post some traceroutes to yahoo.com or google.com. that says alot on where the issue is occuring. if your first hop shows high pings it coming from your end. also logs only show issues the modem sees, it does not show you modem CRC errors or uncorrected FEC which usually signify modem is going bad.



SparkChaser
Premium
join:2000-06-06
Downingtown, PA
kudos:3
Reviews:
·Verizon FiOS
reply to QuasiTime

I've had the 5120 for about 5 months and have been get the same error messages
Time Priority Code Message
060127162425 3-Critical R02.0 No Ranging Response received - T3 time-out
060127153311 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
060127141743 3-Critical R02.0 No Ranging Response received - T3 time-out
060127140124 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
060127140123 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
060127135309 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
060127135309 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
060127135309 5-Warning DHCP: Renew: Another TFTP server IP address
060127124426 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
060127124425 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
060127123509 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
060127123508 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
060127121950 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
060127121950 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
060127121307 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
060127121218 3-Critical R02.0 No Ranging Response received - T3 time-out
060127120046 3-Critical R02.0 No Ranging Response received - T3 time-out
060127115441 3-Critical R02.0 No Ranging Response received - T3 time-out
060127115134 3-Critical R02.0 No Ranging Response received - T3 time-out
060127114626 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast

However, it seems to work fine. No dropouts, good speed, good pings. I guess what I'm saying is that the 5120 seems to go nuts with error messages that don't necessarily mean anything.

When I had the SB4200 on here I didn't have any of the errors but the speed was slower. The SB5120 shows errors but seems to operate normally. 7K down/350 up