TornadoV,
I will give this a try and let you know.
Thanks!
Main Topics
Browse All TopicsI am trying to utilize the ActiveDirectoryMembershipP
The server running the ASP.NET site is in the DMZ with port 389 open. I can test that the port is open and that the Web Server can access the Domain Server. The code I have written to test this creates a DirectoryEntry using the same connection info as below. Also, I am able to test this connection with Ldp.exe and everything checks out.
Attatched is what I have in my web.config file. I set the ADService Connection String to the Domain server behind the firewall using port 389, which is open. Then in my provider is set the connectionProtection to "none" to force the provider to use port 389. However, when I try to use the built in login server control I get the error noted above. This site works internally on a server in the LAN, so I am confused as to why it will not function. I am sure that I completely overlooked something, so any suggestions are appreciated.
Thanks,
Chris
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.
I was able to get port 3268 open for the Global catalog, so now both 389 and 3268 are open. I am still however getting the same error when I try to use the ActiveDirectoryMembershipP
I noticed that you're using connectionProtection="None
"When the connectionProtection is set to "None", you can not connect to the ADAM Directory with a Windows Account; therefore, you must create a User Object in the ADAM instance and add it as a member of the Administrator role. "
There is another important part:
"However, you will still have problems connecting to ADAM with ASP.Net Membership API for two reasons. First, you need to configure ADAM to support unsecured bind operation since by default ADAM only support a secure connection such as SSL, and second ADAM does allow passwords to be send over an unsecured connection. In the ADAM ADSI Edit, go to the Configuration naming context and choose the properties for CN=Directory Services, CN=Windows NT, CN=Services. Double click the attributes "msDS-Other-Settings" and click edit and remove the entry "RequireSecureProxyBind=1"
At the command prompt, type: dsmgmt
At the dsmgmt: prompt, type: ds behavior
At the ds behavior: prompt, type: connections
· At the server connections: prompt, type:
connect to server localhost:389
At the server connections: prompt, type: quit
At the ds behavior: prompt, do the following:
To allow password settings over a non-SSL connection, type:
allow passwd op on unsecured connection
"
Hope this helps.
We've used ADAM for our implementation, this might be usefull: http://forums.iis.net/t/10
Also, http://saloweblife.blogspo
Q connectionProtection=None for ADThis is not a combination you should ever use. In AD environments, any operations that set or change passwords must be done over secure connections, so with a setting of None, the provider will always fail when it attempts things like ChangePassword or ResetPassword. Also, you need to always use explicit connection credentials with this setting. Because AD has built-in support for automatically securing connections there isnt much reason for ever using None in an AD environment.
Here is list of ports that we have open between ADAM in DMZ and internal AD DC:
389, 636, 3268, 3269 and 135 (RPC Endpoint Mapper - used for replication between ADAM and AD)
Hope this helps
Thanks TornadoV,
Originally I was just trying this as a demo, but it looks like this might be the way we implement the project, so I am thinking that using ADAM and secure connections will be our best bet.
I am going to do some research on setting up ADAM...So I will probably be back.
Thanks for all your help,
Business Accounts
Answer for Membership
by: TornadoVPosted on 2008-05-06 at 08:21:18ID: 21508077
You will need to open up port 3268 to query the global catalog, if you will use SSL/LDAP, you need 636 and 3269 respectively.