Microsoft KB Archive/825107

= The Lsass.exe process may stop responding if you have many external trusts on a Windows 2000 Server-based domain controller =

Article ID: 825107

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
If you have many external trusts and many simultaneous logons where the domain is not specified on a Microsoft Windows 2000 Server-based domain controller, the Local Security Authentication Server (Lsass.exe) process may stop responding.

Note This problem does not apply to any logons where the domain is specified.



CAUSE
This problem occurs because the Lsass.exe process runs out of resources if the number of simultaneous logons multiplied by the number of trusts is more than 1,000.

This problem typically will not occur. This problem may require hundreds of trusts and dozens of users who attempt simultaneous logons. For example, if the domain controller has 75 external trusts or downlevel trusts and the domain controller experiences 25 simultaneous logons where no domain specified, the number of logons multiplied by the number of trusts is 1,875 (25 logons x 75 trusts = 1,875). In this example, the Lsass.exe process would not be able to allocate enough resources to authenticate the client logon requests.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
No prerequisites are required.

Restart requirement
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Hotfix installation instructions
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

After you install this hotfix, you must create a new registry subkey to enable the hotfix. After you enable the hotfix, the domain controller will no longer try to authenticate a domainless logon by querying external trusts.

Important This new behavior may cause unwanted side effects if you have clients that do not send domain names with their logon requests. Such clients may include Microsoft Windows 98 clients and Microsoft Outlook Web Access. These programs will still work if the user account is in the Windows 2000 Server domain or in the global catalog. You should only experience problems if a user account is in an external domain.

To create the new registry subkey to enable the hotfix, follow these steps:
 * 1) Click Start, click Run, type regedit, and then click OK.
 * 2) Locate the following registry subkey:.
 * 3) Right-click this subkey, point to New, click DWORD Value, type NeverPing, and then press ENTER.
 * 4) Right-click NeverPing, click Modify, type 1 in the Value data box, and then click OK.
 * 5) Exit Registry Editor.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages

For more information, 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

Keywords: kbbug kbfix kbwin2000presp5fix kbqfe kbpubtypekc KB825107

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.