We had the Conficker.aa worm floating around the network for over a month before it was finally erradicated. In that space of time we have had various "strange" things happen that I've never encountered. I have two main questions, one of which I will post here, and I will start a q/a session on the other seprately.
On a previously infected computer (our web server), we have several shares. Permissions wise, nothing had changed. Previous to the Conficker worm, we never had issues with it. Now, our shares intermittantly disappear from a person who tries to access them even though that person has permissions (even admin). Looking at the share, all permissions are fine, user settings are fine, the folder is still shared (Hand under the folder), and the server service is still running. Yet one cannot gain access to the \\computername\share using that method. Logon scripts will not map a drive either. Finally, I resorted to creating a new server, new name, IP address, and creating new shares. It too, experiences the same problem. At some point shortly after a boot or reboot, the shares simply do not respond, yet are there in every way. Rebooting will bring the shares back, but only for a very short time. No errors pertaining to these shares appear in the event logs either.
Information; Running w2k3 (standard) servers with all fixes, patches and service packs applied to date AD is native mode, 4 domain controllers IIS is configured on the box with ASP.net
Comments and suggestions are welcomed. I've hit a brick wall on this and must now reach out to those who might offer suggestions I had not considered. Any help is appreciated.
This conversation is currently closed to new comments.
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
File Shares disappear shortly after booting or rebooting server
On a previously infected computer (our web server), we have several shares. Permissions wise, nothing had changed. Previous to the Conficker worm, we never had issues with it. Now, our shares intermittantly disappear from a person who tries to access them even though that person has permissions (even admin). Looking at the share, all permissions are fine, user settings are fine, the folder is still shared (Hand under the folder), and the server service is still running. Yet one cannot gain access to the \\computername\share using that method. Logon scripts will not map a drive either. Finally, I resorted to creating a new server, new name, IP address, and creating new shares. It too, experiences the same problem. At some point shortly after a boot or reboot, the shares simply do not respond, yet are there in every way. Rebooting will bring the shares back, but only for a very short time. No errors pertaining to these shares appear in the event logs either.
Information;
Running w2k3 (standard) servers with all fixes, patches and service packs applied to date
AD is native mode, 4 domain controllers
IIS is configured on the box with ASP.net
Comments and suggestions are welcomed. I've hit a brick wall on this and must now reach out to those who might offer suggestions I had not considered. Any help is appreciated.