Some weeks ago we set up DNN with AD integration for our new Intranet. At first, everything seemed to work fine when we tested with some users: First Name, Last Name, Display Name, E-Mail and Roles were correctly synchronzied. Now, after we went live, when I look at our user table, none of our user are synchronized correctly, but get the following information instead:

• Username: DOMAIN\user-id (this, of course, is correct)
• First Name: user-id
• Last Name: (empty)
• Display Name: (empty)
• E-Mail: user-id@our-company.com

As one of our custom modules depends on a correct e-mail address, this issue causes many problems.

Could it be one of the following reasons:

• Since our first test, we changed our portal alias to http://our-intranet-name/. Could it be that?
• We did not add our intranet to the trusted intranet zone on every computer, because it seemed to work fine without. I think I can remember that when we tested the first time, things were syncronzied correctly even without having the intranet address added to the trusted zone.

I would be glad if someone can help us, as this is a really big issue for us. Thanks in advance!

//edit: I afterwards checked our AD settings in DNN again. While the settings are still the same, I am now getting the following error message when clicking "Update authentication settings":

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

Thanks for your reply, Mike. I read the AD users guide, where it says the following:

• Give the user account you use for impersonation the same permissions to your DNN install that the NETWORK SERVICE or ASPNET account has.
• The user account may also need the same permissions that the NETWORK SERVICE or APSNET account has on the website directory in the Temporary ASP.NET Files (usually found under the <SystemDrive>:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files directory).

Can you explain what user account I have to take? Do you know, why this is now causing a problem but not before? Is the error message and the missing/incorrect synchronization because of this impersonation? I would like to understand the problem better.

Sorry to ask again, but I do not know much about this topic and I have to brief my colleague who is now working on this issue:

What is a domain account? As I have to tell my colleague to try the impersonation solution, I have to tell him to add a domain account but do not know what to tell him exactly. Do we have to create an additional AD user? Or only a user account on the machine our intranet is running on?

Thanks again!