Blaster worm - Did you get it? Personal PC only please

[Ovi]

Originally posted by az
Yes, and when I got it, I totally panicked (because I couldn't find any information on WHY my sys kept restarting), add to this my computer rebooting every 2 minutes, the heat, and that I was tired, and I was totally useless. It was only thanks to Ovi that I found out what it really was, and finally fixed it.

I feel so ashamed for not having been able to think straight and fix it myself

AZ

Hi Az!
Hey, no need to feel ashamed! That "rebooting in xx seconds" box was scary, plus it hardly gave one time to poke around before it rebooted the system!! In fact I had to stay offline (to prevent getting rebooted again) and then tried to figure out what was going on!
And as for why I got the worm: Well, till last week I had XP's built in firewall (ICF) enabled. But then due to that "periodic freezing" bug in Windows Messenger (caused due to it clashing with ICF, it kept repeatedly opening ports or something, but happens only when DirectX9 is installed!), I disabled ICF! And then this worm struck! Needless to say I have re-enabled ICF, Windows Messenger may freeze all it wants!!
Cheers
Ovi

[agallag]

My router saved me at home, even though I'm pretty sure I was all patched up already.

Work system was fine too, since I was home sick monday and tuesday and had my laptop with me.

Servers in the lab at work are another story. I had set up a quick test environment last week, and all three servers had it. It went through our corporate network pretty quick. I guess someone connected through VPN from an infected home machine to get it in. Pretty easy to clean up though.

[Brian R.]

My Zyxel Zywall10 and Norton AV worked I guess. No problems on any of my home computers.

[DentyCracker]

I got it because
1) I couldn't be arsed to windowsupdate this machine at the normal time (Small matter of getting stuff signed in preparation for leaving old job, moving to London, AOL dialup etc)
2. AOL (couldn't get into connection properties to enable firewall)

Now sorted. Hehe it was fun repeatedly running shutdown -a and restarting the rpc service. Especially as it happened just as I was installing ntl broadband. Kaspersky at first missed it, so I updated it. Then it could detect but not clean it (later version). Then after the next update it could sort it. I also found a standalone file for the patch (windowsupdate was being hammered). The firewall is now of course turned on on the cablemodem connection

[GuchiGuh]

ZoneAlarm Pro did well.