Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Register LDAP SSL Protocol failed with error 10048. The LDAP SSL server is not available. Make sure port number 636 is not used by another application.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange Directory service?
What is LDAP?
Related to event 1306 from MSExchangeDS, this event can occur independent of 1306 or in conjunction. This is a known bug on a Windows 2000 Server running MS Exchange 5.0 or 5.5. As per ME224447: "Windows 2000 uses its own LDAP Server service which initializes prior to Exchange Server's LDAP Server service. This service uses Ports 389 and 636. When Exchange Server starts, the Exchange Directory attempts to initialize the same ports (for Secure Sockets Layer connectivity)."
As per ME232606: "This issue occurs when Exchange Server is running on a system that already has a Directory service using this port and when Exchange Server is installed on a Windows 2000 domain controller." See the Q article on how to change the port used by the Exchange Server LDAP SSL service for listening.
The ME241865 article describes that this error can occur on MS BackOffice server that has the Internet Locator service (ILS) installed. The article points to ME176169 for information about how to configure Exchange to use a different port, allowing the ILS to use TCP port 389.
|Private comment: Subscribers only. See example of private comment|
|Links: ME224447, ME232606, ME241865, ME176169, ME214864|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated