Select the product you need help with
How the BadPwdCount attribute works in Windows 2000 and in Windows Server 2003Article ID: 900215 - View products that this article applies to. INTRODUCTIONThis articles discusses how the bad password count attribute
(BadPwdCount) works in Microsoft Windows 2000 and in Microsoft Windows Server
2003. When you submit incorrect credentials to the Active Directory directory
service, the value of the BadPwdCount attribute of that user object increases. This attribute is used
to determine whether a user account will be locked out based on the password
lockout policy. In Windows 2000 and in Windows Server 2003, the value of the BadPwdCount attribute should increase one time when the following conditions are true:
However, in Windows Server 2003, the BadPwdCount attribute increases only one time when you use the UPN to bind your incorrect credentials to Active Directory. MORE INFORMATIONThe BadPwdCount attribute should increase one time when you submit incorrect
credentials to Active Directory. However, in Windows 2000, when you use the IADsOpenDsObject::OpenDsObject method and the UPN to submit credentials, the credentials are submitted one time by NTLM authentication and one time by Kerberos authentication. Therefore, the BadPwdCount attribute increases two times. In Windows Server 2003, the double increment does not occur. For more information about the BadPwdCount attribute, visit the following Microsoft Web site: http://msdn2.microsoft.com/en-us/library/ms675244.aspx For more
information, click the following article number to view the article in the
Microsoft Knowledge Base:
(http://msdn2.microsoft.com/en-us/library/ms675244.aspx)
817701
(http://support.microsoft.com/kb/817701/
)
Service packs and hotfixes that are available to resolve account lockout issues
PropertiesArticle ID: 900215 - Last Review: January 30, 2007 - Revision: 1.3 APPLIES TO
|


Back to the top








