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 provider configuration errorsAD provider configuration errors
Previous
 
Next
New Post
5/19/2009 6:19 PM
 

Hi,

I'm getting two errors when I try to configure the AD provide 01.00.05 under DNN 04.09.03. 

Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Access is denied. ---> System.Runtime.InteropServices.COMException (0x80070005): Access is denied.

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.

I've read the recommendations on using impersonation, but that seems it won't work in my case.  I'm doing development with DNN on my local box which is VPNed into the network containing the AD server.  I'm not logged into the domain locally, and so the local login and the remote login are different.  This causes an error if I try to use impersonation because it says it can't create a user token for the remote credentials I need to access the AD server.  

Any help would be greatly appreciated

Kevin

 
New Post
5/19/2009 11:54 PM
 

I have heard of people having problems over VPN but unfortunately I can't give you any pointers as I haven't had any problem when working as you are. The only thing I can ask is if the user you're using for impersonation is a domain account?

 
New Post
5/20/2009 3:14 PM
 

The account I'm want to impersonate is a domain account, but this machine (the one running DNN) is not on the domain.  For example, I'm logged into my machine as MYMACHINE\Kevin and I'm VPNed into the domain DOMAIN using the login DOMAIN\kevink.  My VPN connection is configured with a DNS suffix of domain.com.  Under this configuration, I can use SQL Server to query LDAP://domain.com and I get the expected results.

As I understand it, impersonation means that if I'm logged in as Kevin locally, it will try to log me in as Kevin on the remote domain.  That won't work here, since the remote login is different (i.e. "kevink").

Any help will be much appreciated!

 
New Post
5/25/2009 2:56 PM
 

For anyone who comes afterwards searching for a solution to this problem:  I have been unable to get the AD provider to work with my DNN server outside of the network (VPN access) and outside of the domain.  While it is possible to query AD over LDAP using SQL Server in this configuration, I had to use a machine inside of the network and domain for the DNN AD provider to work.

 
New Post
5/26/2009 12:12 PM
 

I have gotten that scenario working here before, but the computer I was using to do the VPN session with was also a domain member.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD provider configuration errorsAD provider configuration errors


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