(Back to Cisco675fix.html)
Your Feedback
Here are some nice comments I've received from DSL customers like me and from ISPs who use Cisco 67x DSL Routers:
"Thank you for the most user friendly document on 'flashing' a Cisco 675/678 CBOS that I have ever
read. This will be made available to our customers."--an ISP
"Hey, thanks for posting the great "howto" on fixing the cisco 675. Found the link on 8wire and gave it a shot (my older 675 was dropping connection about every hour or two for the past few days, and Qwest's advice to "disable web access" was pretty worthless.).
The fix worked great for me!
Thanks again"---a DSL user
"Hello Juleigh -
"Thanks so much for your help and please keep me posted on any "final" fix or
patch that you may learn of. I will do the same."--a DSL user
"Thank you so much for your extremely helpful writeup. I only wish Qwest
and/or Cisco could come up with support this good.
Code Red has been making my/our life miserable lately and Qwest hasn't been
much help.
So - please let me know when and where I can have a pizza delivered to you
from the guys at ---------!
Thanks again and take care,"----an ISP
"Damn Fine work!!!
Thanks."---an ISP
"Juleigh,
Thanks for the info. I think most of the DSL problems recently have been
Qwest's issue, not user issues like they have been telling our customers. I
can't see throwing away an expensive piece of equipment because Qwest won't
take the time to walk customers through reconfiguring it. If you find out
any more info keep on me posted."---an ISP
"Juleigh, Juleigh, Juleigh...
A big kiss on the forehead for you!
I had to do this several times, but finally got the cbos in. Had to use the
cbos from your site as the one from cisco didn't work, oddly enough.
But still I'm not online through the dsl, most likely because of some
difficulty with passwords and usernames.*
Thanks again so much for making me persevere. I really don't know what made
the difference in all those six or seven tries, but persistence worked.
By the way, it was a qwest tech who gave me the lead to you! "---a DSL user
*(followup email after he got his account information from his ISP)
Juleigh,
This is fabulous. I got the info from qwest and am up and running.
What a process. Both Qwest and Cisco told me the router was toast.
I am so appreciative. Can I contribute to your favorite charity or
something? Or to your company?
Thanks"---a DSL user
"Thanks for the info..."----an ISP
"Juleigh,
Thank you so much for the info. I will be happy to pass this on to
our customers who have these problems.
If you have any further questions or comments, please feel free to
email us at ---------- or call us at ------------.
Thanks"---an ISP
"Hello
Thank you for the information."--an ISP
"THANK YOU!
You just saved us a lot of time and money! It was so easy to follow!"---a DSL user
"You rock!!!
I got a 675 several months ago from a guy that said it had been infected
with the CodeRed worm. While in the process of 'updating' it via telnet,
it was interrupted and appeared dead to all indications. Get this, the
guy is a 'network' guru and said it was fried and was probably going in
the trash. He tossed it to me and said I could make a paperweight out of
it.
"Well, long story short. I plugged it in and no wan lights at all. Searched for fixes including Cisco/Qwest/anywhere and found nothing. I used Google and type in 675 corrupted and whoila! Your site showed up. I followed every step EXACTLY as you had it down and on the very first time, SUCCESS!!! Waahooo!!! (Sorry for shouting, but I'm so dang fired up about it, I gotta let one loose!)
"Thanks for having the info. Thanks for making it easy for anyone to use and follow. Just thanks."---a DSL user
"Thank you for providing the info for erasing the 675 and reprogramming. It worked just fine!"
---a DSL user
"Thanks! Your Cisco 675 pages on the web are great and the fixes work."--a DSL user
"I have to admit ... your website is the most helpful one out on the web for
getting your Cisco 678 back to a functional status. Kudos to you!
"---a DSL user
In Defense of Qwest
I have heard and received all kinds of tales about Qwest in the wake of the Code Red Worm, most of which involve a few expletives. While I sympathize with, and to an extent, share this attitude with regard to the speed/accuracy of the solution, I want to say these good things about Qwest.
This Code Red Worm, particularly the second mutation, took Qwest as much by surprise as it did us users. Qwest has had an enormous increase in their tech support call volume, and they have in the past few days assigned many more people to the phone lines. This has decreased the "hold" time from 4 hours to less than an hour. Qwest is posting updated help to their website. Although this help doesn't cover what to do when your router's CBOS is corrupt, it is good, albeit temporary, stuff for most of the Cisco users whose routers are still able to accept reconfiguration. Qwest is working with Cisco to try and find a more permanent solution, and Qwest is now contacting their Cisco customers directly by letter and email, rather than waiting for them to call Qwest. Also, a few of the tech support people on the Qwest lines are friendly, excellent advisors. You might have to call more than once to get one of 'em, but you'll be glad you did.Let's remember that the bad guys out there are the ones who wrote this Worm and its variations.