|
I have a WCG200 v2 (firmware 2.0.3.9.32-0906) with Comcast in Atlanta, GA and have the following issues: 1.) With even light internet usage such as XBOX Live, I lose connectivity to the internet. 2.) Sometimes, with this loss of connectivity, the modem hard resets itself - i.e., all settings are restored to factory defaults (e.g. wireless is re-enabled, password reset to default, etc. Power cycling the modem usually solves this problem immediately, but that's hardly a permanent solution. I have noticed that this tends to happen more frequently after it has rained, which makes me suspect some Comcast equipment needs fixing - or at least sealing so that moisture doesn't infiltrate the components. If I'm running bittorrent (uTorrent, latest version), this tends to happen within an hour or so. That makes me think the device is wigging out from stress, but my bittorrent settings are pretty dovish (90 max connections, 1 torrent active at a time, 100kB/s max upload on a "3mbps" upload connection). Without fail, upon connectivity loss, I will see something like the following in the modem log: No Ranging Response received - T3 time-out If the device power cycles itself, I usually see something like: 1970-01-01 00:00:22 - critical - SYNC Timing Synchronization failure - Failed to acquire FEC framing And then it puts on some bell bottoms and starts disco dancing! (note the date above) Here's my signal levels: Downstream: power = -3.9 dBmV, SNR = 37.4dB Upstream: power = 38.0 dBmV, SNR = ??? [for Comcast-eye-only, so we can't bust them when their service turns to bovine excrement, which seems to be whenever neighbors come home and load up something with OnDemand] My understanding is that these numbers are within tolerance, but most people report a positive downstream power level and my upstream power level might be on the precipice of unacceptable. Comcast has scheduled a technician for next week, but they asked that I contact Linksys as well. After doing research on the "No ranging response received" issue, I found that lots of people get this problem, but no one ever posts exactly what fixes it. The best answer is something like, "Comcast came and replaced something at the street". Of course, most forum threads end without it being clear a solution was reached at all. I'm hoping this will be the exception. So, some questions: A.) Anyone else having problems like this? B.) Is this the latest available firmware? Does it have known issues? C.) Are there some magic settings I need to enable / avoid? D.) Does this indicate a faulty unit? Let the solutions begin! -- Jesse
|
