Article ID: 812499
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
After an administrator resets a user account password and then sets it to immediately expire, the user may not be able to change his or her password during the next logon attempt. However, if the user waits a while, the user can then change the password.
CAUSE
This problem is caused by domain controller replication latency, and may occur if the user's password is changed on a domain controller in a site other than the site where the user is located. For more information about the cause of this problem, click the following article number to view the article in the Microsoft Knowledge Base:
320325 User may not be able to change their password if you configure the 'User must change password at next logon' setting
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For more 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
Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The Global 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.
Date Time Version Size File name -------------------------------------------------------------- 16-Feb-2003 23:30 5.0.2195.6613 124,176 Adsldp.dll 16-Feb-2003 23:30 5.0.2195.6601 130,832 Adsldpc.dll 24-Feb-2003 23:06 5.0.2195.6667 62,736 Adsmsext.dll 16-Feb-2003 23:30 5.0.2195.6660 377,616 Advapi32.dll 16-Feb-2003 23:30 5.0.2195.6611 49,936 Browser.dll 16-Feb-2003 23:30 5.0.2195.6663 135,952 Dnsapi.dll 16-Feb-2003 23:30 5.0.2195.6663 96,528 Dnsrslvr.dll 16-Feb-2003 23:30 5.0.2195.6661 46,352 Eventlog.dll 16-Feb-2003 23:30 5.0.2195.6627 148,240 Kdcsvc.dll 20-Feb-2003 23:11 5.0.2195.6666 204,560 Kerberos.dll 03-Dec-2002 02:09 5.0.2195.6621 71,888 Ksecdd.sys 24-Jan-2003 21:40 5.0.2195.6659 509,712 Lsasrv.dll 24-Jan-2003 21:41 5.0.2195.6659 33,552 Lsass.exe 05-Feb-2003 15:59 5.0.2195.6662 109,328 Msv1_0.dll 16-Feb-2003 23:30 5.0.2195.6601 312,592 Netapi32.dll 16-Feb-2003 23:30 5.0.2195.6627 360,720 Netlogon.dll 24-Feb-2003 23:05 5.0.2195.6669 929,552 Ntdsa.dll 24-Feb-2003 23:05 5.0.2195.6666 392,464 Samsrv.dll 16-Feb-2003 23:30 5.0.2195.6622 112,912 Scecli.dll 16-Feb-2003 23:30 5.0.2195.6625 305,936 Scesrv.dll 10-Feb-2003 22:22 5.0.2195.6663 166,912 Sp3res.dll 16-Feb-2003 23:30 5.0.2195.6601 51,472 W32time.dll 16-Aug-2002 12:32 5.0.2195.6601 57,104 W32tm.exe 24-Feb-2003 23:05 5.0.2195.6666 125,200 Wldap32.dll 24-Feb-2003 22:24 5.0.2195.6659 509,712 Lsasrv.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To disable the new behavior that this hotfix provides, add or edit the SamDisableSingleObjectRepl item. To do this, follow these steps:
- Click Start, click Run, type Regedit, and then click OK.
- Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Note If you do not find the SamDisableSingleObjectRepl item in this subkey, follow these steps:
- On the Edit menu, point to New, and then click DWORD Value.
- In the details pane, type the new value SamDisableSingleObjectRepl.
- Right-click SamDisableSingleObjectRepl, and then click Modify.
- In the Edit DWORD Value dialog box, under Base, click click Decimal.
- In the Value data box, type the value 1, and then click OK.
- Close Registry Editor.
To re-enable the new behavior made available by this update, delete the registry key or change the value of the key to 0.
For more information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the following article number to view the article in the Microsoft Knowledge Base:
265173 The Datacenter program and Windows 2000 Datacenter Server product
You may receive the following Event on the domain controllers where you must install this hotfix:
DC is logging kerberos event id 7 0x108 event in the system log:
Event Type: Error
Event Source: KDC
Event Category: None
Event ID: 7
Description: The Security Account Manager failed a DC (or a KDC) request in an unexpected way. The error is in the data field.
The account name was ????O???????e and lookup type ax. Data: 0000: 34 00 00 c0 4..À
Keywords: kbhotfixserver kbqfe kbdirservices kbwin2ksp4fix kbenv kbwin2000presp4fix kbfix kbbug KB812499
