Reply
Contributor
Blown4Six
Posts: 11
Registered: ‎12-01-2010
Accepted Solution

Started Unicast Maintenance Ranging, HELP

I am very very dissatisfied with Comcast. The service I have been getting is horrible. My internet connection is so unstable I cannot use the computer, my xbox, anything that uses the internet. This happens directly connected to my Motorola Surfboard modem or through my router.

 

I've had a Comcast tech come to my house 2 times now, and nothing has been changed other than a few connections tightened up, which the first time they came out got my SNR up to within acceptable ranges. The second time he came out and changed out a splitter that was meant for an amplifier when I had no amplifier.

 

Internet is spotty, sometimes it will work for a day, three days, half a month, and it always comes back to this. I keep getting: Started Unicast Maintenance Ranging - No Response received - T3 time-out

And when this happens my internet will drop every 10 seconds or 30 seconds, couple minutes etc.. It varies but usually when I get the T3 timeout it will drop every 10 seconds or so it seems and I cannot do anything that requires internet connectivity.

 

Anyone have any insight on the error  Started Unicast Maintenance Ranging - No Response received - T3 time-out?

Connection Expert
EG
Posts: 41,710
Registered: ‎12-24-2003

Re: Started Unicast Maintenance Ranging, HELP

Power levels ? Get them here; http://192.168.100.1

 

Copy and paste them in to your next post.

Contributor
Blown4Six
Posts: 11
Registered: ‎12-01-2010

Re: Started Unicast Maintenance Ranging, HELP

[ Edited ]

Downstream

------------------------------------------

Frequency  (747000000 Hz Locked)

Signal to Noise Ratio  (36 dB )

Power Level  (-5 dBmV)

 

Upstream

---------------------------------------------

Channel ID 1

Frequency (37200000 Hz Ranged)

Power Level (42 dBmV)

 

Log

--------------------------------------------------

2010-12-02 02:16:41     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:06     3-Critical     R002.0     No Ranging Response received - T3 time-out
2010-12-01 22:07:12     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 22:06:39     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:01:22     3-Critical     R002.0     No Ranging Response received - T3 time-out
1970-01-01 00:01:18     3-Critical     R003.0     Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:01:18     3-Critical     R002.0     No Ranging Response received - T3 time-out
1970-01-01 00:00:37     3-Critical     R003.0     Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:37     3-Critical     R002.0     No Ranging Response received - T3 time-out
1970-01-01 00:00:55     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
1970-01-01 00:00:23     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 21:34:07     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 21:33:35     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:21     3-Critical     D002.0     DHCP FAILED - Request sent, No response
1970-01-01 00:00:10     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 21:16:24     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 21:15:52     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 21:14:59     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 21:14:26     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:01:19     3-Critical     D001.0     DHCP FAILED - Discover sent, no offer received
1970-01-01 00:01:02     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:55     3-Critical     D001.0     DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:44     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:30     3-Critical     R002.0     No Ranging Response received - T3 time-out
2010-12-01 20:59:31     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 20:58:59     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:03:01     3-Critical     D002.0     DHCP FAILED - Request sent, No response
1970-01-01 00:02:52     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:02:48     3-Critical     R002.0     No Ranging Response received - T3 time-out
1970-01-01 00:01:51     3-Critical     R003.0     Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:01:51     3-Critical     R002.0     No Ranging Response received - T3 time-out
1970-01-01 00:00:43     3-Critical     R003.0     Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:43     3-Critical     R002.0     No Ranging Response received - T3 time-out
2010-12-01 20:55:07     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 20:54:35     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:05     3-Critical     R002.0     No Ranging Response received - T3 time-out
2010-12-01 20:45:30     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 20:44:58     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 20:43:23     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 20:42:51     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:40     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
1970-01-01 00:00:07     3-Critical     R002.0     No Ranging Response received - T3 time-out
2010-12-01 15:44:34     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 15:44:02     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 15:33:40     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 15:33:07     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 09:03:04     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 09:02:32     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 08:32:26     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 08:31:53     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 07:50:32     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 07:50:00     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:53     3-Critical     D001.0     DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:42     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:36     3-Critical     D001.0     DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:35     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:27     3-Critical     D001.0     DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:15     3-Critical     R002.0     No Ranging Response received - T3 time-out
2010-12-01 07:18:35     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 07:18:03     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 07:01:21     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 07:00:48     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 06:35:08     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 06:34:35     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 04:52:49     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 04:52:17     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 04:16:59     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 04:16:26     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:03:20     3-Critical     D001.0     DHCP FAILED - Discover sent, no offer received
1970-01-01 00:01:21     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:01:12     3-Critical     D001.0     DHCP FAILED - Discover sent, no offer received
1970-01-01 00:01:11     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:40     3-Critical     D001.0     DHCP FAILED - Discover sent, no offer received
2010-12-01 03:05:10     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 03:04:37     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:24     3-Critical     R002.0     No Ranging Response received - T3 time-out
2010-12-01 03:00:49     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 03:00:17     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-12-01 02:49:51     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 02:49:18     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:05     3-Critical     R002.0     No Ranging Response received - T3 time-out
2010-12-01 02:33:38     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-12-01 02:33:06     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-11-28 03:22:24     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-11-25 15:31:16     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:02:13     3-Critical     I002.0     REG RSP not received
1970-01-01 00:02:06     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:01:59     4-Error     D004.3     ToD request sent- No Response received
1970-01-01 00:01:53     3-Critical     D002.0     DHCP FAILED - Request sent, No response
1970-01-01 00:01:43     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:01:05     3-Critical     R002.0     No Ranging Response received - T3 time-out
1970-01-01 00:00:47     3-Critical     R003.0     Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:47     3-Critical     R002.0     No Ranging Response received - T3 time-out
2010-11-25 08:51:44     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-11-25 08:51:12     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:15     3-Critical     D001.0     DHCP FAILED - Discover sent, no offer received
2010-11-25 08:49:42     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-11-25 08:49:10     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:01:39     3-Critical     R002.0     No Ranging Response received - T3 time-out
1970-01-01 00:01:33     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing

 

Contributor
Blown4Six
Posts: 11
Registered: ‎12-01-2010

Re: Started Unicast Maintenance Ranging, HELP

[ Edited ]

 

 

*edit* I failed to put in my first message that I had scheduled for a tech to come out today and they were going to swap out my modem to try and remedy the problem, because they cannot see any problem on their end.

 

I've looked up the error "Started Unicast Maintenance Ranging - No Response received - T3 time-out" on google, look it up for yourself! There are many people with the same problem, and it involves CC doing more than just swapping out modems. People have had to put great effort into having CC resolve the issue because everything always seems fine on their end so they point the finger at the customer when it's a problem with the isp.

 

 

And now, CC called and said that they will not be coming out because they think the problem is fixed, that it was just a power outage.... Thats the 3rd or 4th time there has been a "power outage" in my area.

 

Not happy, i'll be very displeased if this isnt the issue.

 

 

 

 

 

Contributor
Blown4Six
Posts: 11
Registered: ‎12-01-2010

Re: Started Unicast Maintenance Ranging, HELP

[ Edited ]
2010-12-02 13:31:503-CriticalR005.0

Started Unicast Maintenance Ranging - No Response received - T3 time-out

Still happening

2010-12-02 15:52:483-CriticalR005.0Started Unicast Maintenance Ranging - No Response received - T3 time-out
Contributor
Blown4Six
Posts: 11
Registered: ‎12-01-2010

Re: Started Unicast Maintenance Ranging, HELP

Update:

 

Called CC again today (thursday) and politely explained my situation, and the CSR that I talked to was helpful and was actually able to see my modem go down while I was on the phone with him, which was relieving since every time before they couldn't see any problem with my line.

 

Long story short, he had me bring my modem into a local comcast service store and exchange my Motorola SB. I ended up getting a Arris Touchstone WBM460a modem. It seems like its a pretty decent modem, and I picked the modem up at around 6pm on thursday 12/2. So far the internet has been perfect and I've been actually seeing faster down speeds than I did with my old motorola modem. Anyone have any expirence with the Arris modems?

 

We'll see how long it lasts. I'll update this if anything changes.

Regular Problem Solver
Posts: 2,841
Registered: ‎11-02-2003

Re: Started Unicast Maintenance Ranging, HELP

[ Edited ]

Have heard of some connection issues with the Moto 6120....I'm trying to get CC to get firmware passed to mine for Extreme, which I upgraded to from Ultra.....Right now I'm waiting in the "24 to 72 hour" window for the changeover to occur.....

When I leased my modem from CC it was a Cisco DPC3000...then I decided to own mine outright and went with the Moto.....

Good luck!

Connection Expert
EG
Posts: 41,710
Registered: ‎12-24-2003

Re: Started Unicast Maintenance Ranging, HELP


dsanbo wrote:

I'm trying to get CC to get firmware passed to mine for Extreme, which I upgraded to from Ultra.....Right now I'm waiting in the "24 to 72 hour" window for the changeover to occur.....


I think you mean config-file/bootfile.

Regular Problem Solver
Posts: 2,841
Registered: ‎11-02-2003

Re: Started Unicast Maintenance Ranging, HELP

EG.....

Thanx for the correction.....you're right!

Contributor
Blown4Six
Posts: 11
Registered: ‎12-01-2010

Re: Started Unicast Maintenance Ranging, HELP

12/4/2010 19:03820002003No Ranging Response received - T3 time-out;CM-MAC=00:1d:cd:ba:6b:7c;CMTS-MAC=00:1b:d5:fe:82:b8;CM-QOS=1.1;CM-VER=3.0;
12/4/2010 20:20820003003Ranging Request Retries exhausted;CM-MAC=00:1d:cd:ba:6b:7c;CMTS-MAC=00:1b:d5:fe:82:b8;CM-QOS=1.1;CM-VER=3.0;
12/4/2010 20:20820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:1d:cd:ba:6b:7c;CMTS-MAC=00:1b:d5:fe:82:b8;CM-QOS=1.1;CM-VER=3.0;
12/4/2010 20:20840201004Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=00:1d:cd:ba:6b:7c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
12/4/2010 20:2024171643066MDD IP mode Override Mode=0;CM-MAC=00:1d:cd:ba:6b:7c;CMTS-MAC=00:1b:d5:fe:82:b8;CM-QOS=1.1;CM-VER=3.0;
Contributor
Blown4Six
Posts: 11
Registered: ‎12-01-2010

Re: Started Unicast Maintenance Ranging, HELP

........


Still happening? Really?

Contributor
Blown4Six
Posts: 11
Registered: ‎12-01-2010

Re: Started Unicast Maintenance Ranging, HELP

[ Edited ]

UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1232.00 MHz41.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 1204747.00 MHz-3.74 dBmV35.60 dB256QAM4265688590
Downstream 2201729.00 MHz-4.32 dBmV34.77 dB256QAM40941821300
Downstream 3202735.00 MHz-4.99 dBmV34.93 dB256QAM40652618970
Downstream 4203741.00 MHz-3.83 dBmV35.42 dB256QAM40738210580

 

So I am getting the same errors with my new Arris modem... I'm on the phone with CC as I am typing this and they are sending out 2 techs. One to check just the line from the pole to the house, and the other to check in the house again. This will be the third time I've had a tech come to my house, and every time they come, everything looks fine to their little scan computer machines. I dont know where to go from here, make them run a new line to my house?

Contributor
Blown4Six
Posts: 11
Registered: ‎12-01-2010

Re: Started Unicast Maintenance Ranging, HELP

Finally had a level 4 tech come out to my house, thank you CC.

 

Comcast is in the clear, for now. Seems that my problems stemmed from older TV's that were sending signal back through the cable out to the post, and also some older lines ran through the house. /facepalm Which was causing my modem to have problems talking back to the network, which was (i'm guessing)  causing the "No Ranging Response Recieved." timeout.

 

So the problems were coming from my house pretty much the whole time, but I just dont understand why it took 3 trips for CC to send someone that was competent enough to figure that out! Glad things are somewhat straightened out. Now, to replace the older tube tv's that were causing the problems. Does CC cover that? lol :smileysilly: