Knowledge Base

Password Uniqueness May Not Account for Case Sensitivity

Article ID: 165091

Article Last Modified on 11/1/2006

APPLIES TO

This article was previously published under Q165091

SYMPTOMS

If the Account Policy for a domain requires a unique password and you try to change your password on a client computer that has support for case sensitive passwords, changes in case may not count as a unique password.

MORE INFORMATION

When a Windows NT-based computer negotiates a session with a Windows NT-based domain controller, it sets flags that show that it can support case-sensitive passwords. This means there is case distinction of passwords, for example, you can change your password from "password" to "PassWord".

Down-level clients (such as Microsoft Windows for Workgroups, Microsoft Windows 95, and Mac OS 9 clients) do not support case-sensitive passwords. Because of this, when a password is set on the domain, two copies of it are stored. If the password is set from a down-level client, both passwords stored are the same. However, if the password is set by a client with support for case-sensitive passwords, the case-specific password is stored along with a case-insensitive password. By doing so, you can set a case-sensitive password and still be able to logon from a down-level client.

When password uniqueness is checked, it compares the password it is given to the case-insensitive password. This limits you to actual character changes when you make a unique password. For additional information about passwords and case sensitivity, click the following article number to view the article in the Microsoft Knowledge Base:

294562 OL2001: The Domain Password in Outlook Is Not Case Sensitive

STATUS

Microsoft has confirmed that this is a problem in Windows NT.

Keywords: kbenv kbprb KB165091


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.