XP logons taking a long time

we have a 2000 domain with AD and group policy running-- however the logins take a tremendous amount of time - we have disabled the virus scan - check msconfig for startup- deleted cached profiles-- deleted user accounts-- we even did the suggestion from this forum to enabled the "always wait for the network" in group policy on the local box

doing all of these tasks did not help in any way-- the logins can take up to 2 minutes to apply.


the errors we were getting are userenv, 1505, 1053

were also getting and auto enrollment error eventid 15

we also disbaled the background intelligence transfer


HELP

we have had this issue for about 4 months

campbell06410Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

gemartiCommented:
Miscellaneous information (Probably not useful)

Windows XP May Slow Down If Users Are Logged On with Fast User Switching
http://support.microsoft.com/default.aspx?scid=kb;en-us;312058


If you have shared resources that you access through the Network Neighborhood then look at this:

Possible Solutions to Slow Network Browsing
http://www.practicallynetworked.com/sharing/troubleshoot/slowbrowse02.htm
0
stockley31Commented:

XP relies heavily on DNS in networks.

When XP log's onto a Win2k domain, it uses DNS, so if you don't have a local DNS server setup correctly, it will take a long time to boot up.
Make sure your XP's computer has it's DNS server set correctly, and the DNS server is operating correctly.

Slade


0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Fatal_ExceptionSystems EngineerCommented:
yes, first thing to do is to ck your DNS for any errors...  run the following tests:

DCDiag and NetDiag in Windows 2000 Facilitate Domain Join and DC Creation:

http://support.microsoft.com/?kbid=265706

HOW TO: Use the Network Diagnostics Tool (Netdiag.exe) in Windows 2000:

http://support.microsoft.com/?kbid=321708

Description of the DNSLint Utility and dnslint.exe dnload:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;321045

=========

Then, if your slow logons continue you can use a reg hack to discover what part of the logon process is slowing you down..

You can determine which part of the login is slow by enabling the userenv.log in verbose mode on the client machine which will tell you how much time is taken at each process of the logon.    Start > Run > Regedit

Then drill down to:

HKLM\SOFTWARE\MICROSOFT\WINDOWS NT\CURRENTVERSION\WINLOGON

Create key D_WORD

UserEnvDebugLevel = 10002 (Hex)

Then do your logon. After logon check C:\Winnt\Debug\Usermode\userenv.log

It will show you the details of your logon and probably help you pinpoint which part of the logon is slow.  One thing though, you might need to take time to analyze the log as it can be quite long....

FE

0
Fatal_ExceptionSystems EngineerCommented:
Correction...  on your XP systems the log is:

 C:\Windows\Debug\Usermode\userenv.log

:)
0
Fatal_ExceptionSystems EngineerCommented:
Split them up...
0
campbell06410Author Commented:
Actually-- I found the answers to my own questions by a tons of research and troubleshooting -
on our setup in AD we were only using the User configurations setting and had nothing applied in the computer configurations settings  - so the logins were running through the user settings and then sitting there in the computer settings - when we checked to disable the computer setting things moved quicker

we also disabled all offline syncronization - that was a setting I saw through another forum -

disabled all file and print sharig (which by the way when you call Microsoft- every other tech disagreed on this-- but I will tell you for us this worked to have it disabled)


so the items together combined solved the issue.

0
Fatal_ExceptionSystems EngineerCommented:
Good for you..  Everything you mentioned makes perfect sense.  

Suggest a refund then..  

FE
0
Computer101Commented:
PAQed, with points refunded (500)

Computer101
E-E Admin
0

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
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 XP

From novice to tech pro — start learning today.