Windows 2000 Server loses shares after re-boot

well why is it rebooting in the first place?

What shares? a DFS? mapped drives to shares on other computers? Is it part of an Windows Active Directory domain? Is this a file server with the shares?

Need more info

well why is it rebooting in the first place?

What shares? a DFS? mapped drives to shares on other computers? Is it part of an Windows Active Directory domain? Is this a file server with the shares?

Need more info

RESPONSE:
Yes, it is a domain file server. It resides in the Windows Active Directory domain. This is the file server with the shares. It is a file/print server. Service pack 4 is on it.

anything in the event logs
how is your antivirus, spyware protection

see if this is you:
http://support.microsoft.com/default.aspx?scid=kb;en-us;842715
Overview of problems that may occur when administrative shares are missing

Hi,

So the shares disappear with all the settings that you had set for them on the physical file server, or is it just that users cannot connect to a mapped drive or home drive?

#1 unless there is a problem, you add new software or a service packs or hotfixes require a reboot, your server shouldn't need rebooting.

Shares that reside on this server should not disappear e.g. they are physically gone and deleted from the server. If the shares are actually on the server but after a reboot, users complain they can not access shares e.g find them via an AD query or via a mapped drive then the problem typically is a connectivity problem. The server doesn't connect to the network.

see if this is you:
http://support.microsoft.com/default.aspx?scid=kb;en-us;842715
Overview of problems that may occur when administrative shares are missing

RESPONSE:

Thanks. I will try it.

Hi,

So the shares disappear with all the settings that you had set for them on the physical file server, or is it just that users cannot connect to a mapped drive or home drive?

RESPONSE:

That's correct. Users are correctly mapped.

#1 unless there is a problem, you add new software or a service packs or hotfixes require a reboot, your server shouldn't need rebooting.

Shares that reside on this server should not disappear e.g. they are physically gone and deleted from the server. If the shares are actually on the server but after a reboot, users complain they can not access shares e.g find them via an AD query or via a mapped drive then the problem typically is a connectivity problem. The server doesn't connect to the network.

RESPONSE:
The server is still connected to the network because the common network drive and the application network drive are still accessible during the loss of personal shares period.

Somebody could help? My server also this stopping the sharing, after to only restart it comes back to the normal one. But this occurring 4 times to the day.