We have seen this problem before and fixed it by looking at the KERBOS configuration program. But now I have something odd. Both I and another DBA have the same SysAdmin perms to both boxes. But when we are on the same server trying to run a query off the same linked server, mine works and yet his gives him the error above. What can be causing that? I would have assumed if all things are equal we'd either both be successful or both get the same error.
This is when we are running it in SSMS from our Terminal server. But when we both actually RDP onto the server we are running this from (not the linked server server) it works fine without any problems.
The security has nothing in the mapping and the Be made using the login's current security context is checked. Here is the create statement for the linked server:
@srvproduct=N'SQL Server'
@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
@optname=N'collation compatible', @optvalue=N'false'
@optname=N'data access', @optvalue=N'true'
@optname=N'dist', @optvalue=N'false'
@optname=N'pub', @optvalue=N'false'
@optname=N'rpc', @optvalue=N'true'
@optname=N'rpc out', @optvalue=N'true'
@optname=N'sub', @optvalue=N'false'
@optname=N'connect timeout', @optvalue=N'0'
@optname=N'collation name', @optvalue=NULL
@optname=N'lazy schema validation', @optvalue=N'false'
@optname=N'query timeout', @optvalue=N'0'
@optname=N'use remote collation', @optvalue=N'true'
@optname=N'remote proc transaction promotion', @optvalue=N'true'
