<div>
What tool are you using to check from outside? You basically need to use ldaps when using 636.<br />
<br />
or use ldap explorer.<br />
<a href="http://ldaptool.sourceforge.net/" rel="ugc">http://ldaptool.sourceforge.net/</a>
</div>


What tool are you using to check from outside? You basically need to use ldaps when using 636.

or use ldap explorer.
http://ldaptool.sourceforge.net/ [http://ldaptool.sourceforge.net/]

<div>
It's a third party tool that has a built in LDAPS connectivity built in <br />
I just don't know if lack of having the certificate locally on the non domain computer would prevent any connection at all.
</div>


It's a third party tool that has a built in LDAPS connectivity built in
I just don't know if lack of having the certificate locally on the non domain computer would prevent any connection at all.

<div>
Yeah internally I can but users' externally cannot who are permitted via an IP block rule
</div>


Yeah internally I can but users' externally cannot who are permitted via an IP block rule

<div>
Yeah was firewall related, networking dept. had to fix it. <br />
Didn't think it'd be a complicated on the Windows side of things...
</div>


Yeah was firewall related, networking dept. had to fix it.
Didn't think it'd be a complicated on the Windows side of things...

<div>
<div class="content wysiwyg-content">
I have a domain controller with secure LDAP available on port 636<br />
<br />
However we have internal dns for our outside domain setup to be remoteDC.ourdomain.com<br />
that hostname is set to direct to the internal IP and is opened through external firewall to allow connection into the internal Domain Controller. <br />
<br />
Using LDP.exe internally I can connect to the remoteDC.ourdomain.com but externally cannot, even though firewall rules are there to allow.<br />
<br />
Would this have to do with any certificates or the remotedc.ourdomain.com not matching the internal domain controller called DC01?
</div>
</div>


I have a domain controller with secure LDAP available on port 636

However we have internal dns for our outside domain setup to be remoteDC.ourdomain.com
that hostname is set to direct to the internal IP and is opened through external firewall to allow connection into the internal Domain Controller. 

Using LDP.exe internally I can connect to the remoteDC.ourdomain.com but externally cannot, even though firewall rules are there to allow.

Would this have to do with any certificates or the remotedc.ourdomain.com not matching the internal domain controller called DC01?

External connection to Domain Controller - Secure LDAP 636

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

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.