[dba-SQLServer]Linked SQL Server Login Problems

Mark,

Try and use a SQL account login instead of a Windows account login. When you
log in to your laptop you need to have the same authenticated user on SQL
server. My guess is that you have a separate login on your laptop thus it is
passing your authentication to SQL server (that's what Trusted Connection
means) in which case it fails.

---
Eric Barro
Senior Systems Analyst
Advanced Field Services
(208) 772-7060
http://www.afsweb.com

  -----Original Message-----
  From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Mark Boyd
  Sent: Monday, July 07, 2003 11:35 AM
  To: SQLServerList
  Subject: [dba-SQLServer]Linked SQL Server Login Problems


  I have linked 2 SQL Servers (SQL1 and SQL2) using sp_addlinkedserver.  I
used this sproc to link SQL1 to SQL2, then SQL2 to SQL1.
  In Enterprise Mgr on SQL1 or SQL2, I can access the other server without a
problem.
  When I use Enterprise Mgr on my laptop, I cannot connect to either server.
I receive the following error: "Login failed for user '(null)'. Reason: Not
associated with a trusted SQL Server connection.".
  I went into the properties of each linked server, and changed
"...connections will be made using this security context:" to a valid login
on each server.  I still receive the above error, with the login in place of
(null).
  I've also tried using sp_addlinkedsrvlogin, but have not had much luck.

  Any ideas as to why I am receiving this message?
  Any help is greatly appreciated.

  Thanks,

  Mark Boyd

  Sr. Systems Analyst

  McBee Associates, Inc.



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.493 / Virus Database: 292 - Release Date: 6/25/2003
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/dba-sqlserver/attachments/20030707/36b4e77b/attachment.html>