Long logon time after you set a specific static port for NTDS and Netlogon in a Windows Server 2008 R2-based domain environment

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.0
10.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.0
Tower: 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.