Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD 5.0.2 not working afer UpdateAD 5.0.2 not working afer Update
Previous
 
Next
New Post
3/20/2010 5:12 AM
 

Hi,

I have some problems with AD 5.0.2 configuration. I just updated the DNN from 4.5.1 to 5.1.4 and I’ve installed AD 5.0.2. When I setup my AD i get the error:

Accessing Global Catalog: OK
Checking Root Domain: FAIL
Accessing LDAP: OK
Find all domains in network: 1 Domain(s): one.local (ONE)

and the settings i try to save are :

Enabled?: true

Hide Login Controls?: true

Authentication Type: Secure

Root Domain: one.local (or DC=one,DC=local)

User Name: ONE\user

Before the update those settings worked. Now if a user try to login and is not in the DNN users DB table will not login. I'm new at AD interface, the big problem is that i inherit the administration of this platform form someone how’s not available any more. And I had to do the update do to some business requirement.

 

Thank you

 
New Post
3/21/2010 2:01 PM
 
So the error form above is still showing, but ... i've setup in ISS on the WindowsSigning.aspx file i've checked only "Integrated Windows Authentication" and now sometimes a domain Windows login box popup and if i login with the windows account i get in the portal. Put if i try to log in with the same account in the portal login module it doesn't work. So i got some questions: 1. What is the normal procedure if i put enable on Hide Login Controls, DNN check standard auth info and windows or just the standard one? can i set it to use only AD? 2. What do i have to do to stop the widows login box showing up. 3. And what exactly does DNN when AD recognize the account did DNN copys the info in the Users table And it creates a profile?
 
New Post
3/22/2010 7:39 AM
 
1. One of your logon controls has to be visible. Personally, I disable the standard authentication on portals that don't need it, and make sure the AD login control is not hidden. If you have your domain set right in the menu, they can then log in with their AD account. 2. Two things: a: Make sure that IE has that website setup as either an Intranet or Trusted site. b: Make sure you put in the allowed IP ranges in the AD setup menu. 3. It is supposed to compare the password hash of the entered password against the associated AD account. If they are correct, it will update the associated local DNN account, or create one if it doesn't exist.
 
New Post
3/22/2010 11:21 AM
 
As for the error in your settings.... have you tried using impersonation in your web.config? What happens if you change the Authentication Type to Delegation? Hide Login Controls hides the DNN standard login. When you're trying to login are you entering DOMAIN\Username or just username? As far as the IIS generated Pop-up....Dan has answered that (putting the site in the Trusted or Intranet zones in IE). If your site is internal only then you don't have to worry about the IP address range.
 
New Post
3/23/2010 1:31 PM
 
The site is internal and external used. The only Authentication Type that gives me a working LDAP check is Secure. I've tried impersonation but i get the same result. AD won't work if i select Windows Login (using DOMAIN\user or user gets the same result). I found out that it might be an AD problem. The company has 5 AD databases (domains) and the server that hosts DNN has his own AD/DOMAIN (one2.local) but the users are in other domain/ad (one.local). So i think that my problem comes from there. Accessing Global Catalog: OK Checking Root Domain: FAIL Accessing LDAP: OK Find all domains in network: 1 Domain(s): one2.local (ONE2) What files do i need to modify so i can make the connection manually (or try)? Because after some digging i found out that before the update that was the trick done to make AD connection work. Thank you
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD 5.0.2 not working afer UpdateAD 5.0.2 not working afer Update


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out