Already enabled. I already posted that in my original post. I should have been more detailed in describing what i already tried. Sorry
Any other ideas?
Main Topics
Browse All TopicsWe have many users having slow domain logon issues and I can't seem to pinpoint the problem. The issue is hit or miss. One day they'll logon normal/fast, and then another day it'll take anywhere from 1-5 minutes for their icons to come up. I set user verbose logging on and pulled this log (attached). I'm having trouble interpretting where it could be slowing down.
Network Info.
Windows Server 2003 SP2 Domain Controller providing DNS and DHCP as well.
Stations having the issue are Windows XP SP2 computers.
We also have some laptops with Windows Vista and none of them have problems.
Possible Solutions Tried:
Disabling/Uninstalling certain startup programs.
Adjusting startup scripts and GPOs
Making sure wait for nework was enabled in AD. Turned on Asyncronous load of scripts in AD
Forced Kerberos to use TCP instead of UDP in Windows (http://support.microsoft.
Gave local administrative rights to the user.
I can't remember what else at the moment
.
If you need anymore information just ask.
Please help.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
On your DNS server, it should have its NIC settings static IP with the first DNS pointing to itself and second to your next internal. THen in your DHCP settings, the server config should have internal servers set for DNS. That way it will had out the internal servers.
Also, I know your running xp sp2, but have you reviewed the following EE solution. There is alot of good info in there.
http://www.experts-exchang
cracksalsa,
I checked all of the DNS settings as you suggested and they were all correct. Even the DHCP settings. Also, I looked into that other EE solution you mentioned. Most of the links in there were broken, but managed to find more information about some from google. Going to see if I can find that bootvis.exe tool. One other thing suggested in that EE solution is to disable BITS, but I'm a little concerned this will break our WSUS updating.
dfke,
I checked what you suggested, about adding domain computers to the default domain GPO and sure enough it wasn't there (only authenticated users was there). I added it but it's going to take a little time to determine if that fixes anything. Not sure who setup the Group Policy's before I was hired but it looks like i'll be checking all off the GPOs to make sure the security rights are correct.
I'll let you know how everything turns out, if you have any more suggestions in the mean time, please post them.
Thanks!
You are checking all the right things from a network point of view, just thought I would throw some opinions in there from the desktop point of view.
Its not always easy to upgrade to SP3 in a corporate environemt, I know.. but its worth trying on one system to see the speed of login differences (you can always change it back afterwards). I have found SP3 to handle login speeds on a domain far better than SP2, something to try and see the differences :)
Also, i have tested on some systems removing the iconcache.db file from local settings > application data on a users profile. This too seems to improve the log in time believe it or not ;)
good luck :)
use Netlogon debug (http://support.microsoft.
http://support.microsoft.c
After a murphy's law type of IT morning, I got to checking usrenv logs and it seems more people are having the slowness issue this morning. I pulled open that usrenv log on several machines and noticed a lot of this entry that i havent seen much of:
GetGPOInfo: Local GPO's gpt.ini is not accessible, assuming default state.
dfke,
It seems these computers are hanging longer at the applying comptuer settings now. It sounds like adding domain computers to our Group Policy Objects is affecting this somehow. Not sure though. Any ideas?
maze-uk,
I went to turn the netlogon debug on but it seems that the registry key that microsoft says to delete isn't even there in the registry. In fact the DBFlag path doesnt even exist (the Parameters path does, just no DBFlag folder underneath). Any ideas?
VCBooth,
I looked into that microsoft link. Unless you know of someone that turned that setting to disabled and it fixed a slow logon, I don't think i want to change it. It's in a not configured state right now and I havent seen anything on our end that points to the symptoms that microsoft describes for it.
Thanks!
Business Accounts
Answer for Membership
by: VCBoothPosted on 2009-09-01 at 12:34:22ID: 25235109
This is caused by the asyncronous loading of networking during the boot up process. This speeds up the login process in a stand-alone workstation by allowing the user to log in with cached logon credentials before the network is fully ready.
ive Templates-->System-->Logon, change "Always wait for the network at computer startup and logon" to ENABLED.
To disable this "feature" and restore your domain logons to their normal speed, open the MMC and add the group policy snap-in. Under Computer Configuration-->Administrat
This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template. Since this is an XP only command, non-XP systems will ignore it in a domain distributed group policy.