Select the product you need help with

Invalid Password Message When Strong Passwords Are Required

Article ID: 174076 - View products that this article applies to.

This article was previously published under Q174076

SYMPTOMS

After you change your password, you receive an error indicating that it does not meet the domain password requirements; however, the stated requirements have been met.

Back to the top | Give Feedback

CAUSE

Normally, this message is correct; however, when strong passwords are required there may be restrictions in effect that will exclude many passwords.

Back to the top | Give Feedback

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734

(http://support.microsoft.com/kb/152734/EN-US/ )

How to Obtain the Latest Windows NT 4.0 Service Pack

NOTE: The hotfix will need to be applied to all clients. The client is responsible for mapping a text message to the error code returned from the server.

Back to the top | Give Feedback

MORE INFORMATION

The old password error message was:

Your new password does not meet the minimum length or password history requirements of the domain.

The new messages displayed after you apply the fix are:

Your new password does not meet the minimum length or password history requirements of the domain. Also, your site may require passwords that must be a combination of upper case, lower case, numbers, and non-alphanumeric characters.

Your password must be at least <#> characters long. Your new password cannot be the same as any of your previous <#> passwords. Also, your site may require passwords that must be a combination of upper case, lower case, numbers, and non-alphanumeric characters.

The numeric <#> in the previous dialog box comes from the Account Policy in User Manager.

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Back to the top | Give Feedback