Server 2003 takes 2-3 minutes to "apply personal settings" when logging on.


We have aServer 2003 running as a Terminal server. For the past week it takes between 2 to 3 miutes to login. It stays on "Applying personal settings" for most of the time.

They never had this problem though.

Any ideas to why it takes so long to logon?!?
Optima SystemsNetwork 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.

Ben StirlingOperations Technology AnalystCommented:
If this server is on a domain (I'm betting it is) check that there are no issues resolving DNS and reaching the DC.

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
Don S.Commented:
That is generally either a Group policy driven thing, or a profile driven thing.  GPO could be installing software, or mapping drives or printers that are now not available or some other issue applying one or more policies.  The user's profile may be corrupt or have other issues (are they roaming profiles on here?)
Optima SystemsNetwork EngineerAuthor Commented:
We tried a new profile and it made no difference. It turned out to be a DNS issue. We deleted the fixed DNS entry and then cleared all the cache and re-entered the local IP of the local DNS server. This cured it immediately.
Optima SystemsNetwork EngineerAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for JayHine's comment #a40298489

for the following reason:

We solved it by resetting the DNS entry
Optima SystemsNetwork EngineerAuthor Commented:
It was the DNS settings on the Terminal Server which were causing the problem.
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.