Re: Web Server connecting to db server on different machines

Hi,

if you want to delegate client credentials - kerberos is they only way to go.

You could disable delegation and use a trusted subsystem design to access the back-end resources.

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

Thank you.

Seeing as I may not be able to convince our AD services group to do
this, is there another option?

Thanks.

"Dominick Baier [DevelopMentor]" wrote:

http://msdn.microsoft.com/msdnmag/issues/05/09/SecurityBriefs/default
.aspx

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com
Hello

Im creating an asp.net web app that will need to connect to a SQL
Server db on another machine. I have set this up using trusted
connections and impersonation in the web.config file but I am
getting a "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"
message. I need this to work through domain accounts on both
machines.

Currently, it will work if I am using the machine where the web app
resides (ie. http://localhost/webapp/page.aspx) but i get the above
message when using another remote machine.

Any help is appreciated.
Ben


.