Fer wrote Hi everyone, I have a few problems with AD authentication.  First I've tried to activate AD autentication (ADSIAuthenticationProvider and Delegation), Root domain DC=XXXX and User Name XXXX\YYYYY (this is a user with access to the domain) but the result was 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 changed the config to Root domain XXXX.COM and User Name XXX\YYY and the result was Accessing Global Catalog: FAIL Checking Root Domain: OK Accessing LDAP: FAIL Find all domains in network: Could not access LDAP to obtain domains info Logon failure: unknown user name or bad password.  So I start to google about AD Authentication but all the information about it was ralated to earlier versions of DNN. I didn't give up, and make some changes to the web.config, switching the authentication mode from form to Windows (including uncommenting the impersonate node) and the authentication became to work because it didn't ask me to log in altought it's not enabled from ADMIN > Authentication!!!!

That's because you're bypassing all authentication in DNN and using Windows period. You're not even hitting the AD code.

I went to the Authentication option and turn it on and the initial settings from the post (ADSIAuthenticationProvider, Delegation, Root domain DC=XXXX and User Name XXXX\YYYYY) and the result was   Accessing Global Catalog: OK Checking Root Domain: OK Accessing LDAP: OK Find all domains in network: 1 Domain(s): icebergsolutions.com (ICEBERGSOLUTION) The problem is that I have 2 child portals (linked in the menu thru 2 pages in the parent portal using a Link to an external resource but pointing to the child) and when I click on one child, the status bar from the IE starts to flick, I cant view anything and after that I get a timeout error. May be that's not the correct way to link to subportals, but I didn't find other one. Other problem that I'm getting it's that 3 domain users were created automatically during some test, but now I tried to enter (to the parent portal) from another machine with other user logged in and I get the flicking in the status bar. Do you have any idea about those problems? Thanks, Fernando    Other notes about the web.config: The line   is uncommented and the line crearly commented

A couple of things: The error you were getting originally was because you need to uncomment the <impersonate="true" /> line from the web.config and only that line from that section (leave DNN using forms authentication). You'll have to make some additional changes to it that are covered in the documentation.

The screen flashing that you're seeing is a side effect of changing the authentication in the web.config from forms to Windows. If the account already exists in the DNN database the user is logged in but if it doesn't the application gets thrown into a loop. I posted some links in the last couple of weeks on some possible fixes for that and I'll see if I can find the post that they're in.

Child portals have been an issue with the AD provider for a long time but I think I've got it fixed in the 01.00.04 beta (see the pinned post at the top of the forum).