Remote Procedure Call

The god damn thing shows up for no reason other then to piss me off.

I get this error. Can't figure out what is causing it. Come home from work to find that nothing on my computer will run even after rebooting. So, I reformat.

Get everything back up and running. Shortly there after, I start getting the RPC error again. I figure maybe it has something to do with IRC, that someone is fucking with me. So I turn it off. It continues, so I figure it has something to do with AIM, so I turn that off. It keeps going.

I don't even need to do anything other then login for the error to occur. I open a file, RPC error. I open IE, RPC error. I do an MS update, RPC error.


I run a current version of Norton, which is updated constantly, be it on its own or by my own button mashing of the "update" feature. I don't open suspicious emails or visit websites that are of the shady nature.

Lately, I just leave IRC and AIM running and I just do my own thing. Run FTP to upload/download current fansubs to a groups T1 dump, nothing else.

To get around the constant reboots, I opened up the ADMIN tools and set the options for the RPC to "restart the program" instead of "restart the computer". So this way I can now stay logged in for more then 2 mins before it reboots itself(currently at 9mins and counting as of this post)

While changing its setting may let me browse or whatever, I don't feel it accurately fixes the problem that I'm getting. I would like to fix it so it doesn't degrade into something further and create more headaches then I need, which I've got plenty.

At this time, it isn't completely up to date with newest drivers or DirectX.

Computer Info:
Win XP
Geforce 4 4600
1gb ram
120 x2 HD's

edit: I do have current MS updates and security patches as well as Service Pack 1.

See this thread Here (http://www.erollisimarr.com/forum/showthread.php?t=15006)

Just found this after hitting my guilds website.
At the MS site now, see if I can get the shit running properly.

Thanks.

Whoever makes this shit needs to have a nice spike driven into the side of their head.

The fix does indeed work, I was getting this fucking same error this morning and I havent had it since applying the patch.

A nice litttle worm.

http://securityresponse.symantec.com/avcenter/venc/data/w32.blaster.worm.html

Microsoft has released patches to prevent it

A nice litttle worm.

http://securityresponse.symantec.com/avcenter/venc/data/w32.blaster.worm.html

Microsoft has released patches to prevent it

Microsoft released a patch for this quite some time ago. Please patch your machines folks, it only takes a few minutes to do.

Why is it that the only people i know who are getting hit with this are EQ/ex eqers.....

Patched it last night, still online, so guessing it worked.



Microsoft released a patch for this quite some time ago. Please patch your machines folks, it only takes a few minutes to do.


Ya...good thing I knew about this, so I could come here and waste everyone's time with my problem. Thanks for adding nothing constructive.

I like replied to a couple threads AND made a seperate post to fix this, but no one seems to look =\.

apparently it wasn't a dangerous bug..just a thing to get MS's attention. I didn't get it but I've seen with the bug was included the line of text "I LOVE YOU SAN...billy gates stop making money and fix your software" or something along those lines. dunno what the whole I love you thing is though :p

Why is it that the only people i know who are getting hit with this are EQ/ex eqers.....

I visit heaps of gaming forums and trust me it aint just EQ players or EX EQ players getting hit.

maybe yoiu hjsut only talk to EQ'ers? dunno, too drunk to kno w about anythig right about now :)

For anyone the needs the fix for the 32.blaster.worm go to Corderpounder.com. This guy is a good friend and a computer genius. He has his own server for halflife fans with a firewall and all the high tech stuff and the virus got around all of it. His web page will explain everything on how to fix it. I did it myself and have no probs.

Colbie Rathofkin
Regia Antiquuas
56 Ranger of Tunare

Slayne, let me spell it out for you a bit more clearly:

If you patch your machine regularly, there is a very good chance that the next nasty worm that comes along won't impact you.

That seemed pretty constructive to me.

I update constantly, But this certain update/patch was not in the critical updates. Nor was there any link to it when running the windows update program. Makes it hard for us non-computer gurus to know about it. I didn't get hit by it but was able to patch up as soon as a guildie linked where the patch was available.

The patch for this has been available since July 16th... it was on Windows update on that same day they announced the vulnerability. I remember because I patched a ton of machines that day because of it being there, and I used Windows Update for all of those machines.

Perhaps you already had the patch on your system from July, and thus you would not see it on Windows update. I won't try to figure out why you didn't see it, but Microsoft did indeed post this to Windows Update that same day as they announced it.

Technical description:

Microsoft originally released this bulletin and patch on July 16, 2003 to correct a security vulnerability in a Windows Distributed Component Object Model (DCOM) Remote Procedure Call (RPC) interface. The patch was and still is effective in eliminating the security vulnerability. However, the “mitigating factors” and “workarounds” discussions in the original security bulletin did not clearly identify all of the ports by which the vulnerability could potentially be exploited. We have updated this bulletin to more clearly enumerate the ports over which RPC services can be invoked, and to ensure that customers who have chosen to implement a workaround before installing the patch have the information that they need to protect their systems. Customers who have already installed the patch are protected from attempts to exploit this vulnerability, and need take no further action.

http://www.microsoft.com/technet/treeview/?url=/technet/security/bulletin/MS03-026.asp