Mike,
I'm having a similar problem to Simon but not quite the same. I get the message "No Providers are enabled - the standard DotNetNuke Authentication provider will be used"
I get the following for the authentication to AD.
Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
OK
Find all domains in network:
1 Domain(s):
huntinternal.com (HUNT)
If I attempt to hit the Login button it brings up the standard DNN login. When I navigate to the Windowslogin.aspx page it brings that page up (no auto signin). I can fill the information for any windows account and it will authenticate properly and create the account(s) in DNN as they are in DNN. Then you stay logged into DNN on any other browser (ie) that you open.
I have tried changing to use the windows impersonation on the web.config. I tried the Browser to allow the site to local trusted site. I have the authentication provider uncommented. I also tried Simons issue with renaming the username in the aspnet_users and Users table. I never get the error Simon describes about the creation of the user.
I also have the Login Control hidden.
It seems like the provider works by allowing me to sign in with any account that I want and the provider is just not the default enabled internally within DNN during this configuration. I'm thinking maybe I should get the source and see why the AD provider comes back with not enabling it.
When I set the provider to NOT hide controls, it gets through without the the default DNN provider error however the login button shows only the old DNN login. The site never automatically brings up the windows authentication control as shown in page 8 of your User Guide.
Do you have any direction on this?