This article was previously published under Q246717
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
You may find multiple instances of the following entry in the Directory Services event log:
Event Type: Warning Event Source: NTDS LDAP Event Category: LDAP Interface Event ID: 1216 Date: 11/19/2000 Time: 9:12:58 PM User: N/A Computer: Computer Description: The LDAP server closed a socket to a client because of an error condition, 1234. (Internal ID c01028c::4294967295).
Note that the Internal ID value varies with each instance.
This event log message occurs when a Lightweight Directory Access Protocol (LDAP) client sends a request to the computer by using User Datagram Protocol (UDP) but does not keep its socket open to listen for the response from the server. When the server tries to send the answer back, the error message is logged to the event log. This is a harmless error that can occur frequently under normal operating conditions. It occurs only if the diagnostic logging level is increased by modifying the level of LDAP logging to 2 or above in the registry.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this issue:
Start Registry Editor (Regedt32.exe).
Locate the LDAP Interface Events value in the following registry key: