Lost secure channel takes a long time to be reestablished when RPC Endpoint Mapper is secured on Windows Server 2012 domain controllers

Applies to: Windows Server 2012 FoundationWindows Server 2012 FoundationWindows Server 2012 Standard


Consider the following scenario:

  • You have multiple domains in one or more forests that have Windows Server 2012 domain controllers.
  • You have at least one direct trust relationship between the domains.
  • On domain controllers, you set the value of the RestrictRemoteClients registry key to 2 and the value of the EnableAuthEpResolution registry key to 1. These two registry key settings help secure RPC Endpoint Mapper.
  • The secure channel between the domains is lost when you perform cross-domain NT LAN Manager (NTLM) authentication.
In this situation, there is a long delay before the secure channel is reestablished. You may also receive unexpected credential prompts and the following Error event:  

Log Name: System
Event ID: 5816
Level: Error
Netlogon has failed an authentication request of account username in domain user domain FQDN. The request timed out before it could be sent to domain controller directly trusted domain controller FQDN in domain directly trusted domain name. This is the first failure. If the problem continues, consolidated events will be logged about every event log frequency in minutes. Please see http://support.microsoft.com/kb/2654097 for more information.


This issue occurs because the Netlogon secure channel is a special case for RPC Endpoint Mapper. It can be used to authenticate RPC Endpoint Mapper itself. In some cases, the Netlogon secure channel is not honored, and this causes a deadlock that takes time to resolve. 


This hotfix is also available at Microsoft Update Catalog.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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: Note 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.

Note We suggest that you apply this hotfix to all Windows Server 2012-based domain controllers in your environment.


To apply this hotfix, you must be running Windows Server 2012.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You might need to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.


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