Posted 02 September 2008 - 10:42 AM
I have a computer on a Windows 2003 AD domain that recently had a Vundo Variant infection. I've managed to clear it out, but it seems there are some remnants lurking about. The machine has been acting slowly since the purge, and I decided to perform a few tests to make sure I wasn't missing anything. One of the tests I ran was with netstat.
Running "netstat -an" returned expected results, but I decided to check executables, and ran "netstat -ban".
Instead of the expected result, I got back a "Windows - no disk" error. I played with several other options after this, but it was the "b" switch that caused the error every time, without fail.
Any thoughts? I'm trying to avoid flattening this machine if I can, it's got a load of software specific to only it, but I will if I have to.