Link to home
Create AccountLog in
Avatar of 3v0luti0n

asked on

Computers on network sometimes take a long time to start "Applying computer settings".

Upon boot up, sometimes, but not always, the computers on the network will take several minutes to start up. The "Applying computer settings" displays the majority of the time it takes to boot.
W2K server
W2K Pro
XP Pro

I found the following, but it seems specific to Server 2003:
There's currently a bug in Windows 2003 server which causes the computer to essentially freeze at the "Applying Computer Settings" screen when logging on. We had Microsoft on our system, and they found one piece of internal documentation on this subject. If someone is looking in the Services menu, and clicks on "IPSEC Services" and click away without changing anything, I believe it causes your TCP/IP stack to crash on a reboot. However, if you were to change something in the "IPSEC Services" and click OK, you would be fine. I'm not exactly sure what the fix is, as Microsoft spent 7 hours working on it.

It took close to two hours for our computer to login, and we had to do several things in Safe Mode to get this back up. We tried uninstalling Norton Antivirus, rebuilding the TCP/IP stack, and many other little things, but nothing worked. I can't offer a solution, as I don't have one, but save yourself the time and get Microsoft on the phone and talk to them about the IPSEC Services making your computer freeze at "Applying Computer Settings". Microsoft said they know the problem exists, but aren't sure how fo fix it yet. Good luck!      

Does any one know the solution to this? If not, how can I troubleshoot this?
Avatar of luv2smile

A lot of times this can happen because your DNS is not setup properly and the computer is having a hard time resolving to the domain.

Avatar of oBdA
That's probably just incorrect DNS settings.
Make sure that
* Your DC (assuming it's running DNS) points to itself *only* for DNS resolution
* Dynamic Updates are allowed for your forward and reverse lookup zones (DNS MMC / Properties of the zone)
* Your clients use your internal DNS *only*
* For external name resolution, configure forwarders on your DNS server to point to your ISP's DNS
After this is ensured:
* Check if your DC has registered itself in DNS
* Check if the SRV records (see article below) exist; if not, stop and restart the netlogon service on your DC

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003

Troubleshooting Active Directory DNS Errors in Windows 2000

HOW TO: Troubleshoot DNS Name Resolution on the Internet in Windows 2000

HOW TO: Configure DNS for Internet Access in Windows 2000

Troubleshooting Common Active Directory Setup Issues in Windows 2000

How to Verify the Creation of SRV Records for a Domain Controller

How Domain Controllers Are Located in Windows

How Domain Controllers Are Located in Windows XP

10 DNS Errors That Will Kill Your Network
Avatar of 3v0luti0n


I have Two DCs and both of them are DNS servers. In my network properties the prefferred DNS server was pointing to the other and the secondary was pointing to  itself. I change this to reflect the above suggestion. Also, in one of my servers DNS properties, I had an additional entry for a "Listen On" IP address. It was in the range. I think this could have been an issue. I will test to see how we did.
Avatar of oBdA

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account