W2K Server only pings - no network access

[atakanoguz]

Hi,

The server was hit by the Blaster worm. It has been manually removed.

Following this, it has not been possible for the other client pc's to access the server.

ipconfig /all worked fine.

i did a sfc /scannow to validate the files as well.

Later on the server was updated to SP4.

All the services were double checked with the IT guy who is in the HQ's far far away. He's no help.

Can you help?

Is there anyway to bring the computer's state back to before it was infected?

Any ideas?

Thanks.

Atakan

 

[n3buo]

We have found that the Majority of ISP's are now blocking access to port 135. Currently SBC, Charter in Texas, Cox Cable just to name a few. This is cuase major issues with access to Windows 2000 servers as well as Smaba shares on Linux machines. Might want to check to see if they are filtering you!!

Dave

 

[RichardHuang]

If it's not the issue that Dave mentioned, you can try to check your Server service in Admin Tools because this service is used to manage file/printer shares. Also, uninstall and reinstall TCP/IP protocol is very helpful to get the network back.

Richard

Hi, I am in Toronto.