Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1309 Source: MSExchangeDS

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

Windows Event Log Analysis Splunk App

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



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.