re:
I need for it to use a domain
account that wil also be authorized in the SQL Server.
As I mentioned :
If you are using Windows authentication in SQL Server,
you can use a domain account which you can have
ASP.NET impersonate.
Not a huge problem, although it's a bit
more complicated solution than it need be.
There must be hundreds of thousands, if not millions,
of web developers who connect to remote SQL Server
databases using ASP.NET, without a problem, every day.
I don't see why the case you present would be any different.
Furthermore, you might not even need to use a domain
account common to both the IIS server and the SQL Server.
You could try changing your connection string to
Trusted_Connection=yes
When using a trusted connection you do not pass the
UID and password. When you do this, SQL Server
maps the connection to a SQL Server standard login.
If you create a SQL Server standard login
YourIISServer\ASPNET with whatever password
you choose ("yourPassword"), you should connect, too,
if you allow that login the permisssions which your
database operations need.
Juan T. Llibre
ASP.NET MVP
===========