security for linked server

  • We need to have a process connect from a SQL Server 2005 server/database to a SQL Server 2000 server/database. The users that need to have access have server logins on both SQL servers and users in both databases. The linked server is created on the 2005 server with RPC in and out set to 'true', collation compatibility is set to false, use remote collation is set to 'true', security is set that if the user is not in the list that it should use the current security context. When the user tries to run the statement that needs to use the linked server the error message saying that it failed because user 'NULL' cannot connect. I thought the users actually id would be passed not user 'NULL'. I do not want these users to have full system or server permissions. If I tell the linked server to connect as 'sa' if the user is not in the list then the linked server is accessible [by all].

    Can someone tell me what is set incorrectly? Both SQL Servers are set to use Windows and SQL security.

    Thank you in advance for your insight.

  • What are the OS's of the two servers - and are they on the same domain?

  • The SQL Server 2005 is on Microsoft Windows 2003 R2 Standard 64 Edition, Service Pack 2

    The SQL Server 2000 is on Microsoft Windows 2003 Enterprise Edition, Service Pack 2

    Both servers are on the same domain, the same domain user runs the sql service on each

  • The "Null" user issue is usually related to "integrated security" (i.e. Windows authentication) failing to properly transfer credentials between the two servers - how are the users connecting to the first server (the direct one) - is it with integrated security?

  • Yes. Except for specific applications the users that need to use the linked server connect via their Windows domain account.

  • Have a look at this article

    http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply