Windows xp hang applying computer settings

->>>> Click Here to Download <<<<<<<-

In reply to Malkeleah's post on January 8, Okay, here's what I did and learned: 1. I disconnected my 2nd hard drive, partly to minimize current draw from the power supply, but also to keep the bootup clean and simple between a C: hard and D: CD-R drives.

This time, I waited for about 15 mins and to my surprise the setup screen came up! There is a long time period between when the "Setup is starting Windows I was able to partition and format my hard drive. Lessons learned: - Keep the number of peripherals down to a minimum so that it keeps the unknown hardware failures from confusing the troubleshooting issues.

I've plugged the PC into a different port, but same result. I've plugged a different PC into this PC's port and it boots fine. I've checked the DNS and everything seems to check out fine. In my event viewer I get the following: Automatic certificate enrollment for local system failed to contact the active directory 0xb.

The specified domain either does not exist or could not be contacted. Enrollment will not be performed. Group Policy processing aborted. The only way to make it boot quickly is to unplug the netork cable. After booting though, when I plug the network cable back in, it still takes about 10 minutes to get a DHCP address. New software or hardware? Office Office Exchange Server. Not an IT pro? Resources for IT Professionals.

Sign in. United States English. Ask a question. Quick access. Search related threads. After it boots up it is fine. We first thought it was Symantec endpoint causing an issue so we upgraded to the latest version which helped a little.

Looks like a SMB problem. Any suggestions to help alleviate this issue? In addition to Prashants's suggestion, ensure the problem workstations are updated with latest update and patches. On the Domain Controller check for errors in the event log, also check that the Domain Controller is looking to the right DNS server as well. Best Regards, Abhijit Waikar. This can be mostly wrong DNS configuration settings on the client machine.

You can also make use of enabling "always wait for the network at computer startup and logon" option in group policy. You can also utilize userenv logging. Also, take a look at below link. Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.