[dba-SQLServer]Linked SQL Server Login Problems

Eric -

Thanks for your help.  I think I finally got it working.

I believe one of the main issues was the way the 2 servers were
configured.

The authentication was set up as 'Windows Only' on both machines.

I changed this to 'SQL Server and Windows', then created a login with
SQL authentication.

Everything looks good.

 

Thanks again,

Mark

 

-----Original Message-----
From: Eric Barro [mailto:ebarro at afsweb.com] 
Sent: Monday, July 07, 2003 3:30 PM
To: dba-sqlserver at databaseadvisors.com
Subject: RE: [dba-SQLServer]Linked SQL Server Login Problems

 

Mark,

 

When you configure your EM connection from your laptop you need to
uncheck the trusted connection box and instead use SQL server
authentication instead of Windows authentication. Windows is trying to
pass your Windows authentication to the SQL server. Since you are not on
the same domain as the SQL server when you connect it will see you as a
"different user". In other words you won't be using the same security
context.

---
Eric Barro
Senior Systems Analyst
Advanced Field Services
(208) 772-7060
http://www.afsweb.com <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 12:08 PM
	To: dba-sqlserver at databaseadvisors.com
	Subject: RE: [dba-SQLServer]Linked SQL Server Login Problems

	Eric -

	Thanks for the reply.

	I have now created a new login on SQL1, named MarkB, with SQL
Server Authentication.  This is the same network login I use when
booting up my laptop.  I changed the security option "...connections
will be made using this security context:" to MarkB, and my network
password.

	Although, I am still receiving the error "Login failed for user
'MarkB'. Reason: Not associated with a trusted SQL Server connection.".

	What am I missing?

	 

	Thanks,

	Mark

	 

	-----Original Message-----
	From: Eric Barro [mailto:ebarro at afsweb.com] 
	Sent: Monday, July 07, 2003 2:41 PM
	To: dba-sqlserver at databaseadvisors.com
	Subject: RE: [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 <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.

		 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/dba-sqlserver/attachments/20030708/8940a8ff/attachment.html>