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 Configuration issueAD Configuration issue
Previous
 
Next
New Post
11/17/2010 9:52 AM
 
We have had a corporate website hosted on a computer within the local network. AD authentication has been working just fine with these parameters:

Root Domain:   dc=INTRANET
Default Domain: INTRANET

We moved the website to a hosted site outside of the internal corporate network.  AD Authentication is now failing with the same settings.  If I go to the site and just update settings, I get this:

Error: 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.Authentication.ActiveDirectory.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetNetworkStatus() at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.NetworkStatus() at DotNetNuke.Authentication.ActiveDirectory.Settings.UpdateSettings() --- End of inner exception stack trace ---

---------------
So, I changed the settings (having looked at the documentation) to:

Root Domain:   dc=INTRANET.mycompany, dc=com
Default Domain: INTRANET

Now I don't get an exception, but I do get another error:

Error Accessing Global Catalog:
FAIL
Checking Root Domain:
FAIL
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
Logon failure: unknown user name or bad password.


Where should I go from here?



Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
New Post
11/17/2010 11:18 AM
 
Looks to me like the server can't talk to the Active Directory. Is this server on the domain but just out in the DMZ or is it just a stand alone server?
 
New Post
12/16/2010 2:32 PM
 
I am still struggling with this and have not been able to resolve the problem.

To recap, we moved our corporate website to an external host, but we still want our internal users to be able to login to the site using their AD credentials.

The site is mycompany.com.  This is external and outside of our firewall.  It is running DNN 5.5.1 and AD Provider 5.0.2.

Our AD domain is intranet.mycompany.com.

I have specified the Root Domain as "dc=intranet.audaciousinquiry,dc=com"

This results in the following string of errors when I try to update AD settings:

Accessing Global Catalog:
FAIL
Checking Root Domain:
FAIL
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
Logon failure: unknown user name or bad password.

---------
To make sure that I could configure AD inside of my firewall, I installed a local version of DotNetNuke (5.6.0) and configured AD with Root Domain set to "dc=intranet,dc=local" and all of the other parameters the same as I configured the web site.  With these settings, I am able to authenticate with AD on the local installation.

---------
In all honesty, I'd flying a little blind here.  I understand that the external website says that it cannot find the LDAP server.  We have opened up the firewall so that all requests from the IP of the website are passed through.

I'd appreciate any ideas on how I might try to debug this.

Thanks!



Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
New Post
12/16/2010 3:36 PM
 
You don't mention whether the server is still part of the domain or not. It's been my experience that it needs to or the AD ignores requests. I've never had to fix a problem such as you're having so it's hard to say what needs to be done. The only thing that comes to mind other than having network analyzing software running to see where it dies is to try LDAP browser (http://ldapbrowser.com) on the server and seeing if it can talk to the AD.
 
New Post
12/16/2010 3:58 PM
 
Yes, the website is part of the mycompany.com website. Thanks, though, for the suggestion to use LDAP Browser. I'll see if the hosting company can support that.



Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD Configuration issueAD Configuration issue


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