Symptoms

Consider the following scenario:

  • You enable selective authentication over a trust between two Active Directory forests.

  • You use a user account from one Active Directory forest to access a resource server in another Active Directory forest.

  • NTLM authentication is used in and between these two Active Directory forests.

  • The resource server has a security channel to a Windows Server 2008 R2-based read-only domain controller (RODC).

  • There is no read/write domain controller (RWDC) in the closest site to the RODC.

  • The computer password of the resource server is changed.

In this scenario, selective authentication over the forest trust fails. You may experience various authentication failures. Here are some examples:

  • When you access the resource server, you receive the following error message:

    Access denied

  • You are prompted repeatedly to input your user name and password.

Cause

This issue occurs because the RODC does not have the password of the resource server at the time of authentication.

When the RODC performs the selective authentication check, it tries to read all the Active Directory attributes of the resource server computer object. However, as the RODC cannot retrieve the password of the resource server, this causes authentication to fail.

Resolution

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 Web site:

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 R2

  • Windows Server 2008 R2 Service Pack 1 (SP1)

For more information about how to obtain a 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 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.
    21xxx

    Windows Server 2008 R2

    RTM

    LDR

    6.1.760
    1.
    21xxx

    Windows 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

Netlogon.dll

6.1.7600.21048

693,760

08-Sep-2011

05:30

x64

Nlsvc.mof

Not applicable

2,873

10-Jun-2009

20:47

Not applicable

Netlogon.dll

6.1.7601.21813

695,296

08-Sep-2011

06:33

x64

Nlsvc.mof

Not applicable

2,873

10-Jun-2009

20:47

Not applicable

Netlogon.dll

6.1.7600.21048

564,736

08-Sep-2011

04:26

x86

Nlsvc.mof

Not applicable

2,873

10-Jun-2009

21:29

Not applicable

Netlogon.dll

6.1.7601.21813

564,224

08-Sep-2011

06:19

x86

Nlsvc.mof

Not applicable

2,873

10-Jun-2009

21:29

Not applicable

Workaround

You can use one of the following two methods to work around this issue:

  • Disable account password changes for computers which use a RODC for their security channel.

  • Change the site topology so that there is a RWDC in the closest site to the RODC.


Status

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

More Information

The RODC supports password changes for user accounts over the netlogon security channel. The RODC forwards the password change request to a RWDC when the computer account’s password is changed. When the password change is successful, the RODC makes an opportunistic attempt to replicate the new password. However, the replication attempt may not target the same RWDC to which the password change request is forwarded.

Although the RODC has its own existing security channel with an RWDC over which the password change happens, the RWDC targeted by the replication attempt is selected by using the DClocator mechanism. In most site topologies, this behavior will cause the same domain controller that is being used for the replication attempt to be the current security channel target. However, if there is no RWDC in the same domain in the site closest to the RODC, the password change and replication attempt may occur against different RWDCs.

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 how to enable selective authentication over a forest trust, visit the following Microsoft website:

General information about how to enable selective authentication over a forest trustFor more information about how to configure selective authentication, visit the following Microsoft website:

General information about how to configure selective authentication

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File name

Amd64_0caf3106ff02b60b89c9d545792026c3_31bf3856ad364e35_6.1.7600.21048_none_9a893a6b7aa6f649.manifest

File version

Not applicable

File size

1,060

Date (UTC)

08-Sep-2011

Time (UTC)

09:44

Platform

Not applicable

File name

Amd64_0e7e58fe08c4a3c71653acdcc4a5f0f9_31bf3856ad364e35_6.1.7601.21813_none_1a842e21757b81df.manifest

File version

Not applicable

File size

709

Date (UTC)

08-Sep-2011

Time (UTC)

09:44

Platform

Not applicable

File name

Amd64_d0d81f110ea917a2a3131f5317a03ed1_31bf3856ad364e35_6.1.7601.21813_none_825a6a5ddaa496d5.manifest

File version

Not applicable

File size

1,060

Date (UTC)

08-Sep-2011

Time (UTC)

09:44

Platform

Not applicable

File name

Amd64_dc11db02cc633a9f065ad3f21d62956a_31bf3856ad364e35_6.1.7600.21048_none_ffab83fd2ef937aa.manifest

File version

Not applicable

File size

709

Date (UTC)

08-Sep-2011

Time (UTC)

09:44

Platform

Not applicable

File name

Amd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21048_none_5a6467e36aa5900e.manifest

File version

Not applicable

File size

35,547

Date (UTC)

08-Sep-2011

Time (UTC)

06:01

Platform

Not applicable

File name

Amd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21813_none_5c665cff67b7f359.manifest

File version

Not applicable

File size

35,547

Date (UTC)

08-Sep-2011

Time (UTC)

07:31

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

3,215

Date (UTC)

08-Sep-2011

Time (UTC)

09:44

Platform

Not applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21048_none_64b912359f065209.manifest

File version

Not applicable

File size

16,596

Date (UTC)

08-Sep-2011

Time (UTC)

04:42

Platform

Not applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21813_none_66bb07519c18b554.manifest

File version

Not applicable

File size

16,596

Date (UTC)

08-Sep-2011

Time (UTC)

06:38

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×