You receive a warning message that does not correctly describe the password requirements when you set a new password that does not meet the requirements in Windows Server 2003

Consider the following scenario.

• A Microsoft Windows Server 2003-based domain hosts users.
• Another Windows Server 2003-based domain hosts computers.
• The password expires on a computer that is running Windows Server 2003.
• You set a new password that does not meet the complexity requirements of the domain that hosts users.

In this scenario, you receive a warning message that does not correctly describe the password requirements. The warning message that you receive resembles the following: In this warning message, all the numbers in the password requirements are zeros.

This problem occurs because the computer cannot retrieve the password requirements in an anonymous session.

After a user password expires, the computer can use computer information to create sessions only with the domain controller that hosts the user. In this case, Kerberos authentication fails if the target domain is not in the list of Domain Name System (DNS) suffixes to search. Therefore, the computer uses an anonymous session. In an anonymous session, the computer cannot retrieve the password requirements when the password change fails.

To resolve this problem, apply this hotfix to every Windows Server 2003-based computer on which you receive the incorrect warning message.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix on x86-based versions of Windows Server 2003 or on Itanium-based versions of Windows Server 2003, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed. For more information about how to obtain Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2), click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base: