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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN & ADDNN & AD
Previous
 
Next
New Post
1/22/2007 11:07 AM
 

Hi:

I'm a newbie to customizing DNN, I have choosen DNN to use as our companies Intranet but am running into issues configuring dnn 4.3.7 to use windows authentication. I see a lot of posts on this but can't seem to find the information I need. I have purchased dnnMasters User import tool and can import all users from AD to DNN but when I try to use the built-in tool to port users and roles into dnn I have no success. Can someone point me to a step by step on how to accomplish this? As you can see from the picture below everystep fails and I don't know why. Any help would be greatly appreciated.

Well nevermind the pic it will not let me upload it, anyway here are the settings I'm using.

 

Accessing Global catalog: Fail

Checking Root Domain: Fail

Accessing LDAP: Fail

Find All Domains in Network: Could not access LDAP to obtain domains info

Login Failure: unknown user name or bad password.

Windows Authentication: Checked

Syncronize Role: Checked

Provider: ADSIAuthentication Provider

Authentication Type: Delegation

Root Domain: ldap://c-p.com also tried c-p.com & DC=c-p, DC=com

User Name: Administrator

Password: is correct despite the error above

Email Domain: @c-p.com

You can email me directly @ ciscor@c-p.com or respond to this post.

Thanks,

Cisco

 

 

 
New Post
1/22/2007 1:43 PM
 

Root domain should be dc=c-p,dc=com
Username: c-p.com\Administrator or Administrator@c-p.com

Just for the record I personally wouldn't use your domain administrator account but rather a dummy domain account or even your own username/password for testing purposes.

EDIT: Oh and you don't import your AD users into your DNN database. That's taken care of automatically was each AD user logs into the site.

 
New Post
1/22/2007 2:52 PM
 

The reason I posted the ability to import from ad to dnn using the import tool was to show that I don't have any connectivity issues getting to AD and the import tool was used on a different dnn site.

I am using admin because I can't seem to get it to work any other way and this was a way for me to rule out any permission issues. I have started over from scratch with a vanilla site but, if I specify my root domain as dc=c-p,dc=com I get the following:

Error: Windows Authentication is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Security.Authentication.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootEntry() at DotNetNuke.Security.Authentication.ADSIProvider.GetNetworkStatus() at DotNetNuke.Security.Authentication.AuthenticationController.NetworkStatus() at DotNetNuke.Modules.Authentication.AuthenticationSettings.cmdAuthenticationUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

 
New Post
1/22/2007 11:16 PM
 

I've only seen that error when I've left the domain blank (which doesn't happen to all users). If you restart the site (under Host Settings) and go back to the Authentication tab is it remembering the root domain?

Another thing you could try to is to user impersonation in your web.config. Around line 110 of your web.config you'll see a commented out section with <identity impersonate = "true" />. Just uncomment that line and add, I think, userName="domain\username" password="password". I'm guessing on the syntax as the install that uses impersonation is at work and I'm at home. You'll also have to give this user the same rights to your DNN install as Network Service has.

 
New Post
1/23/2007 9:41 AM
 
That worked for my local test but not for the one I need it too, the server I actually need to function currently sits on our DMZ, although it will not live there permanently I will need to here for testing purposes and I need AD sync to function. It seems to save all settings in the suthentication module but throws that exception (from previous post) when trying to contact AD, I assume there is still an issue with dnn, as opposed to a transport issue because I would expect to see a different error. Any other ideas?
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN & ADDNN & AD


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