Re: SQL Server 2000 linked server problem

Tech-Archive recommends: Speed Up your PC by fixing your registry



frankm,

Could you describe the security settings on the linked server's security
tab?

If it is "Be made using the login's current security context" then it might
imply that something broke the delegation chain for the double-hop needed to
pass a user's credentials to the next server. When you are logged onto the
server there is no double-hop since the linked server is only one hop away.

Does that make sense? In that case, it is not a SQL Server problem, but a
Windows or a domain problem. The SQL Server is simply victimized. Since I
am not a domain/network administrator I don't have good insight into what
could be wrong, but I am pretty sure that is where the problem lies.

RLF


"frankm" <frankm@xxxxxxxxxxxxxxxx> wrote in message
news:v0Tcj.1219$se5.545@xxxxxxxxxxxxxxxxxxxxxxx
The error is "SQL Server does not exist or access denied" which means it
cannot connect.
I know all of it works - it works from EM on the server itself and doesn't
from any remote client.
I have tried RPC settings and that does not work.

Apparently this happens "once in a while", and it takes a reboot to fix
it.





"Russell Fields" <russellfields@xxxxxxxxxx> wrote in message
news:%23v9K5rLSIHA.3532@xxxxxxxxxxxxxxxxxxxxxxx
frankm,

What error are you getting? That might reveal what the problem is. In
general: Check the security tab of the linked server properties if it is
security context error. You might also check the Server Options for how
RPC and RPC OUT are set.

Out of curiousily, have their been any changes to your network
infrastructure for the purpose of making the network more secure?

RLF

"frankm" <frankm@xxxxxxxxxxxxxxxx> wrote in message
news:%jRcj.1769$pr6.1313@xxxxxxxxxxxxxxxxxxxxxxx
This is SQL Server 2000 sp3a.

I have linked servers that have been working for a fairly long time.

If I am on the server (TermSvc), I cann connect and test through the
linked server successfully.

If I am initiating this from any workstation or application off the SQL
Server itself, the linked server connection fails.

Any ideas???

frankm







.



Relevant Pages

  • Re: Server 2003 AD, security context APIs, "operations error" ??
    ... since that is a much more common server scenario than ... Are you saying that the NTLM security ... security context to log on remotely, but if it is not forwardable (cannot be ... access AD and read this info if the process' account has the rights in AD to ...
    (microsoft.public.platformsdk.security)
  • Re: Server 2003 AD, security context APIs, "operations error" ??
    ... Are you saying that the NTLM security ... context retrieved from the client isn't passed along to the AD? ... act of passing along the security context the thing called "delegation" ... The server AD get call fails another way -- ...
    (microsoft.public.platformsdk.security)
  • RE: addling linked server
    ... What is the target for the linked server? ... Is it SQL Server? ... what security context you need to have the queries run on your linked ...
    (microsoft.public.sqlserver.server)
  • Re: Setting up Linked server to MsAccess
    ... This will set the security so anyone using the linked server ... At the database level I have added my Server login ...
    (microsoft.public.sqlserver.security)
  • Re: MAS90
    ... To set up a linked server from SQL Server 2000 to MAS90 using Enterprise ...
    (comp.databases.ms-access)