Logging into a Windows 2003 Server, w/XP Professional

Why when loggining into a DC(Windows 2003 server), it takes so long to log on and finish booting XP Professional? What is the machine doing, they were not like this in a normal boot, without login prompts. Is there something we can do to speed it up?  The screens that show are.......

Loading your Personal settings
Applying your Personal Settings
HaroldNetwork EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

this is most likely caused to misconfigured DNS settings in TCP/IP.

Make sure that the client machine points to your internal Windows domain controller/DNS server.  Do not point client machines any other DNS servers...

When it hangs like this, it is probably looking for you domain using DNS... if you have the TCP/IP DNS settings pointing to some other DNS server (like a router or the ISP DNS server), you will experience this slow bootup process and your clients will have trouble "talking" to the domain.
You might also want to look into the process in which all your services are being started on the client machines. If for instance you have a service trying to start before one of dependants had a chance to start then you will experience exactly what you described.

In my case, awhile back I was having problems with the RPC service starting properly which in turn caused netlogon on a few clients to not run causing 10-15 minutes worth of loading.
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

HaroldNetwork EngineerAuthor Commented:
DNS is installed on DC and has it's IP as the listening IP.  If the client computers are getting an IP from a router, DHCP, we have to hard code the IP of server in DNS settings?
If the client computers are getting an IP from a router, DHCP, we have to hard code the IP of server in DNS settings?

You can probably go into your router and change the DHCP settings... so that it hands out the IP of your internal DNS server IP address.    If you can't do this, then yes, walk to each machine and hard code it.  (Or install the DHCP service on your Windows 2003 server .....and shut off your DHCP service on the router).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
HaroldNetwork EngineerAuthor Commented:
Ok, I have a couple things to look at and try which will take a little time, as the box is a customers server, not here, so bare with me as I test this.
HaroldNetwork EngineerAuthor Commented:
Now I have to figure out what my best DHCP setup is, with the VPN tunnels we have in place!!!!

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.