I guys we have been trying to get the Tam's module work around and we are not successful and we are following the instructions document but still no success.

Please any one send us the instructions.

Thanks

Are you using DNN2 or DNN3?  There is a seperate WindowsAuth w/ DNN3 thread...

Greetings. I've installed a fresh DNN 3.1 on a test box and integrated Tam's mod without any problems. That's the good news. I had several AD users log in successfully via Windows Authentication (we're not using forms based at all), their accounts got create and roles sync just fine.

Now the bad news. I had just left that box alone for 1 day, made no changes whatsoever, I'm not kidding, and today everyone is getting a login challenge/reponse dialog. Regardless of what they enter they can't log in. The only way I can get a log in it to log onto the physical box locally as an AD user who is an DNN Admin. Once in, I've tested that I can reset the Auth mod's setting sand it finds my AD etc just fine. I've looking in the database and all relevant user tables and data is their.

I've reconfirmed all the obvious stuff... file permissions, IIS settings, web.config didn't change (yes I have a backup one maintained..hehe), IE 6 settings, etc. I've rebooted the box many times, restarted clients all with the same behavior. Not sure what to do next honestly. Granted this is just a test box and I can rebuild it but I want to understand why this might have happened this early in the life of this box.

Any help or clues are appreciate.

Thanks,

Ralph

PS. Yes I've read the forum and searched already. I've read the docs. I have had awesome experience with DNN 2.x and Tam's Mods, they've been running for almost a year on a production server without a single failure.

Did you get yours figured out? I'm struggling to get Windows Authentication to work with DNN3.1.1. Works extremely well with 2.1.2, but the 3.1.1 copy gives a "not authorized" message; then you refresh and it allows you to view but doesn't log you in (although one or two users do get logged in) ... I've run through the full install a couple of times but not too much luck. Could be permissions (although I use the same user for the 2.1.2 copy) ... running out of ideas!