Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Before asking a question I tried to follow through the points in the above article to set up a trusted connection between a MS SQL server and a production IIS 7 server.

I essentially want the DB connection string to connect to the server without having to pass login info.

They are not a private network.

I have tried the points in the article but this didn't work.

Does anyone have any other suggestions on how I can achieve this?

share|improve this question
up vote 0 down vote accepted

The method works if either the IIS Application Pool and SQL Server login are the same domain account, or if they share username and password (i.e. fall back to workgroup like mode of login).

The way I get the IIS web application to run under a specified user account is to create an application pool with the identify I want, and then assign the web application to use that application pool. No need for impersonation settings in Web.Config.

share|improve this answer
Thanks. Any idea how to implement this when you have for example a Mailserver and a Sql Database Server which you want to connect over a private network in a trusted manner? – user29100 Dec 15 '09 at 9:29
Define the account, then create the IIS application pool to use that account, assign the IIS web app to that application pool. Then give that user access to the (remote) things the application needs. – Richard Dec 15 '09 at 10:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.