Thanks Mike. I've just installed 4.8.2 to our staging environment and am having extactly the same problem with the "Success" status bug. Look forward to the next beta to fix this.

Cheers Wayne

I am now seeing the same problem Robert reported. I too installed 4.8.2 and then the AD-1.0.3 package. Users who have never authenticated against the site are not getting auto logged in and are not getting a windows login dialog. They are just being sent to the home page in a non-logged in state. The "Authentication"  line in web.config is uncommented and clearing cookies/cache seems to have no affect. I did secure WindowsSignIn.aspx and followed the install instructions.

Initially after I installed, it sorta kinda worked for me and a few other folks, in that we did get a windows login dialog, and saw that DNN accounts were created for us; but that isn't happening anymore, and I don't quite know what happened.

I tried an experiment: I deleted the account created for me in DNN, cleared my cache/cookies and then went back to the site. It sent me to the home page but in a non-logged in state. I then manually browsed to WindowsSignIn.aspx (/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignIn.aspx), and it popped a windows login dialog, which I filled in and it then sent me back to the home page in a logged in state (and recreated my account in DNN) -- which was all expected. So it seems as if whatever mechanism is supposed to automatically send me to WindowsSignIn.aspx is not working.

Windows Server 2003 R2 Standard Edition Service Pack 2

Can you describe what mechanism detects that the user is not logged in and forwards the user to WindowsSignIn.aspx?

One thing I did in my experimenting with the authentication settings -- not sure if this would matter -- is, in Admin -> Authentication, after having enabled Active Directory by filling in and submitting the Active Directory Settings section, I unchecked the "Enabled" checkbox under DotNetNuke Authentication Settings and submitted, at which I was shown a warning message "No providers are enabled - the standard DotNetNuke Authentication provider will be used." This confused me, since I still had Active Directory enabled. Can you explain this warning and would this have an impact?