>Hey Rick-
>
>Thanks for the reply. My issue right now is setting ASP.NET to run under a different windows user than ASPNET w/o exposing that password in the impersonate tag. I am able to connect to a SQL Database w/o using the password in the connect string.

Just set your authentication to Windows and specify a login user in web.config. This will let you run the app under a specific account and you can then use a trusted connection.

One thing to remember that's very important is that you want to use a single user all the time for the app because if you don't SQL Server's Connection Pool of the SqlClient will firre up a whole new pool of connections. Unless the connection string is exactly the same a new pool is used which can chew up tons and tons of connections in a hurry.


>IE
>Web Server running ASP.NET has a user called ws1/webUser
>Database server w/ SQL Server has a user called db1/webUser

If the user exists on both machines and has the same password then this will work just fine.

>How can I add ws1/webUser to the SQL Server database. When I try to add the ws1/webUser to my SQL Server, my SQL Server rejects that user because it does not recognize the ws1 domain.

You probably have to duplicate the user on teh second machine, unless you indeed have a domain server or Active Directory running (which you don't - otherwise this would work). If you don't then you need to duplicate users.