ron1973's profile

New Contributor II

 • 

18 Messages

Closed

Random Disconnects in River Ridge / Elmwood, Louisiana Area

After thinking I resolved my internet connection problems with Cox (by way of using the services of the Better Business Bureau) about a year or two ago, I am finding myself in the unfortunate position of having to ask the good people here for your input.

For the last month or so, I have been getting random modem disconnects. At the time, originally, I had an old DOCSIS 2.0 modem, and all of the lights on the modem would go out, except for the power button. When they would come back on, I would have all the appropriate lights lit except for the SEND light and of course the connection light. The SEND light simply kept blinking and I was unable to log onto the internet.

These disconnects happened at random points during the day. Sometimes, they wouldn't happen at all for a day or two...but, inevitably, I would get booted off again completely.

So, I called Cox Cust. Svc and explained to them the problem as best I could. They immediately informed me to switch modems, because according to them the "signals were fine," between myself and them, and they said it might be a bad modem.

They sent out a technician who looked at the line inside the apartment for less than 5 minutes. He said that the signal was fine, etc.. I tried to explain that usually the signals ARE fine, but when things happen, I lose connection COMPLETELY and RANDOMLY. He left saying that since he couldn't see the problem then, there was nothing he could do.

To eliminate the possibility of them continuing to say it was "my modem and router," I got a brand new DOCSIS 3.0 Motorola Surfboard SB6121 AND completely disabled my router (it is no longer even connected to the power supply. I furthermore replaced the Cat5 cabling between my modem and computer, just in case. I even got them to force a firmware update onto my new modem.

Well, lo and behold, the modem ...NEW MODEM...did the same thing as my old modem did, and my computer wasn't even on. I saw it drop as I was just getting home.

I called the service person and explained to him the ongoing drops I have been experiencing and he explains to me that they just got a service flag that the node in my area was undergoing "repairs." I asked him the time...5:50 PM CENTRAL time today. Thats about 5 minutes into my call to him.

I dont know what it is. I scanned for viruses, I got a new modem, I removed the router from the equation and I got a firmware update on said modem. I replaced the cabling, and still noticed the connection drops even when the computer isn't ON.

Please, review this information and see what you think. If you need signal levels on my modem, I would be happy to provide. Pingtest results, same. Pingplotter, same. When the internet works, it works VERY well. The problem is that when it doesn't it falls flat and takes me with it.

Please give me your opinions...Cox reps...I'm definitely interested in hearing from YOU.

Former Moderator

 • 

7.1K Messages

If you could go to http://192.168.100.1 and post the signal levels as well as the modem log that would be quite helpful.

Contributor

 • 

73 Messages

Sounds like you have done everything possible to prove that your equipment is not the source of the intermittent problem, Ron.   I went through this about 2 years ago.  I upgraded to a Motorola SB6120 DOCSIS 3.0 modem to replace what I thought could be a failing DOCSIS 2.0 modem  That didn't solve the problem.   I still had an intermittent problem with dropping lights and connections.   Cox came out and replaced the splitters and connectors on the coaxial cabling for the house.  This resulted in an improvement but didn't solve the problem completely.  Finally, Cox came out again and made measurements with some kind of spectrum analysis gear and isolated the problem to the coaxial cable run feeding my modem.   The problem apparently wasn't with the signal level but was with another parameter that was measured as bad.    They replaced the coaxial cable run and that solved the problem.

Recently, I have been experiencing intermittent loss of response during the evening hours.   The lights on my modem look fine, but I lose Internet response.   My cable modem log is showing some errors.

New Contributor II

 • 

18 Messages

Channel ID 237  238  239  240 
Frequency 849000000 Hz  855000000 Hz  861000000 Hz  867000000 Hz 
Signal to Noise Ratio 38 dB  38 dB  38 dB  38 dB 
Downstream Modulation 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
4 dBmV   4 dBmV   4 dBmV   3 dBmV  

UpstreamBonding Channel Value
Channel ID 4 
Frequency 34450000 Hz 
Ranging Service ID 1160 
Symbol Rate 2.560 Msym/sec 
Power Level 45 dBmV 
Upstream Modulation [3] QPSK
[2] 16QAM
[3] 64QAM
 
Ranging Status Success 

Signal Stats (Codewords)Bonding Channel Value
Channel ID 237  238  239  240 
Total Unerrored Codewords 644003222  644003908  644001714  644002649 
Total Correctable Codewords 446  255  489  841 
Total Uncorrectable Codewords 4336  3791  5763  4471 
Jul 26 2012 13:55:27 6-Notice I401.0 TLV-11 - unrecognized OID
Jan 01 1970 00:03:16 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:02:39 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded;
Jan 01 1970 00:02:35 3-Critical R02.0 No Ranging Response received - T3 time-out
Jan 01 1970 00:01:43 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded
Jan 01 1970 00:01:33 3-Critical R02.0 No Ranging Response received - T3 time-out
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout
Jul 26 2012 13:51:43 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
Jul 26 2012 13:51:43 3-Critical R03.0 Ranging Request Retries exhausted
Jul 26 2012 13:51:41 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 26 2012 13:46:21 6-Notice I401.0 TLV-11 - unrecognized OID
Jan 01 1970 00:03:59 5-Warning D04.1 ToD request sent - No Response received
Jan 01 1970 00:03:44 3-Critical R02.0 No Ranging Response received - T3 time-out
Jan 01 1970 00:03:38 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded
Jan 01 1970 00:03:30 3-Critical R02.0 No Ranging Response received - T3 time-out
Jan 01 1970 00:02:34 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded
Jan 01 1970 00:02:27 3-Critical R02.0 No Ranging Response received - T3 time-out
Jan 01 1970 00:01:38 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded
Jan 01 1970 00:01:37 3-Critical R02.0 No Ranging Response received - T3 time-out
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout
Thank you for looking into this.

Former Moderator

 • 

7.1K Messages

It appears at though the issue may be with the upstream signal/channel.  When was the last time a technician was out to take a look at things?

New Contributor II

 • 

18 Messages

I have been corresponding with LHSIhelp on dslreports.com and he reviewed as well and said that an engineer moved my modem to a different upstream channel.  Will this help?  He has a long history of helping people there.  

But yes, I had a tech, he stuck a reader on the line from the splitter by the TV and said everything was fine, but that was a couple weeks ago.  LHSIhelp made the changes I mentioned today.

Thank you sir.

Reminder: this is a brand new modem with new cables.

New Contributor II

 • 

18 Messages

DownstreamBonding Channel Value
Channel ID 237  238  239  240 
Frequency 849000000 Hz  855000000 Hz  861000000 Hz  867000000 Hz 
Signal to Noise Ratio 38 dB  38 dB  38 dB  38 dB 
Downstream Modulation 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
3 dBmV   3 dBmV   3 dBmV   2 dBmV  

UpstreamBonding Channel Value
Channel ID 2 
Frequency 28050000 Hz 
Ranging Service ID 1160 
Symbol Rate 2.560 Msym/sec 
Power Level 44 dBmV 
Upstream Modulation [3] QPSK
[2] 16QAM
[3] 64QAM
 
Ranging Status Success 

Signal Stats (Codewords)Bonding Channel Value
Channel ID 237  238  239  240 
Total Unerrored Codewords 20437710  20437713  20437715  20437717 
Total Correctable Codewords 42  16  14  14 
Total Uncorrectable Codewords 661  687  688  688 
It did it again.  Just now.  The service rep said just now that other modems " in the building" were reporting their modems flicking off just now, about 20 mins ago she said.  This is consistent with the other gentlemen I reported to a few days ago.  SOMETHING is wrong with the connection here, and its ongoing.

ul 28 2012 12:38:36 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:01:18 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:00:54 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;
Jul 28 2012 12:36:59 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
Jul 28 2012 12:36:59 3-Critical R03.0 Ranging Request Retries exhausted;
Jul 28 2012 12:36:58 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 28 2012 12:35:36 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:01:37 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:01:03 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;
Jan 01 1970 00:04:28 3-Critical R02.0 No Ranging Response received - T3 time-out
Jan 01 1970 00:04:09 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded;
Jan 01 1970 00:04:08 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;
Jul 28 2012 12:28:43 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
Jul 28 2012 12:28:43 3-Critical R03.0 Ranging Request Retries exhausted;
Jul 28 2012 12:28:42 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 27 2012 17:05:11 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:01:26 5-Warning D04.1 ToD request sent - No Response received;

New Contributor II

 • 

18 Messages

Thanks Rob.  It's deeply frustrating for me, because the bills certainly aren't cheap for the service I am getting, and they come out on time and consistently too.  There are few alternatives in my area, as I consider Uverse to even be of lower quality than Cox.  Unfortunately, Cox has purchased our polticians and has a monopoly on cable here, so they're the only game in town when trying to get HSI.

I am not blaming the folks like Chris or the helpful Cox rep on dslreports.com, I am frustrated with the structure itself, and the inability to locate this problem or spend the time from the higher-ups to push down a response.

New Contributor II

 • 

18 Messages

Did it again about 30-45 minutes ago.  No power outage reported in the area according to the cox rep on the phone.  Stayed out for about 20 mins as I was online trying to pay for school.

DownstreamBonding Channel Value
Channel ID 237  238  239  240 
Frequency 849000000 Hz  855000000 Hz  861000000 Hz  867000000 Hz 
Signal to Noise Ratio 38 dB  38 dB  38 dB  38 dB 
Downstream Modulation 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
2 dBmV   3 dBmV   2 dBmV   2 dBmV  

UpstreamBonding Channel Value
Channel ID 3 
Frequency 31250000 Hz 
Ranging Service ID 1160 
Symbol Rate 2.560 Msym/sec 
Power Level 45 dBmV 
Upstream Modulation [3] QPSK
[2] 16QAM
[3] 64QAM
 
Ranging Status Success 

Signal Stats (Codewords)Bonding Channel Value
Channel ID 237  238  239  240 
Total Unerrored Codewords 64599623  64599626  64599627  64599629 
Total Correctable Codewords 18  51  12  16 
Total Uncorrectable Codewords 672  639  678  674 

Jul 29 2012 12:46:21 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:00:38 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;
Jan 01 1970 00:02:11 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;
Jan 01 1970 00:01:43 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to T4 timeout ;
Jul 29 2012 12:39:40 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;
Jul 29 2012 12:39:40 3-Critical R03.0 Ranging Request Retries exhausted;
Jul 29 2012 12:39:39 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 28 2012 16:09:54 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;
Jul 28 2012 16:09:53 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 28 2012 16:09:52 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;
Jul 28 2012 16:09:48 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 28 2012 16:09:46 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;
Jul 28 2012 15:46:44 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:23:31 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:22:42 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:21:02 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded;
Jan 01 1970 00:21:02 3-Critical R02.0 No Ranging Response received - T3 time-out;

New Contributor II

 • 

18 Messages

Keeping an eye on this garbage service.  Did it again just now.  Complete blinkout, no warning, all lights on modem out except power.  Fail.

DownstreamBonding Channel Value
Channel ID 237  238  239  240 
Frequency 849000000 Hz  855000000 Hz  861000000 Hz  867000000 Hz 
Signal to Noise Ratio 38 dB  38 dB  38 dB  38 dB 
Downstream Modulation 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
3 dBmV   3 dBmV   3 dBmV   2 dBmV  

UpstreamBonding Channel Value
Channel ID 3 
Frequency 31250000 Hz 
Ranging Service ID 1160 
Symbol Rate 2.560 Msym/sec 
Power Level 45 dBmV 
Upstream Modulation [3] QPSK
[2] 16QAM
[3] 64QAM
 
Ranging Status Success 

Signal Stats (Codewords)Bonding Channel Value
Channel ID 237  238  239  240 
Total Unerrored Codewords 7676026  7676027  7674794  7674848 
Total Correctable Codewords 11  48  80  104 
Total Uncorrectable Codewords 633  597  1805  1734 

TimePriorityCodeMessage
Jul 29 2012 13:50:55 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:00:38 5-Warning D04.1 ToD request sent - No Response received
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;
Jan 01 1970 00:00:49 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;
Jul 29 2012 13:46:47 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;
Jul 29 2012 13:46:47 3-Critical R03.0 Ranging Request Retries exhausted;
Jul 29 2012 13:46:46 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 29 2012 12:46:21 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:00:38 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;
Jan 01 1970 00:02:11 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset 
Jan 01 1970 00:01:43 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to T4 timeout ;
Jul 29 2012 12:39:40 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;
Jul 29 2012 12:39:40 3-Critical R03.0 Ranging Request Retries exhausted;
Jul 29 2012 12:39:39 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 28 2012 16:09:54 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;
Jul 28 2012 16:09:53 3-Critical R02.0 No Ranging Response received - T3 time-out;

New Contributor II

 • 

18 Messages

And again ... a watched pot DOES boil, apparently.

DownstreamBonding Channel Value
Channel ID 237  238  239  240 
Frequency 849000000 Hz  855000000 Hz  861000000 Hz  867000000 Hz 
Signal to Noise Ratio 38 dB  38 dB  38 dB  38 dB 
Downstream Modulation 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
3 dBmV   3 dBmV   2 dBmV   2 dBmV  

UpstreamBonding Channel Value
Channel ID 3 
Frequency 31250000 Hz 
Ranging Service ID 1160 
Symbol Rate 2.560 Msym/sec 
Power Level 45 dBmV 
Upstream Modulation [3] QPSK
[2] 16QAM
[3] 64QAM
 
Ranging Status Success 

Signal Stats (Codewords)Bonding Channel Value
Channel ID 237  238  239  240 
Total Unerrored Codewords 7945000  7945003  7945005  7945006 
Total Correctable Codewords 12  43  18  46 
Total Uncorrectable Codewords 615  583  608 

580 

Jul 29 2012 14:08:50 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:00:36 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;
Jul 29 2012 14:06:22 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;
Jul 29 2012 14:06:22 3-Critical R03.0 Ranging Request Retries exhausted;
Jul 29 2012 14:06:21 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 29 2012 13:50:55 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:00:38 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;
Jan 01 1970 00:00:49 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;
Jul 29 2012 13:46:47 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;
Jul 29 2012 13:46:47 3-Critical R03.0 Ranging Request Retries exhausted;
Jul 29 2012 13:46:46 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jul 29 2012 12:46:21 6-Notice I401.0 TLV-11 - unrecognized OID;
Jan 01 1970 00:00:38 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;
Jan 01 1970 00:02:11 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;
Jan 01 1970 00:01:43 3-Critical R02.0 No Ranging Response received - T3 time-out;

New Contributor II

 • 

18 Messages

Just a note: whatever they did, did NOT work.  The only other alternative I can think of on my end would be to get a loaner modem from them that ISN'T a Motorola.  Maybe its something weird with the motorola, since both my docsis 2 and now 3 are Motorola.

New Contributor

 • 

6 Messages

have similar issues to you and though the same thing, replace the motorola with something else, didn't help.  Although in my case, the motorola lights would go out during these issues and with the Zoom, the lights stay on.

New Contributor II

 • 

18 Messages

It's a shame, really.  I have read on the Cox HSI forums on dslreports.com that it could be the coaxial cabling that is gone bad outside.  But the oddest thing about it is that this happens during the day (from about 10 AM until 3-5PM).  I suppose its because the wires heat up at this time and the expansion causes the problems.

Just gotta keep hammering away at their customer support until they fix it.  I've got tenacity.  I'll do so.

New Contributor

 • 

1 Message

Chris, I am trying to research this problem myself and I see the same problem from users posting from the left coast to the other.  Started Unicast Maintenance Ranging - No Response received - T3 time-out

It seems as though you have yet to resolve the issue for anyone.  

My firewall is also reporting consistent DOS attacks as well as I have seen other users posting about that same issue.  Big picture, what is Cox doing to look at/resolve this issue that is obviously service impacting, nationwide and cannot go on forever?

Former Moderator

 • 

7.1K Messages

The T3 errors don't represent a systematic problem or one that can be completely eliminated however in large enough quantities they can indicate there is a problem with the return path signal from the modem to us.  DOS attacks wouldn't affect the modem or logs so you wouldn't see such evidence there. If you have a Netgear router it may be experiencing a firmware bug where it continuously sends DNS queries.  That would need to be addressed by Netgear.