I used to have a server with win2000 OS. Yesteday I updated it to win2003 server R2 service pack 2. My problem now is that in a particular moment nobody can access the server. All of the shared resource of the server are unavailable. The only solution is to restart the server although the server is running fine.

I don't think that is a connection problem of the LAN, because with the win2000 this problem didn't happend. The PC is connected to the same switch and the PC have the same exact hardware.

  • 2
    "The only solution is to restart the server although the server is running fine." - So restarting the server does or doesn't fix the issue? – Dscoduc Sep 11 '09 at 16:58
  • Yes, it does fix the issue, but I can't restart the server everytime this happens. – Tavo Sep 11 '09 at 17:45
  • Do you actually need to restart the whole server, or would just restarting the "Server" service do just as well? Are you getting any errors in your event logs mentioning permission errors or services stopping? – GAThrawn Sep 14 '09 at 10:46

Make sure your client computers have their DNS entries set to the IP address of the server.


Are they in a domain/AD, a workgroup or simply standalone machines? It really depends on the setup, how about you give us the exact error message and an idea of the setup (IP addresses, subnet masks) and are you sure the resources are really shared?

  • The server is in a workgroup. Like twenty machines are connect to it. I don't get an error message, but when I tried to browse the files that the server had shared my explorer freeze. – Tavo Sep 11 '09 at 17:49

R2 made some significant changes to network settings by default, I would check you have recent drivers that are compatible. This article while for SBS describes the issue well

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.