in Win7, why does it take 7s before telling me the password is wrong?
i wake up my laptop, and try login. there's an interesting symptom: if i type the correct password in login screen in win7, it takes 1s to show me the desktop if i type an incorrect password in login screen in win7, it takes 7s to show me the desktop what makes a difference in above situations?-Xiaofeng
February 8th, 2012 11:56pm

In the last episode of <6434520b-2e8b-47f0-a8f6-8059f2424df9@communitybridge.codeplex.com>, Xiaofeng Tang said: i wake up my laptop, and try login. there's an interesting symptom: if i type the correct password in login screen in win7, it takes 1s to show me the desktop if i type an incorrect password in login screen in win7, it takes 7s to show me the desktop what makes a difference in above situations? Are you connected to an Active Directory domain? If so, this is normal behaviour, because while your machine or any DC can confirm a correct password, confirming an incorrect password requires one or more DCs to be involved.
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2012 12:02am

Thanks Dave, your answer makes sense. yes, it's connected to corp domain. if i disconnect from network, confirming an incorrect password will be quite fast(because it's using local data in my pc to confrim), right? Or it still try to connect to a dc until getting no reponse?-Xiaofeng
February 9th, 2012 12:13am

In the last episode of <e0298300-286a-422b-b9cd-779369e65a1e@communitybridge.codeplex.com>, Xiaofeng Tang said: Thanks Dave, your answer makes sense.  yes, it's connected to corp domain. if i disconnect from network, confirming an incorrect password will be quite fast(because it's using local data in my pc to confrim), right? Or it still try to connect to a dc until getting no reponse? Basically what happens, from what I can recall, is this: When you enter a password, your system first checks it against the locally cached password. If successful, the login can proceed immediately. If your password fails, your system will then connect to the nearest DC, and if the password is still incorrect the request goes up to the PDC emulator before finally getting rejected. All of this happens reasonably quickly in most Active Directory environments. Similarly, after the local cache fails to authenticate the user, Windows will be able to detect the lack of a network connection and return an error quickly. What causes significant delays is if you have network connectivity but no available DC, since Windows makes several attempts to find and connect to a DC.
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2012 12:27am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics