Separate Webserver and SQL Server -- error when connecting asp.net app to a datab

"Ann Marinas" <ka_marinas@dotnet.itags.org.xtra.co.nz> wrote in message
news:O8EQVObPFHA.2604@dotnet.itags.org.TK2MSFTNGP10.phx.gbl...

> Please help! I would really appreciate it!!
1) Are you using the native .NET data provider, OleDb or (surely not!) ODBC?
2) What ConnectionString are you using?
3) When you installed SQL Server, what authentication mode did you choose
(SQL Server, Windows or mixed)?
4) On the SQL Server machine, launch SQL Query Analyzer (NOT ENTERPRISE
MANAGER!) and try to log in using the UserID and password from the
ConnectionString in 2) above - can you? If so, can you drop the database
dropdown and select the database from the ConnectionString in 2) above? If
so, run SELECT * FROM sysobjects - what do you see?"Ann Marinas" <ka_marinas@.xtra.co.nz> wrote in message
news:erPYsrbPFHA.3336@.TK2MSFTNGP09.phx.gbl...
Ann,

> 1) I am using System.Data.SqlClient for my data access.
That's a good thing.

> 2) I have changed the connection string which was located in my web.config
> file when we separated the webserver to the sql db server
I'm sure you have but, if we're going to help you, you're going to have to
tell us what the ConnectionString is... :-)

> 3) The authenticatio is set to Mixed mode -- SQL Server and Windows
> Authentication
Even easier.

> 4) On the Webserver, the Query Analyzer is not installed on the webserver.
> However if I am going to access the query analyzer, I have to access the
> sql server itself.
No - just use any machine which can "see" the SQL Server and which has the
SQL Client Tools installed.