Discussion Locked
0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Within days of upgrading my domain to Win2K last March I noticed that all Win2K servers, desktop and laptop computers were taking longer to shut down or reboot. They would get to the blue screen and sit there for 60 seconds, sometimes even longer, before finally giving up and shutting down. Sometimes I get an Event ID 1000 "DETAIL - Access is denied. Build number ((2195))" but I have no roaming policies in the entire company. Just in case, I made a domain policy to change the unload roaming profile retry count from the default of 60 down to 5, but that did not change the slow restart and shutdown times. I have watched new computers with normal shutdown times go immediately slow as soon as I join them to my domain.
10 replies
by w2ktechman
Sounds like a networking problem somewhere. Usually a timeout of 60 seconds would be that it is detecting a slow network, or no network. But since the network does appear, I would check placement of servers/router. Also try making sure that a browse master is available, and the gateway is easily accessible by all systems. And make sure that the DHCP server is easily accessible as well.
by singerguy
It is a small network with only about 60 nodes on it. Everything is hooked up to the same switch. My main servers and two domain controllers (which are also my DHCP servers) are gigabit. Primary domain controller is also browse master. This problem is just as evident on a laptop not connected to the network.
by jimjennings
I would also make sure that none of the clients are running the computer browser service, that makes them try to be the master browser.
by singerguy
I have turned that off on three test computers and it didn't change things.
by rsp
Antivirus software often causes this problem.
by singerguy
I tried a brand new computer by installing everything except the antivirus software and got the same results.
by voldar
Check your DNS settings configuration, it's faulty I think.
And also, look in your EVENT VIEWER - this is why you have it :) - and see what errors you get when computers/users log into your network. I say that because most of the people don't even think about looking/checking the Event Viewer for solving problems.
by singerguy
I went to the event viewer multiple times. Nothing was being logged. It acted like business as usual.
by singerguy
I finally figured it out. Somehow when we were setting up the Win2K domain a security policy was enabled in Local Policies \ Security Options to "Clear virtual memory pagefile when system shuts down" which was delaying the shutdown while that action was performed. I updated the policy to disabled and things are again as they should be. Thanks for all the suggestions.
by singerguy
This question was closed by the author
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending
0 helpful
11 replies
0 helpful
1 reply
0 helpful
10 replies
Question Locked
Do You Save Useful Windows Tutorial Videos for Later
0 helpful
7 replies
Question Unanswered
Is WSL still relevant in 2026?
0 helpful
0 replies