Symptoms

Consider the following scenario:

  • You have one or more forests that have multiple domains.

  • There are combinations of users and resources (such as applications or proxy servers) in different domains.

  • There are lots of NTLM logon requests from the remote domain users to a resource server that is running Windows Server 2008 Service Pack 2 (SP2).

In this scenario, the NTLM requests time out. For example, Microsoft Exchange clients do not authenticate to the Exchange server when this issue occurs. Therefore, users cannot access their mailboxes, and Microsoft Outlook seems to freeze. 

Cause

This issue occurs because the NTLM API throttling limit is reached.

Resolution

Hotfix information

After you install this hotfix, the following new events are logged to track NTLM authentication delays and failures:After you install the hotfix, the EventLogPeriodicity and WarningEventThreshold registry entries can be set under the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\ParametersThe two new registry entries have the following values:

  • Name: EventLogPeriodicity
    Type: REG_DWORD
    Data: Interval in seconds for the frequency of event 5817 and 5819.
    Default: 1800 (30 minutes)
    Minimum: 300 (5 minutes)
    Maximum: 86400 (1 day)

    Note By default, after you install the hotfix, event 5816 is logged when an initial failure occurs, and event 5817 is logged every 30 minutes when later failures occur.

  • Name: WarningEventThreshold
    Type: REG_DWORD
    Data: 0 to 45
    Default: 0 (no warnings)
    Minimum: 1
    Maximum: 45

    Note When a request waits for a Netlogon API call slot for more than this number of seconds, event 5818 or event 5819 is logged. The maximum value of the registry entry is 45. After 45 seconds, the request times out and is tracked by using event 5816 and event 5817.

When you set the WarningEventThreshold registry entry, use a value that suits the importance of NTLM authentication performance in your environment. We recommend that you start with a value of five seconds.

The following details describe how these events are logged:

  • Each outgoing Netlogon security channel is tracked independently.

  • A monitoring thread checks whether any secure channels require an event to be logged.

  • When the first error or warning condition is met, event 5816 or event 5818 is logged. Additionally, the affected security channel is flagged for monitoring by the thread that was mentioned earlier.

  • If an initial event is logged, only the instance counter is incremented when additional failures occur.

  • The next time that the thread starts, event 5817 or event 5819 is logged if there were any instances during the last monitoring interval.

  • If no problem or delay occurred during the last monitoring interval, event 5817 or event 5819 is not logged, and the security channel is no longer monitored.

  • When the security channel detects this issue again, a new event 5816 or new event 5818 is logged, and the security channel enters the monitoring status again.

When the domain controller for a trusted domain changes and there are errors or delays, event 5816 or event 5818 is logged. Therefore, the new trusted domain controller name is tracked, and a new monitoring cycle begins. The change of domain controller may be related to previous events that were logged.

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

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849How to obtain the latest service pack for Windows Server 2008

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 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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

    SR_Level

    Service branch

    6.0.600
    2.
    23xxx

    Windows Server 2008

    SP2

    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" section. MUM files 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 Server 2008

File property

Value

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Bootfix.bin

File version

Not applicable

File size

1,024

Date (UTC)

29-May-2013

Time (UTC)

13:31

Platform

Not applicable

File name

Netlogon.dll

File version

6.0.6002.23179

File size

596,992

Date (UTC)

29-Jul-2013

Time (UTC)

09:05

Platform

x86

File name

Nlsvc.mof

File version

Not applicable

File size

2,873

Date (UTC)

09-Sep-2011

Time (UTC)

11:38

Platform

Not applicable

For all supported x64-based versions of Windows Server 2008

File property

Value

File name

Netlogon.dll

File version

6.0.6002.23179

File size

720,896

Date (UTC)

29-Jul-2013

Time (UTC)

09:43

Platform

x64

File name

Nlsvc.mof

File version

Not applicable

File size

2,873

Date (UTC)

15-Nov-2011

Time (UTC)

15:16

Platform

Not applicable

File name

Netlogon.dll

File version

6.0.6002.23179

File size

596,992

Date (UTC)

29-Jul-2013

Time (UTC)

09:05

Platform

x86

File name

Nlsvc.mof

File version

Not applicable

File size

2,873

Date (UTC)

09-Sep-2011

Time (UTC)

11:38

Platform

Not applicable

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

File property

Value

File name

Netlogon.dll

File version

6.0.6002.23179

File size

1,223,680

Date (UTC)

29-Jul-2013

Time (UTC)

21:11

Platform

IA-64

File name

Nlsvc.mof

File version

Not applicable

File size

2,873

Date (UTC)

15-Mar-2011

Time (UTC)

05:46

Platform

Not applicable

File name

Netlogon.dll

File version

6.0.6002.23179

File size

596,992

Date (UTC)

29-Jul-2013

Time (UTC)

09:05

Platform

x86

File name

Nlsvc.mof

File version

Not applicable

File size

2,873

Date (UTC)

09-Sep-2011

Time (UTC)

11:38

Platform

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 this issue, 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
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

Additional files for all supported x86-based versions of Windows Server 2008

File property

Value

File name

X86_microsoft-windows-security-netlogon_31bf3856ad364e35_6.0.6002.23179_none_ffe508064e6e9601.manifest

File version

Not applicable

File size

23,149

Date (UTC)

29-Jul-2013

Time (UTC)

09:46

Platform

Not applicable

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

File property

Value

File name

Amd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.0.6002.23179_none_5c03a38a06cc0737.manifest

File version

Not applicable

File size

23,628

Date (UTC)

29-Jul-2013

Time (UTC)

10:34

Platform

Not applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.0.6002.23179_none_66584ddc3b2cc932.manifest

File version

Not applicable

File size

18,780

Date (UTC)

29-Jul-2013

Time (UTC)

09:41

Platform

Not applicable

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

File property

Value

File name

Ia64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.0.6002.23179_none_ffe6abfc4e6c9efd.manifest

File version

Not applicable

File size

23,604

Date (UTC)

29-Jul-2013

Time (UTC)

22:08

Platform

Not applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.0.6002.23179_none_66584ddc3b2cc932.manifest

File version

Not applicable

File size

18,780

Date (UTC)

29-Jul-2013

Time (UTC)

09:41

Platform

Not applicable



Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×