Discussion Locked

Recovering after smb storm on port 135

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have some problems with some computers after an employee had brought his own computer to his workplace. the storm hit the PDC (Windows NT 4 Server) and about 30 client computers, winnt, w2k and wxp, after that the computer can?t start when the its wired to network, the error message is "computername already exists on the network" even if we change the name on the computer, we still get the error. We have even tried to reinstall the network on a Computer, but nothin seems to help.

All hint?s would be helpfull

PS I think it could have something to do with SID

3 replies

by pctech

I would suspect that this computer is broadcasting a set computer name no matter what it is set to. Something in it's registry, perhaps?

I would try this, backup all of the critical data on the affected computer. Erase and reload this computer and install all of the updates and patches. Insall any applications and bring the data back in. I would delete the computer and user account on the PDC and replicate this information to any BDCs, for this user and computer, and recreate them with a different user and computer name and replicate this to any BDCs. Make sure that all patches and updates are in for all computers on the network before bringing in the affected computer again.

I hope this helps.

by joseph moore

Ok, let's just start at the beginning here. You had a "smb storm on port 135" when someone brought in a home computer into the office?
Ok, well SMB doesn't run on TCP port 135, but that is besides the point!

Was this home computer infected with Blaster or one of its variants (like the Nachi variant)??? It sure sounds like it was, and now some or all of your LAN computers (maybe even your PDC) are now all infected.

You should do the following:
1) run updated antivirus software scans on all machines, looking for Blaster worm. Run the cleaner tools if you don't have antivirus software:
http://www.sarc.com/avcenter/venc/data/w32.blaster.worm.removal.tool.html
(please remove any spaces)
AND also run:
http://www.sarc.com/avcenter/venc/data/w32.welchia.worm.removal.tool.html
(remove any spaces)

2) Patch all systems with the MS03-039 patch:
http://www.microsoft.com/security/security_bulletins/ms03-039.asp
(yet again, remove spaces)
You might need to apply the most current service pack to be able to apply the patch. This vulnerability in the RPC/DCOM service interaction (running on TCP port 135) can just mangle a machine instead of just infecting it. So, if you have a machine that won't let you apply the patch, then just reboot the box, put on the lastest service pack, reboot again, then you should be able to put the patch on.

by joseph moore

3) Get everything stable and patched and disinfected, then you can look and see if you still have mangled computer domain membership. If things are still weird, just remove the troublesome machines from the domain (join them to WORKGROUP), then rename them to brand new unique names, THEN add them back into the Domain.

Good luck

This discussion is closed to new replies.