Symptoms
Consider the following scenario:
-
You have a domain that includes a primary domain controller (PDC) and a read-only domain controller (RODC).
-
The PDC and the RODC are running on Windows Server 2008 R2-based or Windows Server 2008-based computers.
-
You create a user account and configure the user account's password to be cached on the RODC.
-
You try to log on to the domain by using the user account and provide an incorrect password.
-
The logon request is sent to the RODC.
-
You try to log on to the domain again by using the same user account and provide the correct password.
In this scenario, the badPwdCount attribute is reset to 0 on the RODC. However, the badPwdCount attribute is not reset to 0 on the PDC. The expected behavior is that the badPwdCount attribute is reset to 0 on both the RODC and the PDC. Because of this issue, the user account will be locked incorrectly if the total amount of incorrect password attempts exceeds the value that is set in the Account Lockout Threshold Group Policy setting.
Note The incorrect password attempts can be not in succession.
Cause
This issue occurs because the Security Accounts Manager (SAM) server does not support badPwdCount attribute requests that come from an RODC.
Resolution
To resolve this issue, install this hotfix on the Windows Server 2008 R2 or Windows Server 2008 read/write domain controllers (RWDCs) in domains that contain RODCs.
Note You do not need to install this hotfix on the affected RODC.
Ideally, all servers in an organization can run the latest versions of Windows and take advantage of all the advanced features that are available. Realistically, an organization usually has domain controllers that are running different operating systems. In this kind of organization, an RODC may send badPwdCount attribute requests to a SAM server that is running Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, or possibly an earlier operating system. Before you install this hotfix, a SAM server that is running one of these operating systems will reject the requests. After you install this hotfix, Windows Server 2008 R2-based and Windows Server 2008-based WDCs will no longer reject the requests, but domain controllers that are running an earlier operating system will still reject them. This issue will not be resolved on computers that are running Windows Server 2003 or earlier operating systems.
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 the problem described in this article. 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 website:
http://support.microsoft.com/contactus/?ws=supportNote 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, you must be running one of the following operating systems:
-
Windows Server 2008 Service Pack 2 (SP2)
-
Windows Server 2008 R2
-
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.0.600
2.
22xxxWindows Server 2008
SP2
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Samlib.dll |
6.0.6002.22747 |
57,344 |
26-Nov-2011 |
18:59 |
x86 |
|
Samsrv.dll |
6.0.6002.22747 |
484,352 |
26-Nov-2011 |
18:59 |
x86 |
|
Samsrv.mof |
Not Applicable |
61,288 |
15-Nov-2011 |
15:06 |
Not Applicable |
For all supported x64-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Samlib.dll |
6.0.6002.22747 |
99,328 |
25-Nov-2011 |
15:23 |
x64 |
|
Samsrv.dll |
6.0.6002.22747 |
673,792 |
25-Nov-2011 |
15:23 |
x64 |
|
Samsrv.mof |
Not Applicable |
61,288 |
15-Mar-2011 |
04:38 |
Not Applicable |
|
Samlib.dll |
6.0.6002.22747 |
57,344 |
26-Nov-2011 |
18:59 |
x86 |
|
Samsrv.mof |
Not Applicable |
61,288 |
15-Nov-2011 |
15:06 |
Not Applicable |
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.1.760
0.
21xxxWindows Server 2008 R2
RTM
LDR
6.1.760
1.
21xxxWindows Server 2008 R2
SP1
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Samsrv.dll |
6.1.7600.21085 |
761,344 |
05-Nov-2011 |
05:30 |
x64 |
|
Samsrv.mof |
Not applicable |
62,541 |
10-Jun-2009 |
20:35 |
Not applicable |
|
Samsrv.dll |
6.1.7601.21855 |
761,856 |
05-Nov-2011 |
05:36 |
x64 |
|
Samsrv.mof |
Not applicable |
62,541 |
10-Jun-2009 |
20:35 |
Not applicable |
|
Samlib.dll |
6.1.7600.21085 |
60,928 |
05-Nov-2011 |
04:36 |
x86 |
|
Samsrv.mof |
Not applicable |
62,541 |
22-Jul-2009 |
23:04 |
Not applicable |
|
Samlib.dll |
6.1.7601.21855 |
60,928 |
05-Nov-2011 |
04:31 |
x86 |
|
Samsrv.mof |
Not applicable |
62,541 |
12-Nov-2010 |
23:39 |
Not applicable |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about the ResetBadPwdCount request, visit the following Microsoft website:
General information about the ResetBadPwdCount request
Additional file information
Additional file information for Windows Server 2008
Additional files for all supported x86-based versions of Windows Server 2008
|
File name |
Update.mum |
|
File version |
Not Applicable |
|
File size |
3,078 |
|
Date (UTC) |
28-Nov-2011 |
|
Time (UTC) |
07:45 |
|
Platform |
Not Applicable |
|
File name |
X86_d1a3603c8735e2533a2f6bf81a30cb2a_31bf3856ad364e35_6.0.6002.22747_none_361973ee123198c7.manifest |
|
File version |
Not Applicable |
|
File size |
710 |
|
Date (UTC) |
28-Nov-2011 |
|
Time (UTC) |
07:45 |
|
Platform |
Not Applicable |
|
File name |
X86_microsoft-windows-directory-services-sam_31bf3856ad364e35_6.0.6002.22747_none_b43a3b7cb7528ad6.manifest |
|
File version |
Not Applicable |
|
File size |
96,175 |
|
Date (UTC) |
26-Nov-2011 |
|
Time (UTC) |
19:31 |
|
Platform |
Not Applicable |
Additional files for all supported x64-based versions of Windows Server 2008
|
File name |
Amd64_8f4d673818b41f1b3d297d94a85f0645_31bf3856ad364e35_6.0.6002.22747_none_592113b13d94ac5f.manifest |
|
File version |
Not Applicable |
|
File size |
1,070 |
|
Date (UTC) |
28-Nov-2011 |
|
Time (UTC) |
07:45 |
|
Platform |
Not Applicable |
|
File name |
Amd64_microsoft-windows-directory-services-sam_31bf3856ad364e35_6.0.6002.22747_none_1058d7006faffc0c.manifest |
|
File version |
Not Applicable |
|
File size |
96,214 |
|
Date (UTC) |
25-Nov-2011 |
|
Time (UTC) |
15:54 |
|
Platform |
Not Applicable |
|
File name |
Update.mum |
|
File version |
Not Applicable |
|
File size |
3,102 |
|
Date (UTC) |
28-Nov-2011 |
|
Time (UTC) |
07:45 |
|
Platform |
Not Applicable |
|
File name |
Wow64_microsoft-windows-directory-services-sam_31bf3856ad364e35_6.0.6002.22747_none_1aad8152a410be07.manifest |
|
File version |
Not Applicable |
|
File size |
92,228 |
|
Date (UTC) |
26-Nov-2011 |
|
Time (UTC) |
19:06 |
|
Platform |
Not Applicable |
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
|
File name |
Amd64_0ec034126e2be27ba6c909e65275ee8a_31bf3856ad364e35_6.1.7601.21855_none_bf29252167b2613d.manifest |
|
File version |
Not applicable |
|
File size |
714 |
|
Date (UTC) |
05-Nov-2011 |
|
Time (UTC) |
18:28 |
|
Platform |
Not applicable |
|
File name |
Amd64_4da942e013b184a2a821b6077193c4bd_31bf3856ad364e35_6.1.7601.21855_none_261b2480a8741d80.manifest |
|
File version |
Not applicable |
|
File size |
1,070 |
|
Date (UTC) |
05-Nov-2011 |
|
Time (UTC) |
18:28 |
|
Platform |
Not applicable |
|
File name |
Amd64_a3ae1e73e7e2cecdb3f77a202332a09d_31bf3856ad364e35_6.1.7600.21085_none_3f2f634ca787d07f.manifest |
|
File version |
Not applicable |
|
File size |
1,070 |
|
Date (UTC) |
05-Nov-2011 |
|
Time (UTC) |
18:28 |
|
Platform |
Not applicable |
|
File name |
Amd64_b6535a8c1758d25f40f995fd080716ed_31bf3856ad364e35_6.1.7600.21085_none_8b49b9feb378da5c.manifest |
|
File version |
Not applicable |
|
File size |
714 |
|
Date (UTC) |
05-Nov-2011 |
|
Time (UTC) |
18:28 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-directory-services-sam_31bf3856ad364e35_6.1.7600.21085_none_0e6cc96fd3c359da.manifest |
|
File version |
Not applicable |
|
File size |
99,404 |
|
Date (UTC) |
05-Nov-2011 |
|
Time (UTC) |
18:36 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-directory-services-sam_31bf3856ad364e35_6.1.7601.21855_none_1073bffdd0d13bd8.manifest |
|
File version |
Not applicable |
|
File size |
99,404 |
|
Date (UTC) |
05-Nov-2011 |
|
Time (UTC) |
18:36 |
|
Platform |
Not applicable |
|
File name |
Update.mum |
|
File version |
Not applicable |
|
File size |
3,215 |
|
Date (UTC) |
05-Nov-2011 |
|
Time (UTC) |
18:28 |
|
Platform |
Not applicable |
|
File name |
Wow64_microsoft-windows-directory-services-sam_31bf3856ad364e35_6.1.7600.21085_none_18c173c208241bd5.manifest |
|
File version |
Not applicable |
|
File size |
81,227 |
|
Date (UTC) |
05-Nov-2011 |
|
Time (UTC) |
04:57 |
|
Platform |
Not applicable |
|
File name |
Wow64_microsoft-windows-directory-services-sam_31bf3856ad364e35_6.1.7601.21855_none_1ac86a500531fdd3.manifest |
|
File version |
Not applicable |
|
File size |
81,227 |
|
Date (UTC) |
05-Nov-2011 |
|
Time (UTC) |
04:48 |
|
Platform |
Not applicable |
Call stack information
If you enable verbose netlogon.log logging on the problematic RODC, the following information is logged when this issue occurs:
09/02 00:06:48 [LOGON] SamLogon: Network logon of <user name> from <computer name> Entered 09/02 00:06:48 [SESSION] I_NetLogonSendToSamOnDc: Sending buffer to DC of (null), SCType 0 09/02 00:06:48 [CRITICAL] NlPrintRpcDebug: Couldn't get EEInfo for I_NetLogonSendToSam: 1761 (may be legitimate for 0xc00000bb) 09/02 00:06:48 [CRITICAL] I_NetLogonSendToSamOnDc: (null): failed C00000BB 09/02 00:06:48 [LOGON] SamLogon: Network logon of <user name> from <computer name> Returns 0x0 It means the PDC reject the request for resetting the badpwdcount from the the RODC with the error 0xc00000bb STATUS_NOT_SUPPORTED
