Article ID: 2668820 - View products that this article applies to.
After upgrading your DCs to Windows Server 2008 or Windows Server 2008 R2 you may be affected by this issue. Possible symptoms are logon delays, Outlook and other application hangs, increasing Exchange queue.
A more obvious indicator is Event Warning Netlogon 5807 on the slow responding DC with a very high number of clients, like the following:
Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5807
During the past 4.23 hours there have been 123450 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined sites and may connect to any Domain Controller including those that are in far distant locations from the clients. A client's site is determined by the mapping of its subnet to one of the existing sites. To move the above clients to one of the sites, please consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites. The names and IP addresses of the clients in question have been logged on this computer in the following log file '%SystemRoot%\debug\netlogon.log' and, potentially, in the log file '%SystemRoot%\debug\netlogon.bak' created if the former log becomes full. The log(s) may contain additional unrelated debugging information. To filter out the needed information, please search for lines which contain text 'NO_CLIENT_SITE:'. The first word after this string is the client name and the second word is the client IP address. The maximum size of the log(s) is controlled by the following registry DWORD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize'; the default is 20000000 bytes. The current maximum size is 20000000 bytes. To set a different maximum size, create the above registry value and set the desired maximum size in bytes.
With Windows Server 2008 a new default behavior was introduced. For site-unmapped Client IPs a DC performs name resolution, because since Vista and the introduction of IPv6 a client may have multiple IPs. The IP address the client uses during the LDAP UDP Netlogon ping to contact the DC may not be the only one available. If the Windows 2008 DC has no subnet configured for this IP it tries finding a different one having a mapping and would return the according Sitename to the client.
Depending on the Name Resolution mechanism configured on the DC this name resolution may take some seconds. During this time the LDAP Ping request holds an ATQ Thread from a limited ATQ pool. A very high number of such site-unmapped LDAP Pings may saturate this Pool. Since other LDAP and Kerberos request also need this pool they may be affected as well.
The typical setup when stepping into this issue is a Client- with a trusting Resource Forest, where the Client IP Segments have no Subnet/Site match in the Resource Forest. The Resource Forest DCs may log Event Warning Netlogon 5807 with a very high number of clients.
The behavior is by design and cannot be deactivated. You may apply the following alternatives as resolution:
-create matching subnet/sites, avoid Netlogon 5807 with a high number of unmapped connections
-increase MaxPoolThreads to 10 (counts per core)
Ref. “315071 How to view and set LDAP policy in Active Directory by using Ntdsutil.exe”, http://support.microsoft.com/default.aspx?scid=kb;EN-US;315071
-optimize DC Name resolution, disable Netbios or use P-Node when WINS is required
Ref. “Chapter 11 - NetBIOS over TCP/IP - Microsoft TechNet: Resources”, http://technet.microsoft.com/en-us/library/bb727013.aspx
Similar issue: http://blogs.msdn.com/b/spatdsg/archive/2011/06/24/dc-fails-logons-or-experiences-ldap-timeouts.aspx
ATQ (Active Thread Queue) Performance Counter monitoring:
“Monitoring Your Branch Office Environment”, http://technet.microsoft.com/en-us/library/dd736504(WS.10).aspx
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.