A secure channel is broken after you change the computer password on a Windows 7 or Windows Server 2008 R2-based client computer

Symptoms

In an Active Directory domain environment, the domain controllers (DCs) are running Pre-Windows Server 2008 R2 operating system. When the computer password is changed on a client computer that runs Windows 7 or Windows Server 2008 R2, you will encounter an issue in which the secure channel is broken.

For example, after the password of a client computer is changed, you will see an access denied error when you run the following command on the client computer to query the secure channel:

nltest /sc_query:domain name

When this problem occurs, you have to manually add the client computer back to domain.

Cause

This problem occurs because of a design change in the netlogon!nlsessionsetup function.

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 Windows 7 or 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 7 and 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 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 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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 7

File name

File version

File size

Date

Time

Platform

Netlogon.dll

6.1.7600.20621

563,712

19-Jan-2010

11:55

x86

Nlsvc.mof

Not applicable

2,873

10-Jun-2009

21:29

Not applicable

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Netlogon.dll

6.1.7600.20621

692,736

19-Jan-2010

10:29

x64

Nlsvc.mof

Not applicable

2,873

10-Jun-2009

20:47

Not applicable

Netlogon.dll

6.1.7600.20621

563,712

19-Jan-2010

11:55

x86

Nlsvc.mof

Not applicable

2,873

10-Jun-2009

21:29

Not applicable

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Netlogon.dll

6.1.7600.20621

1,148,416

19-Jan-2010

09:00

IA-64

Nlsvc.mof

Not applicable

2,873

10-Jun-2009

20:52

Not applicable

Netlogon.dll

6.1.7600.20621

563,712

19-Jan-2010

11:55

x86

Nlsvc.mof

Not applicable

2,873

10-Jun-2009

21:29

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

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

X86_f911bf6a58e8bb9bb18d8e7376871192_31bf3856ad364e35_6.1.7600.20621_none_b063bb4105122c1a.manifest

File version

Not applicable

File size

705

Date (UTC)

19-Jan-2010

Time (UTC)

18:48

Platform

Not applicable

File name

X86_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.20621_none_fe548c5db23e0ade.manifest

File version

Not applicable

File size

35,541

Date (UTC)

19-Jan-2010

Time (UTC)

13:41

Platform

Not applicable

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

File name

Amd64_4145a25025a7ec53385d65c6c3386116_31bf3856ad364e35_6.1.7600.20621_none_b814d27d5d42837a.manifest

File version

Not applicable

File size

709

Date (UTC)

19-Jan-2010

Time (UTC)

18:48

Platform

Not applicable

File name

Amd64_ff3660122f7bc879a2c3e65720f0dc8a_31bf3856ad364e35_6.1.7600.20621_none_48e1e40324e2ea72.manifest

File version

Not applicable

File size

1,060

Date (UTC)

19-Jan-2010

Time (UTC)

18:48

Platform

Not applicable

File name

Amd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.20621_none_5a7327e16a9b7c14.manifest

File version

Not applicable

File size

35,547

Date (UTC)

19-Jan-2010

Time (UTC)

13:40

Platform

Not applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.20621_none_64c7d2339efc3e0f.manifest

File version

Not applicable

File size

16,596

Date (UTC)

19-Jan-2010

Time (UTC)

13:27

Platform

Not applicable

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

File name

Ia64_c2b873c51c4611f3e97ee06b02385bec_31bf3856ad364e35_6.1.7600.20621_none_8cabca96d5a6d4a1.manifest

File version

Not applicable

File size

1,058

Date (UTC)

19-Jan-2010

Time (UTC)

18:48

Platform

Not applicable

File name

Ia64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.20621_none_fe563053b23c13da.manifest

File version

Not applicable

File size

35,544

Date (UTC)

19-Jan-2010

Time (UTC)

13:41

Platform

Not applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.20621_none_64c7d2339efc3e0f.manifest

File version

Not applicable

File size

16,596

Date (UTC)

19-Jan-2010

Time (UTC)

13:27

Platform

Not applicable

Kas vajate veel abi?

Täiendage oma oskusi
Tutvuge koolitusmaterjalidega
Kasutage uusi funktsioone enne teisi
Liitu Microsofti Insideri programmis osalejad

Kas sellest teabest oli abi?

Täname tagasiside eest!

Täname tagasiside eest! Tundub, et võiksime teid kokku viia ühega meie Office'i tugiagentidest, kes aitab teil probleemi lahendada.

×