Microsoft KB Archive/222164

= DSMN Fails to Synchronize Passwords When Password History Is Turned On on NetWare =

Article ID: 222164

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows Services for Netware 4.0

-



This article was previously published under Q222164



SYMPTOMS
Users can no longer access NetWare servers managed through Directory Service Manager for NetWare (DSMN) even after their password has been reset.

This problem is very likely to happen with users who forget their password often and the administrators always use the same password when they reset it.

DSMN does not log an event nor display an error message when this happens.



CAUSE
When a user, who exists on Windows NT, forgets the password and asks the administrators to reset it, the administrators can set the password in the domain regardless of the password history. But, if the user's password happens to be in the password history of a NetWare server, DSMN fails to change the password and the user cannot log on to this server with his or her new password.

In your Windows NT domain, you have a password history enabled of at least eight unique passwords as suggested by the Directory Service Manager for NetWare's online Help.

On NetWare servers running under DSMN, you still have password history turned on; for example, because there are still user accounts not managed through Windows NT.

When the new password is sent to the NetWare server, it returns error 0xA0 (PASSWORD_NOT_UNIQUE). DSMN ignores this error code.



Windows NT Server or Workstation 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:


 * http://www.microsoft.com/windows/servicepacks/ -or-


 * 152734 how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

Windows NT Server 4.0, Terminal Server Edition
To resolve this problem, obtain the latest service pack for 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 How to Obtain the Latest Windows NT 4.0 Service Pack



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Keywords: kbhotfixserver kbqfe kbbug kbpending KB222164

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.