Friday, December 23, 2022

Client computer uses site-less SRV records after you restart the computer in Windows 7 or in Windows Server 2008 R2 - Microsoft Support [MS]

Symptoms

When you restart a client computer that is running Windows 7 or Windows Server 2008 R2 in an Active Directory domain environment, the Net Logon service starts before the network interface is initialized. This behavior causes the status of the network adapter to change to intermediate. Additionally, this behavior causes the IP address to change even though the network adapter is assigned to the same IP address eventually. In this situation, the client computer uses site-less LDAP DNS Server (SRV) records (_ldap._tcp.DnsDomainName or _ldap._tcp.dc._msdcs.DnsDomainName) to locate the domain controller (DC).

If this issue occurs in an environment in which only the hub DCs for the site-less SRV records are registered in DNS, and if the client computer's remote branch site is disconnected from the hub site, then the client computer cannot locate a DC. However, the local branch DCs are available in DNS when the hub DCs cannot be reached from the branch site. Therefore, the client computer does not recognize the local branch DCs as DCs.

Cause

This issue occurs because the Net Logon service invalidates the cached site information in the registry prematurely.

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 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 7

  • Windows 7 Service Pack 1 (SP1)

  • Windows Server 2008 R2

  • Windows Server 2008 R2 Service Pack 1 (SP1)

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 7 and Windows Server 2008 R2 file information notes


  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    0.21xxx

    Windows 7 and Windows Server 2008 R2

    RTM

    LDR

    6.1.760
    1.21xxx

    Windows 7 and 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 and for Windows 7" 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 x86-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Netlogon.dll

6.1.7600.21149

564,736

11-Feb-2012

05:34

x86

Netlogon.dll

6.1.7601.21921

566,784

11-Feb-2012

05:24

x86

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.21149

693,760

11-Feb-2012

06:31

x64

Netlogon.dll

6.1.7601.21921

698,880

11-Feb-2012

06:23

x64

Netlogon.dll

6.1.7600.21149

564,736

11-Feb-2012

05:34

x86

Netlogon.dll

6.1.7601.21921

566,784

11-Feb-2012

05:24

x86

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.21149

1,150,464

11-Feb-2012

05:19

IA-64

Netlogon.dll

6.1.7601.21921

1,156,608

11-Feb-2012

05:17

IA-64

Netlogon.dll

6.1.7600.21149

564,736

11-Feb-2012

05:34

x86

Netlogon.dll

6.1.7601.21921

566,784

11-Feb-2012

05:24

x86

Status

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

More Information

If you enable debug logging for the Net Logon service by using the method that is described in Microsoft Knowledge Base (KB) article 109626, you receive a sequence that resembles the following. The sequence indicates how the site name is invalidated.10/20 13:20:01 [SITE] Setting site name to 'MyCachedSiteName'
10/20 13:20:01 [SITE] Hint avoided. 31
10/20 13:20:01 [SESSION] \Device\NetBT_Tcpip_{6964FC65-C026-4EC4-A8B9-29C2019401AC}: Transport Added (169.254.237.187)
10/20 13:20:01 [CRITICAL] IPV6SocketAddressList is too small 0.
10/20 13:20:01 [SESSION] Winsock Addrs: 169.254.237.187 (1) Address changed.
10/20 13:20:01 [SESSION] V6 Winsock Addrs: (0)
10/20 13:20:01 [CRITICAL] Address list changed since last boot. (Forget DynamicSiteName.)
10/20 13:20:01 [SITE] Setting site name to '(null)' For more information about KB article 109626, click the following article number to view the article in the Microsoft Knowledge Base:

109626 Enabling debug logging for the Net Logon service

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

If the hotfix is installed, you may also receive the new error messages that is mentioned in Microsoft Knowledge Base (KB) article 2654097. For more information about 2654097, click the following article number to view the article in the Microsoft Knowledge Base:

2654097 New event log entries that track NTLM authentication delays and failures in Windows Server 2008 R2 are available

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_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21149_none_fe46ce8fb2473556.manifest

File version

Not Applicable

File size

35,541

Date (UTC)

11-Feb-2012

Time (UTC)

06:00

Platform

Not Applicable

File name

X86_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21921_none_003af2e1af64688d.manifest

File version

Not Applicable

File size

35,989

Date (UTC)

11-Feb-2012

Time (UTC)

05:52

Platform

Not Applicable

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

File name

Amd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21149_none_5a656a136aa4a68c.manifest

File version

Not Applicable

File size

35,547

Date (UTC)

11-Feb-2012

Time (UTC)

07:01

Platform

Not Applicable

File name

Amd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21921_none_5c598e6567c1d9c3.manifest

File version

Not Applicable

File size

35,995

Date (UTC)

11-Feb-2012

Time (UTC)

06:50

Platform

Not Applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21149_none_64ba14659f056887.manifest

File version

Not Applicable

File size

16,596

Date (UTC)

11-Feb-2012

Time (UTC)

05:52

Platform

Not Applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21921_none_66ae38b79c229bbe.manifest

File version

Not Applicable

File size

16,596

Date (UTC)

11-Feb-2012

Time (UTC)

05:42

Platform

Not Applicable

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

File name

Ia64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21149_none_fe487285b2453e52.manifest

File version

Not Applicable

File size

35,544

Date (UTC)

11-Feb-2012

Time (UTC)

06:52

Platform

Not Applicable

File name

Ia64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21921_none_003c96d7af627189.manifest

File version

Not Applicable

File size

35,992

Date (UTC)

11-Feb-2012

Time (UTC)

06:42

Platform

Not Applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21149_none_64ba14659f056887.manifest

File version

Not Applicable

File size

16,596

Date (UTC)

11-Feb-2012

Time (UTC)

05:52

Platform

Not Applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21921_none_66ae38b79c229bbe.manifest

File version

Not Applicable

File size

16,596

Date (UTC)

11-Feb-2012

Time (UTC)

05:42

Platform

Not Applicable

No comments:

Post a Comment

Search This Blog

Keyword position bid strategies not supported for Yahoo! Japan - Search Ads 360 Help [gg-searchads-en]

Create a specific type of bid strategy Keyword position bid strategies not supported for Yahoo! Japan Next: Target impression share with a ...