Bugzilla – Bug 8412
Bug to track connection issues with RCA dcw725
Last modified: 2009-04-08 13:46:21 UTC
Support has a report of trouble with an RCA dcw725 router distributed by Time Warner. Text from ticket: (080520-001388) "PROBLEM - Duet - unable to connect to wireless network NOTES - Thomson dcw725 router ( http://www.thomson.net/GlobalEnglish/Products/cable-modems-gateways/us/dcw725/Pages/default.aspx ) - connecting wirelessly - WEP encryption - customer not sure if it's 128-bit or 64-bit (she has both a 10 character and a 26 character key) - firmware never updated" ... Support worked with this customer extensively but could not get his Duet connected successfully to this router. We replaced the Controller. Vinh inspected the Controller that came back and it did have connection problems. But the replacement sent out would still not connect to the router. Customer bought a new router and the Duet connected successfully.
Ross to research, acquire and test router
This is not an easy to find router. Dan do you think your customer would be willing to trade us his DCW725 for a brand new router? I realize he already has a new one perhaps we could come up with something else to offer him maybe a coupon or something.
I'll try contacting the customer and let you know.
targetting as future so it doesn't show up on our search for untargetted bugs
(In reply to comment #3) > I'll try contacting the customer and let you know. > Any word on this, Dan?
The customer stopped replying. We pinged her a couple times but *silence*.
Thanks Dan.
Still none of these on the bay. Dan's customer stopped responding, 0 incidents with this Residential Gateway in the forums. I agree this bug should remain open but I don't agree with the target or severity. Try searching online for firmware for this RG, or a manual, or somewhere to buy it.
We've been unable to communicate with the only customer reporting this issue. We cannot get a hold of the hardware to verify that this is a bug. It's time to close this bug. Please feel free to re-open if anyone out there sees this again and can work with QA to resolve the issue.