<div>
Which is to say the ADDS will answer on port 389 (and also on another port for SSL, though I dont recall which) for LDAP queries.
</div>


Which is to say the ADDS will answer on port 389 (and also on another port for SSL, though I dont recall which) for LDAP queries.

<div>
Thank you very much for all of response. &nbsp;We did have slow authentication process. &nbsp;I think we will apply the hotfix. &nbsp; <br />
<br />
By the way, I try to telnet to the DC on port 389, but didn't get response. &nbsp;I am wondering if the port is open? &nbsp;Please advise.<br />
<br />
Thank you again.
</div>


Thank you very much for all of response.  We did have slow authentication process.  I think we will apply the hotfix.  

By the way, I try to telnet to the DC on port 389, but didn't get response.  I am wondering if the port is open?  Please advise.

Thank you again.

<div>
<div class="content wysiwyg-content">
Hi Experts,<br />
<br />
I am trying to locate my ldap server on Windows network. &nbsp;The server was setup by a consultant. &nbsp;I know the port 389 has been open on firewall to one of our Windows domain controller (W2012r2). &nbsp;But when I login the DC, I could not find any ldap service on the DC. &nbsp;So I don't know what consultant setup on the server for ldap. &nbsp; How can we find out our ldap or what the consultant installed on the DC to have it functioning as ldap?<br />
<br />
Thank you very much for your help in advance.<br />
<br />
EN
</div>
</div>


Hi Experts,

I am trying to locate my ldap server on Windows network.  The server was setup by a consultant.  I know the port 389 has been open on firewall to one of our Windows domain controller (W2012r2).  But when I login the DC, I could not find any ldap service on the DC.  So I don't know what consultant setup on the server for ldap.   How can we find out our ldap or what the consultant installed on the DC to have it functioning as ldap?

Thank you very much for your help in advance.

EN

LDAP on Windows server

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.