	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.8

Accessing Active Directory LDAP with SSL connection over the Internet

Asked by mgudites1 in Lightweight Directory Access Protocol (LDAP), Active Directory

Tags: active directory ldap ldaps ssl

Here'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.com/kb/321051 I'm not sure what else to do. How do I make this work, or should I be approaching this in another way?

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.

View the Solution FREE for 30 Days

20100215-EE-VQP-121 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. bluntTony21,200
2. Chris-Dent20,068
3. jwilleke16,314
4. noci9,800
5. mkline716,968
6. Paranorm...6,000
7. xxdcmast5,300
8. keith_ala...4,800
9. premglitz4,500
10. sedgwick4,000
10. Awinish4,000
12. pwust3,500
13. ZJORZ3,200
14. johnb67673,000
14. CodeCruiser3,000
16. shalomc2,800
16. Nopius2,800
18. Tolomir2,750
19. profya2,500
19. Pber2,500
19. ARK-DS2,500
22. Akhater2,000
22. RobWill2,000
22. snusgubben2,000
22. Shift-32,000
22. ukznmcl2,000
22. mikebernh...2,000
22. naldiian2,000
22. Americom2,000
22. tl1210002,000
22. it4soho2,000
22. chandru_...2,000
22. steelseth122,000
22. IceCode2,000
22. dstewartjr2,000
22. cmcawood2,000
22. grantsew...2,000
22. tgerbert2,000
22. wdurrett2,000
22. marcokre...2,000
22. djohn112,000
22. Krys_K2,000
22. Roads_R...2,000
22. lucius_the2,000
22. x-men2,000
22. leakim9712,000
22. R3C0N2,000
22. Arenar2,000
22. farazhkhan2,000
22. KingR2,000
22. kalmax2,000
22. PFoeckeler2,000
22. Krokky2,000
22. fernando...2,000
22. shabhi2,000
22. Maverick...2,000

1. Chris-Dent265,562
2. bluntTony106,168
3. mkline7160,818
4. RobSamp...38,350
5. Nopius24,150
6. henjoh0923,745
7. LauraEHu...23,050
8. Krys_K21,700
9. xxdcmast19,250
10. Shift-318,950
11. noci17,532
12. tedbilly17,325
13. exx197616,668
14. it4soho16,375
15. jwilleke16,314
16. Paranorm...15,500
17. tigermatt14,322
18. Americom13,875
19. Mestha13,525
20. oBdA13,318
21. sirbounty11,035
22. toniur10,300
23. snusgubben10,164
24. gupnit9,680
25. rindi9,500

Accessing Active Directory LDAP with SSL connection over the Internet

Asked by mgudites1 in Lightweight Directory Access Protocol (LDAP), Active Directory

Tags: active directory ldap ldaps ssl

About this solution