suj's profile

New Contributor

 • 

8 Messages

Sunday, October 11th, 2020

Closed

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

I keep getting 

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

Contributor III

 • 

251 Messages

5 years ago

This indicates a problem on your upstream connection. Confirm that all connections are tight. Replace interior cables with brand new high quality RG6 if practical. Remove all unnecessary splitters. If problems persist, contact Cox and request a tech visit as T3 timeouts are often caused by problems outside the boundaries of your property. Post your modem signals and full logs for more complete advice.

New Contributor III

 • 

10 Messages

5 years ago

Same problem here. Repeated dropout of internet connection. In the last 2 days I have had 7 dropouts, lasting 1-4 min


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

Unicast Ranging Received Abort Response - Re-initializing MAC  4 outages

This is occurring on a newly installed Motorola MB7621, after I was told my problem might be with my 2 yr old Netgear CM600

My logs look pretty much like those posted. 

This is a relatively new problem for me. I use VOIP for phone service, and these dropouts are unacceptable, particularly given what I pay for the service



New Contributor III

 • 

10 Messages

I contacted Cox by phone, and was told I should call Motorola :^(

New Contributor

 • 

8 Messages

Power level on my modem look good,  yet get errors. Someone at Cox must know why these errors are going on. 

Contributor III

 • 

251 Messages

See my reply above. If downstream is good but you have T3s, it's most likely a problem off of your property. Call Cox again and talk to someone else.

New Contributor

 • 

8 Messages

Thanks

New Contributor III

 • 

10 Messages

Nobody at Cox will admit to a problem. They continue to deflect the issues with references to hypothetical customer problems. 

How do we get out of this loop?? 

New Contributor III

 • 

10 Messages

5 years ago

There is a fundamental flaw with the cable company dogma that we see repeated here.

In my case, and in others reported here, the events are clustered in time. There is no connection flaw mechanism that would lead to time-related drop-outs.  However, a problem related to congestion and problems at the upstream end in dealing with congestion would explain time dependence. 

The problem with having a Cox technician examine the problem at the customer end is that he will never find the problem if it is some sort of congestion issue. 

I believe that Cox knows exactly what the problem is, and is not telling us because they do not want to spend the time and money to fix it.

But maybe I am wrong and Dave's explanation that these problems are all unrelated coincidences having nothing to do with each other is the answer. 

Moderator

 • 

2.3K Messages

@Bobsun, I recommend sending us an email with your full address and a brief description of this issue to cox.help@cox.com so we can take a closer look for you. -Allan, Cox Support Forums Moderator.

Recent Discussions

View More

Loading...