long delay at windows 7 starting screen when logging into a domain account

[nervegrind3r]

hey all, I got my new laptop from work yesterday (lenovo t520), and one of the things that annoys me is the long delay when logging into windows. I put my own ssd in there, and its quick as hell to get to the login screen or shutdown, but regardless, after I put my credentials in to login in with my network account (doesnt matter if im at my home network, work network, or the network cable is disconnected), it takes a solid 30 seconds to get to the desktop.

I googled and tried different settings and registry things for a solid 2-3 hours last night and couldnt figure it out. I am pretty certain a windows system service is causing the issue based on the following that I found out:

If I log in with a local admin account, 1 sec wait after I put in credentials
If I do a clean boot with no system and startup services selected, 1 sec wait after I put in credentials
If I do a clean boot with ONLY microsoft services selected (no non-microsoft system or application startup services), then I have a 30 sec wait after I put in credentials.


I really hate to test every ms system services one at a time, to reboot, or combination or services to find out whats going on. I also tried several gpedit changes, registry changes, different backgrounds, etc, basically the top 20 google searches for this issue I tried, and various solution came up.

any ideas folks?

thanks

 

[corkyg]

It could be your AV system checking it out before connecting. Try it with AV disabled. If that helps, consider putting that domain on the exempt list.

 

[nervegrind3r]

already uninstalled av and same thing happens

 

[heymrdj]

NOrmally I see these things caused by DNS issues on the network.

 

[nervegrind3r]

for my testing, I have the laptop disconnected from any network, but I am logging in my system with a domain account.

I know its a microsoft windows service causing the problem. For example, I know if I disable network store interface service, I boot right in to windows (the same as a local account), but that completely kills my network activity.

There must be a way around this

 

[Matt1970]

Do you have any mapped drives that are no longer there? I have seen that cause a good delay before.

 

[nervegrind3r]

Do you have any mapped drives that are no longer there? I have seen that cause a good delay before.

i had several, but thats one of the first things I removed

 

[ZeroRift]

I tend to agree with heymrdj....

It sounds like a DNS timeout is taking place when you log on to your domain account. Do you have any folder redirection policies set? Do you have Offline Files configured?

You mentioned you do all of your testing disconnected from any network; What happens if you log in / out a few times while connected to your domain? Any errors / warnings in your application logs or group policy logs?

You might also try running netmon with the local admin account, then switch users to your domain account and try to log in. Any network lookups would be recorded in the netmon file when you went back to your local admin account. You'd need to be savvy with packet captures to interpret the results, however.... "currports" or "TCPView" might also do the job with the right settings and they would be easier to use.