Hello everyone,

I got a new finding on this issue...I forgot to mention that my 4.8.2 DNN installation was in fact the result of a looooong migration from a 1.0.10 DNN installation. Everything worked fine except this AD issue.

I believe the problem resides in the migration process itself. I made a fresh install of DNN 4.6.2 with AD 1.00.04 and BAM! everything worked just as intended! I then thought it was a problem of 4.8.2 version of the portal..but oh boy I was wrong :( I made a fresh install of DNN 4.8.2 and yeah...everything worked perfectly. This is why im pretty sure its a problem with the migration process I have made.

Im going on vacation for the next 15 days, but when I come back Iam going to start with comparing both databases ( migrated 4.8.2 db and fresh 4.8.2 db ) and see If i can fin anything that leads me to the true problem.

Tobo, did you migrated your DNN installation too?

egangster wrote Hi everyone, I just installed the new AD beta and everything works great If the user is both on AD and on DNN Users database. But when I have a user on AD but NOT on DNN Users database it throws the user into an endless redirect. I have also followed Mike's AD instalation guide and read some other threads with a similar problem... Anyone could point me out some directions? I am desperate :( Some more details: DotNetNuke version 4.8.2 SQL Server 2005 AD 01.00.04.21909  Webconfig: authentication mode="Windows">forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />authentication> < <     I have also tried using the following without sucess. In this case I am presented with DotNetNuke default login and always gives access failed for both users at AD and DotNetNuke users table:

Hello Mike,

First of all, thank you for your fast feedback. I will follow your suggestion as soon as I come back from my vacations :) At least now I feel more relieved with this light at the end of the tunnel :>

Mike Horton wrote I would use a program that does directory comparisons (I use WinMerge) and compare clean 4.8.2 install against your install. I wouldn't be surprised if you find .dll files around that you no longer need and are causing conflicts (make sure you've got backups of everything before deleting files).