.NET and SQL Server on Separate Machines

From: Big Mo (jdecock_at_gonzaga.nospam.edu)
Date: 06/17/04

  • Next message: Fredrik Ljungbeck: "Connecting Enterprise manager to SQL 2000" 
    Date: Thu, 17 Jun 2004 12:22:44 -0700

    Hi all,

    We're working on an ASP.Net Web Application that makes several calls to a
    SQL Server database. Everything was running correctly when the database
    and the web server were on the same computer, but we have sinced moved
    them to separate computers; IIS V6 on Win2000 and SQL Server 8(SP3) on Win
    Serv 2003 Ent.

    The connection string in our web.config file originally looked like this:

    <add key="ConnectionString"
    value="server=localhost;Trusted_Connection=true;database=Store;" />

    After moving the database (and changing the server in the connection
    string), we started to receive this error: "Login failed for user
    '(null)'. Reason: Not associated with a trusted SQL Server connection."
    We ended up changing the connection string to look like this:

    <add key="ConnectionString" value="Integrated Security=SSPI;Initial
    Catalog=Store;Data Source=192.168.0.12;" />

    This string only works if we add the following to the .config file:

    <authentication mode="Windows" />
    <identity impersonate="true" />

    Unfortunately, the web application was designed to use forms
    authentication, so we're still looking for a valid connection string.
    We've tried setting Trusted_Connection=false and providing a username and
    password, but we get the same error as before - only with the provided
    username listed instead of (null). We've tried setting the database to
    mixed mode, and Win Auth only and got the same results.

    Any help would be greatly appreciated. 

    -- 
Jason De***
Elk River Systems, Inc.
http://www.elkriversystems.com
  • Next message: Fredrik Ljungbeck: "Connecting Enterprise manager to SQL 2000"