First, you can turn off anonymous access. This will have the user log into
the domain and the data access will work.
Second, you can add an IUSR_MachineName account to the SQL Server with the
same password. Now, the IIS password is no longer secret and this account
has any rights you allow it to have on the SQL Server machine. Not the worst
security, but not too good.
Third, you can allow all users rights to SQL Server, even the guest account.
I should not have to tell you that this is a horrible idea.
Fourth, you can make an assembly that sits in Component Services, or COM+
(Win 2k), using Enterprise Services. You can then declaratively assign a
user to run data access under.
Fifth, you can spawn a thread with another identity that has rights to SQL.
Of the above options, opening IIS Manager and clicking off the checkbox that
allows anon access is, by far, the easiest.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"Reza" <reza> wrote in message
news:E6**********************************@microsof t.com...
Hello,
I am trying to resolve this for a week and pretty much tried everything,
Windows authenticatio, Forms authentication, none of .net, but still get a
message of. Login failed for user, 'username'. I am able to connect with the same user but with SQL Authentication
access, but this is not an option though due to company policies.
I was searching on site of microsoft, looks like this used to be an old
bug, has this ever fixed?
Thanks in advance for your help,
Reza