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 ForumsAuthenticationAuthenticationCould not access LDAP to obtain domains info. (ActiveDirectoryAuthentication)Could not access LDAP to obtain domains info. (ActiveDirectoryAuthentication)
Previous
 
Next
New Post
4/7/2010 10:51 AM
 
And have you tried using impersonation in your web.config? The AD provider isn't an LDAP provider but an ADSI provider but, as far as I know, it should still work.
 
New Post
7/21/2010 12:54 AM
 
Hello Mike,

Currently im configuring the AD authentication for DNN 5.4.4 trial version. FYI my company is using inhouse domain controller (.local). How do i configure this? all setting were set as you suggested including editing impersonate in webconfig but an error popped out.

Accessing Global Catalog:
FAIL
Checking Root Domain:
FAIL
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
The specified domain either does not exist or could not be contacted.

Is there other setting/configuration for local domain controller? FYI when i change key in dc=com it will popped another error

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 ---

Only when i changed it to dc=com.my it goes back to the 1st error mentioned. im stuck with this for weeks now, please help me . Thank you in advance

 

 
New Post
7/21/2010 1:31 PM
 
When your users log onto their computer what domain to they log onto? That's the domain you want to use in the provider settings.
 
New Post
7/22/2010 2:44 AM
 
Thank you Mike for replying, but I believed I had followed the instructions well.

root domain: dc=cyberview, dc=com.my

for username and password, I use an admin account for the domain.

username: cyberview\admin

this error still popped out

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.

Do advice. Thank you
 
New Post
7/22/2010 10:53 AM
 
Is the webserver on the domain or is it a stand-alone system? It's been my experience that the server has to be part of the domain though I think there are others that have gotten it to work on stand-alone systems. How, I'm not sure though.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationCould not access LDAP to obtain domains info. (ActiveDirectoryAuthentication)Could not access LDAP to obtain domains info. (ActiveDirectoryAuthentication)


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