Comments are available to members only. Sign up or Log in to view these comments.
Main Topics
Browse All TopicsHere's the situation: We have a vendor, hosted outside of our local network, that we want people at our company to be able to authenticate to using our internal LDAP. We don't have an Active Directory, or other LDAP server in our DMZ capable of connecting to their servers. All of our AD servers reside in our internal network.
Here's what we did: we made it so one of our Active Directory servers is accessible from the outside on port 636, but ONLY to the public IP addresses being used by the vendor. That part in itself is working fine (a telnet connection to the public IP on port 636 is successful). The server (names changed for this example obviously) is a member of a local AD domain, and the name on the network is "server1.inside.local" (internal.local is our internal domain). Obviously the vendor won't be able to resolve to that. So, we bought a certificate for "server1.outside.edu" (our outside domain), applied it to the server, and added some DNS entries so our network knows to send requests for both "server1.inside.local" as well as "server1.outside.edu" to this same box.
The problem we're having: the LDAP communications need to be secure. We bought a certificate for "server1.outside.edu" and applied it to the server. As far as I can tell, the cert is installed correctly, as is the intermediate CA for the cert. However, using Microsoft's ldp.exe utility, I can't connect to the server on port 636 at "server1.outside.edu." I can only connect to the internal DNS name, "server1.internal.local." Even locally&for now, forget that ultimately we want an outside vendor to connect. I can't even connect with ldp.exe using the public name when I'm on a computer that's inside of our network -- nothing in between the server and the desktop but a switch, no firewall. I've spent hours on this, tried everything I could think of. I went through these instructions from Microsoft..no luck: http://support.microsoft.c
So to sum up:
Server's local name: server1.internal.local
Server's outside name (applied by DNS entry): server1.outside.edu
Certificate for server1.outside.edu is applied to the server, but can't make a secure LDAP connection to the server using that name.
Hopefully I explained this clearly but if anything doesn't make sense, let me know.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: ArenarPosted on 2009-10-15 at 03:38:07ID: 25579122
Comments are available to members only. Sign up or Log in to view these comments.