The windows 2003 R2 server is a domain, file, dns server. Workstation (XP) don't have problems logging to domain. But when they try to access the map drives, it does not exist and if I open the machine from the windows networks: don't have permission. This problem occur after the server was hit by a malwares. After cleaning, this is the problems we encountered. And also, when I try to open the File Server Manager it gives me an error: can't create a snapin. I already tried uninstall and reinstall the .net framework but no success. How to fix this w/o reinstalling the server?

Hello, A corrupted server should never be trust anymore... I really recommand to you to reinstall from scratch. BR,http://blog.simaju.fr - Partage de connaissances et retour d'expriences.

How to fix this w/o reinstalling the server? Best is to reload. Otherwise, reset security privileges on the shared drives. Right click -> Properties -> Security. Check whether they are shared. Right click -> Properties -> Share

Hello, as Simon.Grosjean already stated once a server was corrupted and even if cleaned(maybe complete, maybe not you'll NEVER know) this machine should be reinstalled from scratch. Required data i would copy to an external drive and scan again with a NOT network connected machine that has 2 different Anti Virus installed and if both state no problems copy the data to another or the new installed server. If that server is the only DC in a domain you have a bigger problem to restore, as it should be restored to a state BEFORE the machine was compromised. You didn't mention DC in the beginning, just domain server, so this is not clear. Do you have any errors in the event viewer of the machine you can't run correct, then please post the complete event viewer errors? Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

@Simon I know, but I need this to be up for awhile. They need to finish their work first before I reinstall or restore the server. @D Negidius thanks for the reply i'll check on that. @Meinolf Weber Sorry for that, The server is a DC and it's the only one on a domain. I do have the backup image of the server from the time we deploy it but it was long time ago. And what event viewer errors do you want? there's a lot of them. I do see some errors.

instead opening the machine from the windows networks please go to start --> run and type the ip address of the server \\x.x.x.x and see what happens and usually the firewalls and antivirus they block lot of things on the servers, you might have to disable the Antivirus and try it againhttp://www.virmansec.com/blogs/skhairuddin

Hi, You may modify the Share and NTFS permissions to access the shared folders. For the snap-in issue, please provide us the detailed error message for our further research. Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

@Syed Thanks for that. As of this moment the problem with sharing was already been solved. They happen to have a defective switch. So I let them changed it. @Arthur For the snap-in issue, it only happens for File Server Management. But other than that it works fine. Here's the error: "Windows Server 2003 R2 File Server Management MMC could not create the snap-in Name: File Server Management CLSID: FX:{f7da6f14-f244-401a-9259-f015a82057d3}" and by the way, is there a way to stop the raid 1 from syncing? or temporary stop the raid 1. I'm asking this coz I notice that the HD light is always on and it makes the server to function so slow.

Hi, Please try the following steps to troubleshoot this issue: 1. Launch MMC. 2. Click File and select Options. 3. Switch to Disk Cleanup tab and click Delete Files. 4. Click OK to check the result. Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for the reply Arthur, right now the server is running and they are using it right now. The problem was their network, the cable and the switch. When it was replaced, everything works fine. But still have problems with the snap-in, but I'm not planning to fix it since we decided to follow Simon's advice to reinstall it. Now we still have problems: 1. We lost the installation CD. Is there a way we can download a copy for it? It was an OEM version. 2. We created a system backup after all the settings and configuration using the built-in ntbackup in *.bkf format. But we didn't create an ASR image on it. Is there a way to bare metal system restoration using the bkf backup file w/o ASR? thanks in advance.