Microsoft KB Archive/292573

= ADSI SetPassword Call Does Not Always Set the Password on the Target Domain Controller =

Article ID: 292573

Article Last Modified on 2/19/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition

-



This article was previously published under Q292573



SYMPTOMS
When you use Active Directory Service Interface (ADSI) SetPassword to reset a user's password, the password may not be reset on the server that ADSI is bound to. For example, when you use the Users and Computers Snap-In with the focus set on domain controller (DC) 3 to reset the user's password and to create a setting that requires the user to change passwords at the next logon, the password may be set on a DC other than DC3, but the user must change passwords at the next logon, and a flag is set on DC3.



CAUSE
ADSI's LDAP provider uses the Kerberos library to reset the users password and the call that is made into Kerberos does not take the server name as a parameter but rather only the domain name. Depending on what is found in the Kerberos binding cache the password could actually be set on a different DC than what ADSI is connected to.



RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

Date        Time       Version          Size         File name -- 6/4/2001  05:16p   5.0.2195.3680    501,520   Lsasrv.dll(56-bit) 6/13/2001  12:17p   5.0.2195.3729    62,736   Adsmsext.dll 6/13/2001  12:17p   5.0.2195.3692   355,088   Advapi32.dll 6/13/2001  12:13p   5.0.2195.3680   519,440   Instlsa5.dll 6/13/2001  12:17p   5.0.2195.3698   142,608   Kdcsvc.dll 6/13/2001  12:04p   5.0.2195.3729   209,008   Kerberos.dll 5/29/2001  09:26a   5.0.2195.3649    69,456   Ksecdd.sys 6/4/2001  05:16p    5.0.2195.3680   501,520   Lsasrv.dll 6/4/2001  05:16p    5.0.2195.3680   33,552    Lsass.exe 6/13/2001  12:17p   5.0.2195.3727  909,072    Ntdsa.dll 6/13/2001  12:17p   5.0.2195.3678  382,736    Samsrv.dll 5/29/2001  09:53a   5.0.2195.3649  128,784    Scesrv.dll



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 2000 Service Pack 3.



MORE INFORMATION
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Additional query words:

Keywords: kbhotfixserver kbqfe kbbug kbenv kbfix kbsecurity kbwin2000presp3fix kbwin2000sp3fix KB292573

-

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

© Microsoft Corporation. All rights reserved.