O ya, you guys were always lots of help.
Thanks a.
Printable View
O ya, you guys were always lots of help.
Thanks a.
If you can't get into Windows Update to get the patch CNET has it available here-
http://download.com.com/3120-20-0.ht...search=+Go%21+
Wish we would have gotten into either VDr or MSupdate yesterday mornig when this happened...:rolleyes: - our whole 2000 system got hammered and some older NT machines broke down completely when attempting to run MSupate...
Running 98 DOES have advantages sometimes ;) - no prob at home :D
Hi everyone,
Just thought I would add a note that Eeye Digital Security released a free RPC DCOM vulnerability scanner that can be found here:
http://www.eeye.com/html/Research/To...=RetinaRPCDCOM
You have to fill out a form, but it is worth it!
It just makes it a lot easy to tell which systems still need the patch, and when you are done.
TIP: Today I attempted to scan a home users PC, which had no LAN IP, and therefore no IP when not connected to the Internet. If this is the case, scan 127.0.0.1. the name will resolve to LOCALHOST. Another good idea is to remove the default checkbox for "Show only vulnerable servers". That way you know it is working when everything is patched.
Slic, I tried a scan-got no results. Do I have to manually enter my IP address?
Windows 2000 Pro.
I've aplied the patch.
Just so I'm staright on this Blaster thing, Win98 machines are not affected, right? Also since this is a worm/trojan rather than an email virus, do you need an a/v program or a firewall or both to stop it?
I haven't read all posts before - but if somebody gets shutdown in 1min window just to prevent do it:
start >> run >> shutdown -a
Just wanted to give others a heads-up, as many will probably be making/receiving service calls. Download & carry a copy of Win 2000 SP4 (Network install, think about 129 MB) along with the patch.
Just got done working on a Win 2000 machine, and as with the majority of folks out there, the owner had not downloaded any service packs. Need at least SP2 in order to install the patch. I tried the Windows Update way of installing SP4 twice - after using the norton removal tool - and while the SP was downloading I got the worm again.
Finally got smart and downloaded SP4; then ran removal tool, SP4 and patch installs before getting online again. I was an idiot, but no idea how fast this thing is spreading at the time.
That's correct. It's a good idea to have a firewall and an antivirus installed, but not necessary to stop this worm for Windows 98 users. More technical explanation is available here: http://securityresponse.symantec.com...ster.worm.html - and if you want the in-depth technical analysis, it's in this .pdf document:Quote:
Originally posted by f117nighthawk
Just so I'm staright on this Blaster thing, Win98 machines are not affected, right? Also since this is a worm/trojan rather than an email virus, do you need an a/v program or a firewall or both to stop it?
https://tms.symantec.com/members/Ana...t-DCOMworm.pdf (that last link from http://www.securityfocus.com/archive/1/332625 )
STEBEL, thanks for that info.
While I guess this is a good sign that everyone should keep up to date on the latest high-importance patches and security devices (really, how many reminders do we need? ;)) I think the worm author said it best, in the message embedded within msblast.exe:
I must say I'm impressed with Symantec's handling of this situation. They were on the ball from the get-go. I've been given reason to recommend other products (such as TrendMicro's) above theirs for a couple of years now, but this incident has restored my faith in how much they care about their user's systems. I'm glad this thread could be of assistance to people out there affected by this. :)Code:billy gates why do you make this possible ? Stop making money and fix your software!!
Well, the DoS attack is scheduled for tomorrow (8/16) - I hope it's somewhat contained by now.
I agree, Symantec has been impressive since the beginning (fast and accurate).
My understanding of Microsoft's reasoning in not originally mentioning Win 2000 (Gold, SP1 and SP2) is that they no longer support these versions (I may be wrong about SP2).
Blame for this infection obviously lies with the people who are creating and attempting to spread this worm and its varients, but I agree that Microsoft's culpability is strong for allowing the vulnerability in the first place. The fact that so many people where caught off guard, even though we've had plenty of warning, is probably understandable considering the different attitudes people have toward Microsoft's Updates. Also, there are a lot of people who pay little attention to their computers and computer news in general.
Murph: thanks for the heads up for Win2000 machines.
XP 64bit has been out for some time, for the IA64 Intel Chip, the AMD version is on it's way, so yes, some people do have the 64BIT version of windows, but only the ones with huge walletsQuote:
Originally posted by ChiefE7
To all interested: If your wondering whether you have XP 32 or 64 bit, not to sweat.....M$ has not released XP 64 bit yet, I believe 64 bit has a release date of 18 Aug 03.....I think they decided to have a little advanced publicity on XP64...hehehe;) :rolleyes: :confused:
What would be the hardware requirements for a good 64 bit Windows machine? I could buy the parts and build it piecemeal. Would there be any way I could put 64 bit XP on my current machine?
http://www.microsoft.com/WindowsXP/6...n/overview.aspQuote:
Originally posted by f117nighthawk
What would be the hardware requirements for a good 64 bit Windows machine? I could buy the parts and build it piecemeal. Would there be any way I could put 64 bit XP on my current machine?
You need a 64-bit processor, such as Intel's Itanium 2 (released in 2001 and way high end) or the Athlon 64 FX - which is coming out next month and more aimed at lower end users who want a smooth transition. The G5 will also be 64-bit. 64 bit computing will be fun once it's accessible to everyone with the ease 2GHz processors are currently available.
BTW
I don't do any help desk, so I'm not sure how long this thread is needed. If the need for this info has pretty much passed, please let me know so it can be de-stickified.. :)
Might as well as destickify this thread to make room for the next one.
http://www.microsoft.com/security/se...s/ms03-033.asp