Symptoms
Consider the following scenario:
-
You have Windows Server 2008 R2-based domain controllers in a Windows Server 2008 R2-based domain environment.
-
You set a specific static port to be used for NT Directory Service (NTDS) and Netlogon on a domain controller. To do this, you follow the method that is described in following Microsoft Knowledge Base (KB) article:Â
224196 Restricting Active Directory replication traffic and client RPC traffic to a specific port
-
You configure a perimeter network (also known as DMZ, demilitarized zone, and screened subnet) to enable network traffic on the specific static port.
-
You try to log on to the domain controller.
In this scenario, the logon procedure for the domain controller takes longer than expected. Additionally, some services that depend on the Netlogon service may be disrupted.Also, you can see the following RPC extended error information reported in the netlogon.log file:[CRITICAL] [22508] NlPrintRpcDebug: Dumping extended error for I_NetServerReqChallenge with 0xc0020017[CRITICAL] [22508] [0] ProcessID is 948[CRITICAL] [22508] [0] System Time is: 10/7/2014 17:9:8:786[CRITICAL] [22508] [0] Generating component is 18[CRITICAL] [22508] [0] Status is 1722[CRITICAL] [22508] [0] Detection location is 1442[CRITICAL] [22508] [0] Flags is 0[CRITICAL] [22508] [0] NumberOfParameters is 1[CRITICAL] [22508] Unicode string: dc1.contoso.com[CRITICAL] [22508] [1] ProcessID is 948[CRITICAL] [22508] [1] System Time is: 10/7/2014 17:9:8:786[CRITICAL] [22508] [1] Generating component is 18[CRITICAL] [22508] [1] Status is 1722[CRITICAL] [22508] [1] Detection location is 323[CRITICAL] [22508] [1] Flags is 0[CRITICAL] [22508] [1] NumberOfParameters is 0[CRITICAL] [22508] [2] ProcessID is 948[CRITICAL] [22508] [2] System Time is: 10/7/2014 17:9:8:786[CRITICAL] [22508] [2] Generating component is 18[CRITICAL] [22508] [2] Status is 1237[CRITICAL] [22508] [2] Detection location is 313[CRITICAL] [22508] [2] Flags is 0[CRITICAL] [22508] [2] NumberOfParameters is 0[CRITICAL] [22508] [3] ProcessID is 948[CRITICAL] [22508] [3] System Time is: 10/7/2014 17:9:8:786[CRITICAL] [22508] [3] Generating component is 18[CRITICAL] [22508] [3] Status is 10060 The RPC error is 1722 (RPC_S_SERVER_UNAVAILABLE), and the Sockets error is 10060 (WSAETIMEDOUT). These errors indicate that the server could not be reached and that it did not respond in time.In the following network trace, you notice that the port tried by the client together with the TCP SYN requests does not receive a response. Therefore, the server does not respond on this port.10.1.1.70 57565 (0xE0DD) 10.1.1.140 135 (0x87) EPM EPM:Request: ept_map: NDR, Netlogon(NRPC) {12345678-1234-ABCD-EF00-01234567CFFB} v1.010.1.1.140 135 (0x87) 10.1.1.70 57565 (0xE0DD) EPM EPM:Response: ept_map: NDR, Netlogon(NRPC) {12345678-1234-ABCD-EF00-01234567CFFB} v1.0Tower: NDR, Netlogon(NRPC) {12345678-1234-ABCD-EF00-01234567CFFB} v1.0, RPC v5, 10.1.1.140:2645 (0xA55) [2645]Tower: NDR, Netlogon(NRPC) {12345678-1234-ABCD-EF00-01234567CFFB} v1.0, RPC v510.92.24.141, 10.1.1.140:49150 (0xBFFE) [49150]Tower: NDR, Netlogon(NRPC) {12345678-1234-ABCD-EF00-01234567CFFB} v1.0, RPC v510.92.24.141, 10.1.1.140:1028 (0x404) [1028] Note The client picks the first port (in this case, it is 2645) and that port is not open on the firewall.When you have update 2654097 installed in Windows Server 2008 R2 or you are using Windows Server 2012 or a later version, domain members and domain controllers that are talking to a domain controller that is affected by this problem will log events 5816 and 5817 when it occurs.
Cause
This issue occurs because there is no synchronization between endpoint registrations on the domain controller. The endpoint registrations are performed by different services or threads that are hosted by the Lsass.exe process.For example, the following services are hosted by the Lsass.exe process:
-
Lsarpc
-
Samr
-
Drsuapi
-
Netlogon
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 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:
976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this hotfix, 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.
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
Milestone
Service branch
6.1.760 1.22xxx
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 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 x64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Netlogon.dll |
6.1.7601.22289 |
699,904 |
01-Apr-2013 |
07:33 |
x64 |
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.7601.22289 |
1,158,144 |
01-Apr-2013 |
04:23 |
IA-64 |
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:
824684Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
|
File name |
Amd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.22289_none_5c208d1b67eb79b1.manifest |
|
File version |
Not applicable |
|
File size |
35,995 |
|
Date (UTC) |
01-Apr-2013 |
|
Time (UTC) |
08:04 |
|
Platform |
Not applicable |
|
File name |
Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.22289_none_6675376d9c4c3bac.manifest |
|
File version |
Not applicable |
|
File size |
16,596 |
|
Date (UTC) |
01-Apr-2013 |
|
Time (UTC) |
04:44 |
|
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.7601.22289_none_0003958daf8c1177.manifest |
|
File version |
Not applicable |
|
File size |
35,992 |
|
Date (UTC) |
01-Apr-2013 |
|
Time (UTC) |
04:52 |
|
Platform |
Not applicable |
|
File name |
Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.22289_none_6675376d9c4c3bac.manifest |
|
File version |
Not applicable |
|
File size |
16,596 |
|
Date (UTC) |
01-Apr-2013 |
|
Time (UTC) |
04:44 |
|
Platform |
Not applicable |
