-----Original Message-----
You've still got the Blaster Worm/virus in your system.
Now to get rid of it:
W32.Blaster.Worm Removal Tool - ZDNet Downloads
http://downloads-zdnet.com.com/3000-2092-10219754.html?
tag=lst-0-4
.
Nope. Been there, done that.
*EVERY* scanning program I have tried, including the one
you reccomend, come back with a message saying that I *do
not* have any W32.Blaster infection. So unless this new
RPC 2 worm is not detected as a W32.Blaster infection,
and if I'm not infected with it already, the problem is
still related to the MS RPC update. Ever since installing
the update I have had serious issues with XP. No TCP
sockets left for internet connections, unexpected
restarts (which always result in a warning about not
being shuting down correctly and scandisk being run),
hard drive partitions 'dissapearing' while in use
(litterally being gone and not accessable), and so on.
After restarting the problem is gone for a few hours.
The situation *always* occures after the computer has
been on 5 or more hours. The MS update pages, say I have
all updates available already installed, so I'm not
missing one. But the problem did not occure until *after*
installing the RPC update from MS. There is no warning
message about restarting, its a hard restart (as though
someone hit a reset button on the computer). The restart
isn't related to any specific program other then Windows.
I've tried to limit programs, to single out
possible 'problem' programs. Nothing that I have done,
results in a 'fix'. Starting the computer and leaving it
idle with only the Windows programs running (the ones MS
feals are important enough to have running all the time,
even when there not really needed) and the computer will
still restart. Again, everything points to the MS RPC
update as being the problem.
It's sad that 'hackers' have to create something to
exploit the programming weakness in an OS, but even
worse, when the update to fix the problem, creates more
problems then it fixed and the hackers created.
Regretfully I'm stuck with an unstaible OS due to an
update from the manufacture. The other option is to
reinstall and not install the update, but then have to
worry about the W32.Blaster attacks. The question is,
which is worse? With the W32.Blaster I atleast get a
warning message and time to save my work. What is the
purpose of haveing the RPC process running in the first
place? I don't use it, but can't disable the process.
Disableing the process, would solve the issue from the
get go. Forcing a useless process to be run because 'It's
a required Windows process', is a sign of weakness. If
its so important to the system, break it down into the
small elements and run it like that! Hell, there are 4
svchost processes running, each one with a different
function, and killing them results in a system restart,
but most have be disabled in the services.
I'm really starting to beleive that Windows XP is a hack
program, put together to get out to the public "at all
costs". It includes MS 'back doors' so that MS can 'spy'
on the users. The software routinely sends MS information
about usage, and in most situations, doesn't tell the
user that it's doing it (spy ware), and with every
update, the software offeres more functionality
to 'hackers' and more unstability to the owner!
