10-01-2009 09:02 PM
10-06-2009 10:55 PM
Hi all, hey Dave,
I got a really smart guy, Brian, helping me from Cisco Irvine Headquarters, but it was not easy to get to the right person.
You should call cisco support and tell them that you have this router and that only Irvine division has the ability to fix it. I was told that it is only them who knows how to fix it. They won't transfer you immidiately though, they can only submit the tickets for Irvine to call you. So take your case number and tell them to submit the ticket.
Within 48 hours they should call you and set up a conference call with Comcast. You'll need your Comcast information (phone# and etc.) and it is Comcast who will push an update for your firmware and everything is going to be just fine.
At least this is what happened to me, I have ver. 2 though and I am with Cox. However, I did ask Brian about Comcast and basically it's the same story there too. If it is the same problem like mine and you need the firmware upgrade that is the case.
Good luck everyone, hope this will help.
Nookeen
10-27-2009
11:32 PM
- last edited on
10-27-2009
11:54 PM
by
OnnagokorO
I lived with this mess for like 7 months. When you call linksys they say they can't update the firmware because the cable company has to do it. Plus Time Warner seems very reluctant to help solve any problems on modems not rented from them.
I ended up getting a Different wireless N router from Frys for like $20. Disabled Nat and Routing and used the WGC200 as a modem only.
It's too bad because I used to think very highly of the Linksys brand, but not after dealing with customer service reps with both Linksys and Time Warner.
Tisk Tisk...
11-25-2009 11:32 AM
Folks -
Just had an amazingly pleasing experience with Cox and the WCG200. My dad has been complaining about Cox for many many months, and I finally decided to see what I could do to help. This forum was a big help as it relates to WCG200v2 firmware -- the punch line of this story is that after upgrading the firmware (his cable-modem/router was about three years old), his network is working PERFECTLY.
When I realized (1) his firmware was badly out of date, and (2) THE ONLY WAY YOU CAN UPDATE THE FIRMWARE is by going through Cox, we reached the conclusion that we'd rather buy a new device and pay the $100 in order to avoid going through Cox support. I started looking for the latest and greatest DOCSIS 3.0 combo modem/router device that was available locally for him, and realized there are only a couple of options. I decided I'd take a fly at upgrading his firmware, and since you know the punchline (we did it and it fixed all of his problems), let me cut to the chase. Here's what I did:
- Instead of calling Cox, I went through their Chat support online. I was ready to barrage the agent with tons of info that would demonstrate that I knew what the hell I was doing and that all I wanted was a firmware update. If you do this, be ready with all of your account info -- account number, pin, address, phone number and last four of the social security number.
- Once I got over the first hurdle (supplying all the account info), I told the rep the model number of the device and cut-and-pasted the firmware revision that's currently running. (By the way - someone on this forum posted a message saying that Cox keeps an eye on this and updates it when necessary - that's a bunch of mularky. Complete and total mularky. Not only that, but my dad has been calling Cox with problems for months and NO ONE has looked at the fact that his firmware is several years out of date.)
- I then pasted in the modem log error messages showing all of the disconnects. At this point, the agent knewhe was chatting with someone who knew what he was doing and said "I'm going to transfer you to a Level 2 technician.". I told him that would be fine, and did a Tiger Woods fist-pump.
- The level two technician came on to the chat line, introduced himself, and said "so you need your firmware upgraded?". I told him yes, and he started the upgrade process.
- In ten minutes, from the time I started the chat to the time the router was restarted, THE PROBLEM WAS FIXED.
I promise you -- if you try to go through the level one help desk and talk through the problem, they're going do diddle around, waste your time and eventually frustrate you to the point where you'd rather not have an interenet connection than deal with Cox. But by going through the chat support team and getting right to the level two tech with a specific request to update the firmware, I had the best support experience I can remember having. TEN MINUTES.
JUST TELL ME HOW TO DO IT!!! - If you're in Arizona using a WCG200v2, look at your firmware revision number. You do that by typing in "192.168.0.1" into the URL field in Internet Explorer. You'll be prompted for a username and password -- if you haven't screwed with it, it's a blank username and a password of "admin" (no quotes). At the top of the screen on the right side, you'll see your firmware revision number. As of November, 2009 (the time of this post), the proper number for this device on Cox's network in Arizona should be: Firmware Version: 2.0.3.9.31-0214. (If you're in a different area of the country or you're, say, a Comcast customer, this might not be the correct version. Just look at yours compared with this one -- if the fourth digit isn't a "9", you probably need to get your firmware updated.)
Prior to the upgrade, mine was 2.0.3.5.something -- obviously quite a bit older... And since the new firmware was installed (a week or so now), we haven't had a single disconnect. It's running perfectly -- responsiveness and speed is light-years better. And my dad is done griping about his crappy internet service and telling me how much he hates Cox. Sound familiar???
Take my advice - If you're a Cox customer with a WCG200, run -- don't walk -- to your PC and get your WCG200 firmware upgraded. And save yourself some pain -- CHAT with the COX techs and get your problem escalated to a level 2 tech who can do the firmware update. You will LOVE the improvement, and it won't cost you hours of your life and boatloads of frustration.
- John
11-30-2009 07:29 PM
12-15-2009 04:23 PM
12-24-2009 05:25 AM
All -
I've had this problem through 3 of these WCG200 v.2 modems over a period of 4 years. In the past there were a lot of complaints about Linksys not correcting the problem, but with Firmware Version: 2.0.3.9.31-0214 the problem seems to be fixed. I am on Cox in the Hampton Roads area of Virginia, and used the section "JUST TELL ME HOW TO DO IT!!!" posted by brooks0455 as a script when going online to the Cox Chat support folks. I did have have some difficulty with the initial Chat contact...Romina was the name used. Romina seemed to have a cut and past script that kept telling me I needed to contact the manufacturer of my equimpent to get updates. She was applying the "broken record" technique to get me to go away, and as a last attempt, she asked me if there was anything else she could help me with. At that point I replied, "Yes. You can connect me to tier 2 support". I was surprised that I didn't meet resistance at that request, but in a few minutes I was connected to Juan. I told Juan that I had a Linksys WCG200 v.2 with firmware version 2.0.3.5.xx-xxxx and needed it upgraded to the recommended version of 2.0.3.9.31-0214. He asked me to hold on for a bit, then returned and told me my modem would lose connection and reconnect. Since the firmware has been updated there have been no dropouts or other disconnects. For what it is worth, I have a seperate headless Server 2003 system that I monitor the modem with, and it has recorded no disconnects since the firmware upgrade. If you have a WCG200 v.2 and are experiencing connectivity loss, I highly recommend you investigate your firmware version and a possible update.
Joe
01-05-2010 02:12 PM
01-12-2010 08:00 PM
Newbie here, trying to catch up with you guys.
Similar problem: experiencing intermittment "hangs" on WCG200 v 2
Firmware: 2.0.3.9.31-0214
ISP: Cox
Since my fimrware appears to be current, are there other areas that I should look at to resolve the problem?
Many thanks in advance.
02-04-2010 03:35 PM
My solution:
Tried a diffferent wireless card (Gigabyte miniPCI) for my computer and all works fine.
Tried a different router (Netgear WGR614) with the original 1370 wireless card and all works fine.
Conclusion: Some routers and some wireless cards just don't work well together!
Cox told me they don't do firmware upgrades!