Well, I've just about tried anything now... no impersonation, impersonation without username, impersonation with admin account... I just can't get through to AD. We ran into some problems with using the import tool, which doesn't appear to be much good on the webserver.At this point, the only way I'm able to query the AD, is on localhost with impersonation set to the admin account, leaving the domain/username/password empty (on the import tool). AD authentication still hasn't connected. I've looked through the code of the import tool and it comes to this line:

directoryEntry = new DirectoryEntry(totalDomain);

with "totalDomain" being string.Empty.

How can this be working? How can I do this with the AD provider?

I tried looking for answers in the source code of the AD provider, but the package seems to contain the same things as the install package... no source code :-(

I see, I thought that resources file was a bit large :-)

Anyway, I just installed the AD-provider at the client and it connects just fine. I can't seem to login with any windows account though...

- install ad provider -> check
- configuration settings to connect to ad -> check
- disable anonymous access to WindowsSignin.aspx
- set impersonation to true in web.config
- attempt to login using windows authentication (the form does show the option for it) -> Login failed

The event viewer shows me "Invalid password" in the method "DotNetNuke.Entities.Users.UserController.ChangePassword".

Why does it even want to do ChangePassword?