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 protocol failed with error 10048. If port number 389 is used by another application, change to an unused port, then shut down and restart Microsoft Exchange Directory Services. Contact Microsoft Support Service if condition persists.
|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?
What is a directory service?
As per Microsoft: "This behavior occurs because Windows 2000 Active Directory and Exchange Server 5.5 both use Lightweight Directory Access Protocol (LDAP) port 389 by default". See ME251196, ME241695 and ME260692 for details on fixing this issue.
See EventID 17 from source MSExchangeDS for additional information on this issue.
How to Change LDAP Port Assignments in Exchange Server (ME224447) is also useful.
We found that this event occurs when there is an attempt to run ILS services on Exchange servers. The conflict occurs because both applications are trying to use TCP port 389
|Private comment: Subscribers only. See example of private comment|
|Links: ME176169, ME224447, ME241695, ME241865, ME251196, ME260692, EventID 17 from source MSExchangeDS|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated