Woohoo! All hacked SQL Servers are doing a massive DoS!!!

[Saltin]

-edit- thank goodness were safe. firewall, IDS with these signatures, logging and no MS products accessible from the internet allow me to sleep at night.

I have an entire Windows 2000 network under my supervision that is safe as well..... go figure.
Like Mucman said, it really comes down to administrative competance.

I reckon the lion's share of infected servers are in the .edu namespace.

 

[bsr]

I acually helped my isp fix this problem last night, they had to update nt, and did some other stuff to. They replyed to me with thanks and telling me I was absolutly right

 

[mboy]

I patch all of my machines 2 days after the patches come out (mostly XP pro rigs and NT 4 servers, 2 exposed to net). 2 days give me enough time to evaultae the patches on my rig (or test rigs) to make sure they wont break everything, then I push'em all out.

 

[Kk4JC]

It's sad to see how easy the Internet can be stopped in it's tracks.

Kk

 

[Thor86]

Originally posted by: mboy
I patch all of my machines 2 days after the patches come out (mostly XP pro rigs and NT 4 servers, 2 exposed to net). 2 days give me enough time to evaultae the patches on my rig (or test rigs) to make sure they wont break everything, then I push'em all out.

Ditto. Patching non-production server first to test will save you from "all-nighters".

 

[skyking]

patch all of my machines 2 days after the patches come out (mostly XP pro rigs and NT 4 servers, 2 exposed to net). 2 days give me enough time to evaultae the patches on my rig (or test rigs) to make sure they wont break everything, then I push'em all out.

Bravo!
I have one small server and site, but I also have a dev box at home running a copy. I can test out a patch, and implement it right away, without unexpected results.