GuruBeBop wrote
Hi there!
I have the same problem you describe although it is not related to the "identity impersonate" setting you describe. My setting is commented.
I was wondering about the description you desribe. I was not aware that IUSR and NETWORK SERVICE had to have dbo permissions to the database, nor I remember this mentioned in the documentation. Is this necessary?
Hi GuruBeBop
In regards to the permissions I am running windows server 2003 (for windows server I need to have Network Service user account with permissions to the dotnetnuke folder just as is if it was ASPNET account which is what I use as per instruction in Windows XP Pro)
the reason I have IUSR account with permission to the database is just a matter of trial and error. I was getting error messages of can't connect to database when I would conect to the website with the server ip addres instead of localhost. I added the IUSR account to have permission to the db and it worked. Althoug I don't know if it is necessary, I am new at using dnn and have run into so many issues that I don't even know any more what has permissions to what.
I just ran into a new problem regarding IUSR and Windows Server Authentication module.
I am getting the following:
FAIL
OK
FAIL
I used ethereal to see what was going on and I see that it sends to ldap
not the username and password I provide but the IUSR account and then on a second request it sends the username I provide.
Does anyone have any idea what might be causing this? Anyone with the same problem?(website is for an intranet)
Thank you...