System.Data.Sql Client.SqlExcep tion: Login failed for user 'NT AUTHORITY\ANONY MOUSLOGON'

[Nick nkw]

I already following the steps in:
http://msdn.microsoft.com/library/de...edsecurity.asp

But I still get the error. I found it works when using VS.Net internal
web server. It use Domain\MachineN ame$ to connect SQL Server after
publish to IIS. (It works on IIS after I remove <identity
impersonate="tr ue"/>)

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

What this is telling you is that the Anonymous Logon identity doesn't have
permissions to the specified database. Obviously, as you stated, you can
either change the identity to one that does, or give this account permssions.
Or, you can use SQL Server authentication, which is often a lot easier.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Nick nkw" wrote:

I already following the steps in:
http://msdn.microsoft.com/library/de...edsecurity.asp

But I still get the error. I found it works when using VS.Net internal
web server. It use Domain\MachineN ame$ to connect SQL Server after
publish to IIS. (It works on IIS after I remove <identity
impersonate="tr ue"/>)

[bruce barker]

you will notice, that if you connect to your dev box from another
machine it won't work with <identity impersonate="tr ue"/and if you hit
the site locally on the web server it will work (just like using your
dev box).

to use impersonation you need to switch to kerberos (and enable forwarding).

-- bruce (sqlwork.com)
Nick nkw wrote:

I already following the steps in:
http://msdn.microsoft.com/library/de...edsecurity.asp
But I still get the error. I found it works when using VS.Net internal
web server. It use Domain\MachineN ame$ to connect SQL Server after
publish to IIS. (It works on IIS after I remove <identity
impersonate="tr ue"/>)

[msdn]

my develop box is also connect to the SQL server remotely. And sp_who shows
my Windows domain users. Sounds internal web server and IIS handle SQL
Server logon differently.

"bruce barker" <no****@nospam. comwrote in message
news:O7******** *****@TK2MSFTNG P04.phx.gbl...

you will notice, that if you connect to your dev box from another machine
it won't work with <identity impersonate="tr ue"/and if you hit the site
locally on the web server it will work (just like using your dev box).

to use impersonation you need to switch to kerberos (and enable
forwarding).

-- bruce (sqlwork.com)
Nick nkw wrote:

>I already following the steps in:
http://msdn.microsoft.com/library/de...edsecurity.asp
But I still get the error. I found it works when using VS.Net internal
web server. It use Domain\MachineN ame$ to connect SQL Server after
publish to IIS. (It works on IIS after I remove <identity
impersonate="t rue"/>)