QUESTION: SQL Server access in a one-way trust

• Doug Whittier

  SSC Enthusiast

  Points: 173

  More actions

  November 15, 2005 at 4:06 pm

  #111187

  Hi, all.

  I am having some confusion with connecting to a SQL 2000 SP4 Server

  across a one-way trust.

  I have a SQL server in the trusting domain, and the Admin workstations

  in the trusted domain.

  I am not using domain-level (Windows) authentication, I am only using SQL IDs.

  If I log onto the workstation in the trusted domain with an ID in that

  domain, and attempt to establish a connection to the server, it fails:

  "A connection could not be established to %SERVERNAME%. Reason: SQL

  Server does not exist or access denied. ConnectionOpen (Connect()).."

  If I log onto the workstation using an ID in the trusting domain and

  attempt the same thing, the connection works.

  What is bizarre is that I can get around this behavior by mapping a

  drive to the server from my PC in the trusted domain, using credentials

  from the trusting domain.

  It is as if some 'domain-level' authentication to the server still has

  to occur before the SQL Server ID connection will work.

  I want to be able to connect to this box, but not be forced to use a

  domain ID from the trusting domain, or continually map a drive.

  Again, domain-level authentication was not how I configured the server;

  I set it up for SQL Server IDs only.

  Can anyone shed some wisdom on this one??

  Thanks!!

   

• Carl Federl

  One Orange Chip

  Points: 25384

  More actions

  November 15, 2005 at 7:56 pm

  #604072

  The original version of MDAC version 2.6 that was installed with SQL server 2000 has a known bug with igonoring authentication settings.

  See FIX: SQL Server ODBC Driver Ignores Authentication Setting

  http://support.microsoft.com/kb/q279526/

  You could just apply SQL Server Service Pack 4 to your workstation's Client Tools to solve the problem as this will upgrade to MDAC version 2.8

  SQL = Scarcely Qualifies as a Language