Cable internet connection constantly timing out -- Help me!!

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.


+++++++++++++
I have the same problem with Comcast in Auburn GA, I had no issue with my Internet for 3 years and one day out of the blue mayor issue. see below!!

2009-09-13 23:41:20 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1)
2009-09-13 23:41:15 6-Notice M572.0 Max T3 No Rng Rsp Timeouts - Reinitialize MAC...
2009-09-13 23:41:15 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2009-09-13 23:41:15 3-Critical R006.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
2009-09-13 23:41:15 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out

This is a True Comcast network problem you do not have to change any cable modems or routers in your house. The issue is outside of your house. What you see in your cable modem is a soft reboot "Max T3 No Rng Rsp Timeouts - Reinitialize MAC..."

I had Comcast out in our Sub Division for days working a this same issue and they resolved for 5 days but now it is back. I have a new work order open.

Keep the pressure on Comcast to fix the issue.

I feel your pain...

Keep us posted.
 
Ok, I hope to shed some light on everyone's issues and pull the curtain back a little. I WAS a Charter Communications Senior System Tech. I was responsible for maintaining and repairing all mainline issues. The problem that you guys are having is, i repeat, IS a problem with your cable companies hardline distribution plant. In other words, don't waste your time or money replacing modems and or routers. If you are experiencing problems at certain times of the day, it is related to temperature. I know that sounds crazy, but hardline cable is metal. It expands and contracts with hot and cold temperatures just like any other metal substance. When this happens, the metal is either less dense(when hot) or more dense(when cold). Therefore, the signal passes differently depending on the temperature. Causing higher or lower signals when the sun comes up or goes down. Now, to battle this phenomenon, the amplifiers hanging on the lines are designed to automatically adjust the Gain (signal boost) accordingly. Now, these have to be adjusted and set up properly at least a couple times a year. Mainly due to the changing of the seasons. They can only handle so much temperature change before they start to cause serious errors. Thus your problem begins. Now keep in mind, that most newby service techs for most cable companies are clueless about anything to do with mainline issues. They are only trained to diagnose problems inside your house, and depending on their training(which usually isn't much) they probably won't even know any of this. Also, in most areas, the service techs are scared to put in a "Line Problem" because if they have missed any problems inside your house that could be causing the problem, then they are given a hard time by the system techs (who will find it). So, you should definitely insist that a line problem be put in. Also, talk with any of your neighbors and see if they are having the same issues at the same time. This will help you in your request for a line problem.

Hope this helps

Justin
 
2009-09-27 12:12:23 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-27 09:32:22 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-26 21:42:25 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-26 21:28:24 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-26 21:12:33 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-26 21:08:24 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-26 20:34:27 5-Warning B502.6 TEK Invalid - Invalid Key Sequence Number
2009-09-26 20:34:24 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-26 19:05:27 6-Notice M572.0 Max T3 No Rng Rsp Timeouts - Reinitialize MAC...
2009-09-26 19:05:27 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2009-09-26 19:05:27 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted
2009-09-26 19:05:27 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
1970-01-01 00:00:13 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
2009-09-26 18:16:24 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-26 16:52:24 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
1970-01-01 00:00:13 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-09-26 15:56:11 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-26 15:21:15 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-09-26 14:48:10 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-26 13:56:12 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-26 13:46:11 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-26 13:30:12 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-26 13:20:11 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-26 13:10:13 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-26 12:52:32 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-26 10:48:13 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-26 10:24:20 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-26 01:18:46 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-09-26 00:58:15 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-25 22:04:03 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-09-25 16:14:17 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-25 15:46:17 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-25 06:58:20 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-25 06:20:19 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-24 21:30:19 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-24 20:42:27 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-09-24 15:54:21 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-24 15:52:21 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-24 15:24:21 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-24 10:42:28 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-24 10:26:22 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-24 07:28:23 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-24 07:02:23 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-24 06:53:06 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-09-23 19:16:35 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-23 19:04:25 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-23 18:46:30 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-23 18:28:27 5-Warning B502.6 TEK Invalid - Invalid Key Sequence Number
2009-09-23 18:28:24 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-23 17:04:25 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-23 16:54:25 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
1970-01-01 00:00:11 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:02 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-09-23 14:10:25 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-23 10:42:57 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:17 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:02 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-09-22 17:14:34 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-22 14:43:10 6-Notice M572.0 Max T3 No Rng Rsp Timeouts - Reinitialize MAC...
2009-09-22 14:43:10 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2009-09-22 14:43:10 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted
2009-09-22 14:43:10 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-22 14:07:07 6-Notice M572.0 Max T3 No Rng Rsp Timeouts - Reinitialize MAC...
2009-09-22 14:07:07 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2009-09-22 14:07:07 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted
2009-09-22 14:07:07 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-22 13:58:16 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-21 16:38:19 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-21 15:20:40 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-09-21 14:46:21 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-20 17:10:23 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-20 16:48:23 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-20 11:24:26 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-20 10:52:25 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-19 23:42:26 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-19 23:06:27 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-19 22:32:26 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-19 22:14:27 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-19 21:52:26 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-19 21:50:27 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-19 20:04:31 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
1970-01-01 00:00:14 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:02 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-09-19 17:06:25 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-18 21:58:27 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-18 21:06:27 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-18 18:18:28 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-18 18:10:28 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-18 16:20:20 6-Notice M572.0 Max T3 No Rng Rsp Timeouts - Reinitialize MAC...
2009-09-18 16:20:20 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2009-09-18 16:20:20 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted
2009-09-18 16:20:20 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-18 16:14:23 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-17 21:48:23 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-17 21:44:23 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2009-09-17 17:33:38 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-09-16 20:46:26 3-Critical R002.0 No Ranging Response received - T3 time-out (US 8)
2009-09-16 20:27:05 6-Notice M572.0 Max T3 No Rng Rsp Timeouts - Reinitialize MAC...
2009-09-16 20:27:05 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel


This is just a little more than a week of my connections. I have had a tech come out and litterally replace everything includeing routers splitters cables reset up everything i own bypassed the router and it all worked fine for about 6months now i am having all these drops and i dont know what to do? They just tell me everything is fine from their end.

Frequency 549000000 Hz
Signal To Noise Ratio 35.8 dB
Power Level 4.4 dBmV
Upstream Value
Channel ID 8
Frequency 31600000 Hz
Power 45.7 dBmV
This is a SB5101 modem.
 
Well where to start... have been a cox customer for several years now and haven't really had much issues until about 4 months ago other than the occasional service outage during a storm. Then a little over 4 months ago I started experiancing intermittent loss of connectity in which at the same time the device would reboot. The first few times this happend I assumed this was loss of signal or a renewal of my IP address from Cox.

After several occurences I decided to call tech support and start troubleshooting. Everytime the linksys would self-restart everything was fine, so it was difficult to explain as each time I called Cox would test and see no problems. So they sugguested the device may be losing power. I switched outlets and replaced the surge protector with a new one but the problem kept occuring.

Next Cox explains that this is related to bad coax cable in my house, so they send out a tech which cost a few hundred to check the cabling inside and outside my house, but the problem kept occuring.

Further troubleshooting led to being told that the hardware was bad, so I bought another WCG200 unit and guess what same issues with the new one. Luckily I was able to return the open unit but had to pay a 15% restocking fee to the retailer.

Further troubleshooting with Cox sent me over to Linksys whom explained that this was a known issue and they informed Cox that they needed to update my firmware as it appeared to be quite outdated. So Cox pushed out a new version of the firmware which didn't work and another call to Linksys had me default my device and reconfigure the device. Then it started working and I thought for sure the issue was fixed.

Same problem came back later that night but now is more frequent like every 4 hours the device has to be restarted as the previous issue with the self-restart doesn't occur. Atleast before the firmware upgrade the unit worked but would restart it'self and was more of an annoyance then anything.

Another call back to Cox and I am told that even though it is a compatible device and supported per their website that I would need to purchase another brand of modem and a seperate wireless router combination to restore my stable internet connection out of pocket. I was then transferred over to sales support who explained they wouldn't send out a device to test with that I need to buy this and that "technology changes" so I needed to buy another unit, even though their website still says this is a compatible unit?

Every time I call Cox tech support it is like I have a mystery device as each call takes anywhere from 1 to 2 hours just to get to the point of Teir1 to lead to Teir2 support or eventually to linksys. I have probably spent atleast 36hours on the phone with their support and each time getting another story or hypothetical diagnosis which is costing me (customer) to troubleshoot to no avail. The signals have been checked every call, the modem has been re-provisioned numerous times...

After the most recent firmware upgrade by Cox I got the modem log feature so I plugged a few of the log errors into a search engine and low and behold this problem appears to be very wide spread amongst this device and various ISP's and definetly related to firmware. It appears that each ISP works with Linksys to get firmware releases and the last few have caused quite a bit of issues. It does appear as Comcast has made the most progress in this department and has recently released a new updated version of the firmware that fixes these issues, but from what I can tell they have many more customers on this model than my ISP.

Anyways, I notice there were a few Cox TOC members that browse these sections to help from time to time and I am hoping someone can shed some light on this. It is my understanding that this is the only group within Cox tech support that has any understanding in this process.

here is my information:

Model: WCG200 (version 1)
Firmware Version: 2.0.3.9.31-0418

Standard Specification Compliant DOCSIS 1.0/1.1/2.0
Hardware Version 1.2b
Software Version 2.0.3.9.31-0418
CM Certificate Installed

Status:

System Up Time 0 days 00h:09m:12s
Network Access Allowed
WAN DHCP IP Address Lease D: 01 H: 00 M: 00 S: 00

Connection:

Acquire Downstream Channel 843000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+

Downstream Channel

Lock Status Locked
Modulation 256QAM
Channel ID 207
Provisioned Rate 11500 kbps
Symbol Rate 5360.537 Ksym/sec
Downstream Power 4.6 dBmV
SNR 37.4 dB

Upstream Channel

Lock Status Locked
Modulation 16QAM
Channel ID 1
Provisioned Rate 2300 kbps
Symbol Rate 2560 Ksym/sec
Upstream Power 36.0 dBmV

Modem Log Errors;

Time Priority Description
2010-02-01 21:27:59 notice TLV-11 - unrecognized OID
2010-02-01 18:31:03 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2010-02-01 18:31:02 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-02-01 18:31:02 critical SYNC Timing Synchronization failure - Failed to acquire FEC framing
2010-02-01 18:30:34 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2010-02-01 11:04:37 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-01-30 20:50:15 critical No Ranging Response received - T3 time-out
2010-01-28 12:38:09 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-01-27 23:10:52 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-01-27 19:49:54 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-01-27 09:13:34 critical DHCP WARNING - Non-critical field invalid in response.
2010-01-27 09:13:17 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2010-01-27 09:12:55 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2010-01-27 08:21:20 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2010-01-24 14:04:24 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:03:29 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
 
After having the same "connection drop" problem with charter communications (in Janesville WI here) - and changing out my modem, checking ever setting known to man with my router, and calling a service tech to check the lines, I've come to realize that its probably easier to find a better alternative ISP than it is to find a tech good enough to resolve the issue.

Finally, as one last attempt tonight, i cleared my modem log and just played a game of Team Fortress 2 until it happened again, then immediately went to my modem, logged in, and copied the log.

Fri Feb 12 23:58:07 2010 Fri Feb 12 23:58:07 2010 Information (7) Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID ...
Fri Feb 12 23:58:07 2010 Fri Feb 12 23:58:07 2010 Information (7) SA Map State Machine Started
Fri Feb 12 23:57:47 2010 Fri Feb 12 23:57:47 2010 Information (7) Authorized
Fri Feb 12 23:57:46 2010 Fri Feb 12 23:57:46 2010 Information (7) Registration complete!
Fri Feb 12 23:57:46 2010 Fri Feb 12 23:57:46 2010 Information (7) We registered with a DOCSIS 1.1 config file!
Fri Feb 12 23:57:46 2010 Fri Feb 12 23:57:46 2010 Information (7) Received a REG-RSP message from the CMTS...
Fri Feb 12 23:57:46 2010 Fri Feb 12 23:57:46 2010 Information (7) Sending a REG-REQ to the CMTS...
Fri Feb 12 23:57:46 2010 Fri Feb 12 23:57:46 2010 Information (7) CableModem SNMP configure complete
Fri Feb 12 23:57:41 2010 Fri Feb 12 23:57:41 2010 Information (7) IP init completed ok
Fri Feb 12 23:57:41 2010 Fri Feb 12 23:57:41 2010 Information (7) CableModem TFTP init ok
Time Not Established Time Not Established Error (4) ToD request sent- No Response received
Time Not Established Time Not Established Information (7) CableModem DHCP client init ok
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Beginning initial ranging...
Time Not Established Time Not Established Information (7) downstream time sync acquired...
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) starting ds time sync acquisition...
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Beginning initial ranging...
Time Not Established Time Not Established Information (7) Initial ranging ABORT, re-scanning downstream
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) Beginning initial ranging...
Time Not Established Time Not Established Information (7) downstream time sync acquired...
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) starting ds time sync acquisition...
Time Not Established Time Not Established Information (7) Locked on the downstream. Waiting for UCDs...
Time Not Established Time Not Established Information (7) Downstream lock ok
Time Not Established Time Not Established Information (7) Sync Start
Fri Feb 12 23:54:45 2010 Fri Feb 12 23:54:45 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...

Prior to this I was getting several "T3 Time-out" errors in my logs, but I believe those were caused by mac-address cloning (a feature I read would cause those problems from time to time) - those are not the disconnects we are experiencing however, they just make for a messy log. The important part is the "received response to broadcast maintenance request, but no un(..icast Maintenance opportunities received - T4 timeout). So, since it looks like that message is tied to the actual lines, there is no way to fix it if a tech can't 'figure it out'. The hardest part is that so many customers out there are absolute idiots, that it's impossible to get a tech to even give those of us with REAL issues to resolve the problem. I'm fed up with years of bad charter service (and I do mean YEARS, they are a HORRIBLE company and I can't wait to see them fully bankrupt for the huge debt they owe as it is - this is not rage, simply how I've come to feel from about 13 years of 'working the system' to get help from them, but I'm done playing those games with charter).

Whats worse though, is I'm pretty damn good with computers, I feel absolute pity for every person who DOES have legitimate problems like this, but doesn't know enough to get it resolved - they just have to suffer the problems and probably get a constant feeling of "if only I knew computers better, i could resolve this" - I know because several members of my family were like this.

Charter, I'm sorry, but I'm done.
 
All this information is very useful. Weird thing is that I only get timed out on certain websites. i.e. facebook etc. I can log onto yahoo, google, ask, etc all the time without a lick of problems. I too am running linksys router for wireless with Comcast cable internet to the main RCA router. I can log onto these websites through my companys wifi internet with no problems but at home its religous I will get a timed out connection at least 3 times before connecting. I haven't really looked at what the pinging #'s are at different times as I probabley should. I do play a online game that occasionally gets slow and will rarely disconnect me. But I believe that to be a problem with the compacity the server is experiencing at a givin time. (i.e. the problem on ther end not mine) Anyways Thank you guys and anymore insight would and could be useful.

I am running Windows Vista a/b/g with linksys wireless g router. I am only in the next room from wherethe Comcast cable router and linksys router are. I dont believe it to be a signal strength problem.
 
I am also having a problem with dropped connections. It consistently happens at least once a day, sometimes several times a day. Every now and then we can go two or three days at most with no drops. We use Mediacom, our modem is a Mediacom supplied Thomson DCM425, and is connected to a D-Link DIR655 wireless router. We also have several splitters on the line for our cable TV. I did find a temporary fix to get the internet back up and running. It just takes a few of minutes and has worked without fail for the past couple of weeks (minimum of 10x). I have an old motorola modem (we switched modems a while back thinking that might be the issue) that I keep handy. When my connection drops, I unplug the Thomson modem and remove both the cable and the ethernet cable from the back. Then I remove the ethernet cable that connects my computer to the router and plug it into the Motorola modem. I connect the cable line to the Motorola modem, and then plug it in. Within a couple of minutes, I have an internet connection. But I don't use it like this (otherwise no wireless, and no other computers on my network will have internet, not to mention having to register the new MAC address which my cable company charges $1.99 to do!), I unplug everything I just plugged in and hook it back up the way it was before. Without fail, I have my internet connection back up again. Sounds confusing, but basically you are just connecting your computer directly to the alternate modem (not through a router), waiting for the connection to come up, then putting everything back again. Not sure why this works. Seems like there should be an easier way to do this. It's almost like the connection needs to be reset or something. I have tried using the reset button on the back of the modem (many, many times) and it rarely (maybe 1 out of 15 times) brings my connection back up. I have also tried unplugging everything (modem, router, computer) and waiting 5+ minutes, then plugging everything back in. Also rarely works. Although I don't consider this an actual solution, at least it gets my internet connection back up and only takes a few minutes.
 
Not 100% sure if this is the culprit, but I had a charter tech which took 2 hours at my house tracking down the problem once..

He changed the house line, modem , house to pole, then started backtracking to the C/O.

He found a bad line amplifier on a pole about 5 houses down.....

His explanation: Within the line amp, there are circuits which measure the resistance down the line to the next amplifier. The resistance of the line changes 24/7 due to "thermal expansion/contraction (temperature variance)", there are internal compensation amplifiers which will increase or decrease output down the line to attempt to maintain X dbmv output down the line. The circuits can and do wear/ burn out over time. If this is outage occurring consistently in mornings / evenings / both times, the amplifier may have reached the limit of its adjustment. Then the expensive and quantitative option of the cable co. is "the number of subscribers from that point to end of line" worth the cost of running a new line because thermal cycling has prevented the run to stay in specifications for internet / cable.

Simply you become a $ value...
 
"Started Unicast Maintenance Ranging" .... failed.... also coincided with a Zone Alarm message that I got saying about the same thing "tarted Unicast Maintenance Ranging" ...blocked... where my ZA settings blocked an attempt to connect to my computer. I then logged into the router and traced the attempted connection back to my sons laptop, which was trying to set up a network with others on the LAN using the wireless connection through the router.
 
I also had this same problem in Turlock ,Ca
A simple 79$ fix (about a years modem rental) I bought a Motorola Surfboard modem.
problem fixed.
No more dropping to desktop or connection lost messages.
Online all the time
 
This may be the reason you keep timing out.

Turn off the ip6 settings on your lan/network adapter under the Control Panel, System, Device Manager. Also, change your internet options to limit data speed to 10mb/s (instead of 100mb/s). Many cable modems cannot communicate with ip6 and timeout. I have one mobo that has no issue with ip6 and another must be turned down to ip4. Try this before you invest tons of money.
 
I too am having a problem with my laptop /wireless connection dropping- I constantly am "repairing" the connection on the systray which I guess is renewing the ip address every time. Occasionally I can reload, and I can get it to work that way. But usually a repair is required- At first it was less frequent ; now it is every few minutes. I get "problem loading server check network connections " or something to that effect, or an email error depending on which application i'm using. Our pc /desktop doesn't have this issue ( but my eee pc does-- the only laptop constantly connected- my husband can use his dell w/ no problem but rarely connects here, so I don't know). The laptop runs windows xp, and the desktop runs vista if that matters. and I've also tried calling Belkin ( the router) and our cable company , Brighthouse networks/ road runner-- They say there is no problem in the line, and the Belkin tech had me change the channel on the router to 11 . That did not solve the problem. I am going to see if my husband's palm hot spot w/ verizon does the same thing , if i connect my laptop that way-- If it does, I guess i will know it has something to do w/ the isp-- At first I thought it was my email or something, because the connection never used to do this ever. In fact Brighthouse/road runner has been a great provider aside from this issue which may or may not be attributed to them. I Just want to fix it, because it is very annoying to constantly repair the connection 🙁-- Any help is appreciated--
 
UPDATE to mine-- i actually found a solution after months 'i think' - thank someone named Brian for this who posted this on another forum, if it works for you too!
The following very simple solution worked for me. This will not solve your problem if both your pc and laptop are dropping the connection- but if it is just your laptop having an issue, give it a go.
I turned the network adapter power save mode to off and the problem stopped, here are the steps:
- click "Start"
- click "Control Panel"
- click "Classic View"
- doubleclick "System"
- select "Hardware" tab
- click "Device Manager" button
- click "+" to left of "network adapters"
- doubleclick "Atheros AR5007EG ...."
- click "Advanced" tab
- select "Power Save Mode"
- select "off"
- select "OK"
 
hey all,
i am a computer consultant, systems engineer/administrator, i however do not work for a cable company and have limited knowledge about specifics for cable fiber technology. however i have a firm grasp on networking.

i have had perfect service from RR(oceanic-timewarner) in hawaii until i moved to a new residence.
the house had never had cable service, so when i got it installed it was fresh from the pole to the house to the cable modem. instantly i had issue with modem rebooting etc. i also have the digital phone service.
checking the scientific-atlantic modem reveals t3 time outs and some OID errors there are a few sync ones etc that seem to coincide with the dropped packets(ie connection dropping)

the reason i am posting is that even being able to understand the problem i have had considerable trouble MAKING them fix it. so long story short: i was able to PROVE my problem over and over so that they cannot deny it.(make them responsible to pay my bill and fix the problem)
after swapping out modems, cables, routers, computers, fresh installs, network cards etc... which was all just for the sake of saying it had been done, since the digital phone was also cutting out. also just to note i dont have cable tv so no splitters amps etc. just pole -> house -> cable modem all lines run by the cable company...
so the first tech gave me an older model modem that was "less sensitive" so that instead of rebooting and all the lights resetting every time there was an issue(sometimes every 2-3 min othertimes not for a day or two) it would just drop the connection then pick it back up a few heartbeats later.

so the biggest symptom is playing a game, everything freezes and either a disconnection or then everything goes fast to catch up... like it froze 3 sec then all comes up to speed. very annoying especially when it should be working great(like i said i had no problems at the other house, which i will note was in another district on the island)

ok so heres the meat:
---------------------------
start menu > run(or on windows 7 hold the windows key between alt/ctrl and tap R)
type in CMD and hit OK
type: ping -t google.com
hit enter
this will start an endless loop of packets going to google.com; you should notice that when the internet is idling there should be a consistent stream of packets flowing in at a similar millisecond(ms) value... ie mines 55ms-66ms with an idle connection.(note: im in hawaii yours should be lower)
so now, i goto the speedtest page for oceanic time warner(speedtest.oceanic.com) your ISP might have something similar, its good to use your own ISP's so that you can truly flood the internet connection to its max vs maybe being bottle necked on some internet router outside of your ISP which might not prove the problem...
ok so anyways i run 2 tests at the same time... one to speedtest.oceanic.com and the other to speedtest.net
now i watch my ping test and see the milliseconds start to go all over the place, then eventually packets are lost indicated by the "request timed out" message
also i can note that there is a pause in the speedtest indicator.
so i had a t2 tech support guy on the phone watching my modem while i was doing this and he was able to see that the signal to noise ratio was going out of spec.
---------------------
i got the modem last december 2009. its now november 2010 and i still have the problem. i felt bad for the techs for awhile because it was hard to replicate the problem, but i still knew there was a problem, can hear static/cutouts on the digital phone, game lags, dropped packets etc... but they where still trying to dodge the bullet... i gave them the benefit of the doubt; told the tech i hoped they'd find the problem in their system since they said it wasnt at my house and stopped calling to complain.
time goes by, same problem, getting pissed off trying to use the internet service i pay for and its constantly a hassle. I charge my clients 65$/hr to troubleshoot problems for them, considering how much ive spent on my own personal problem its troubling for me to recommend their service to anyone else even though ive had it for the last 8 years at other homes with no problems.....
so the only thing they havent done on my house is replace the faceplate on the telephone pole, re-run the line to the house and re-run the line to the cable modem. otherwise they have some fked up setting in their system that needs to be addressed. i feel bad for the people without the techincal experience to pin it to these corporate hogs so here you go; hope it helps!
btw, they have told me that i can get a refund from the first time i called to complain, ie january of this year since they refunded december right off the bat because the service was blatantly broken($600 to stand up for what is right. but i still have to fight them for it)
good luck
-themeONE

ps just some basic info:
most cable modems can be accessed at http://192.168.100.1 and there is a log file that can be helpful, especially to show that its not YOUR equipment with a problem. also it should have the signal specs.
i had lots of techs come up but they never saw the specs fluctuate on the modem, mostly because it was idle while i was on the phone complaining.
from what ive read on the net your cable modem should be within these specs:
--------------------------
downstream power: -15dbmV to +15dbmV
upstream power: 30dbmV to 53 dbmV
signal to noise ratio(SNR): 33db or more
--------------------------
 
Status
Not open for further replies.