Hi, trying to setup AD using v1.0.4 on DNN 4.8.4

When clicking the Update Settings on the Authentication page i get;
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.Settings.UpdateSettings() --- End of inner exception stack trace ---

I have been through the instructions several times and have also tried the impersonate settings which causes more problems. What domain\username combination should i use for the imporsonate - should they be the same as the user i'm using in the AD Authentication settings? The server is a DMZ and not on the same domain as the AD server so can i just create a user on the DMZ and use those details? They have opened port 389 and tested that the DMZ can see the AD server using Softerra LDAP Administrator and this works ok.

Would really appreciate some pointers so i can get this working.

Thanks in advance.

Dan.

Hi, with the user for impersonation as the DMZ is not part of the AD domain i wasn't sure what user to put in here, does this user have to exist on the DNN host machine? if so i guess we can't use it to query the AD server though.

When i tried impersonatio without specifying a user, DNN stopped working as it couldn't then login to the database (SQLExpress) - i assume it must affect this as i don't specify a user in the connection string.

In the settings for AD, if i use the settings as your example, e.g. dc=domain,dc=com then how is it going to know where the AD server is as it's not in the same domain and network? We tried putting in the full domain for the AD server and it at least did the diagnostics but all failed. e.g. ad.domain.com

Reading in the forum, there was mention of different ways in which to enter the root domain and some worked better than others - could someone expand on this? I see someone modded some code which handled the name better and constructed them in the correct way - is this mod available?

I'm new to AD integration so sorry if i'm covering old ground here.

Thanks for your help.