Mandar:
In this case you have several options:
- use a "mirrored" local account on the SQL machine, meaning you'll
create an ASPNET account on the SQL machine, synchronize passwords for
the ASPNET account on the web server and SQL machine, and give the
ASPNET account the ability to login to SQL. There is a more detailed
description of how to do this in the following document:
Building Secure ASP.NET Applications: Authentication, Authorization,
and Secure Communication
http://msdn.microsoft.com/library/de...SecNetHT01.asp
- run the ASP.NET worker process in the context of a user who can
access SQL
- use mixed mode authentication (pass a uid and password in the
connection string)
HTH,
--
Scott
http://www.OdeToCode.com
On Wed, 26 May 2004 13:21:13 -0700, Mandar
<> wrote:
>ASPNET is not user on the machine and machinename\ASPNET is also not the SQL server instance.