Re: Security in Linked Servers

From: Terry (trohrer@autocontroltech.com)
Date: 10/16/02


From: "Terry" <trohrer@autocontroltech.com>
Date: Wed, 16 Oct 2002 08:00:59 -0700


I did both and nothing seems to work...Terry

>-----Original Message-----
>Terry,
>
>Have you followed the step in this topic in BOL:
>
>How to add a linked server login (Enterprise Manager)
>
>If so, did you enter a remote user and password or did
you turn on the
>impersonate check box?
>
>Russell Fields
>"Terry" <trohrer@autocontroltech.com> wrote in message
>news:307601c2747d$a1d59ba0$36ef2ecf@tkmsftngxa12...
>I consistantly get the Error 18456: Login Failed message
>when trying to link servers. I've tried it in different
>scenerios, including linking 2 servers on the same machine
>running under the same login with identical SQL security
>accounts/settings and still I get this message. I've
>tried setting up the security mapping in several different
>ways. I get the Error 18456 in the Enterprise Manager
>when I try to refresh the tables under the security then
>the linked sub-tree and when I try to SELECT from a table
>in the Linked Server. Any ideas.
>
>Thanks,
>Terry
>
>
>.
>



Relevant Pages

  • Re: Security in Linked Servers
    ... How to add a linked server login (Enterprise Manager) ... tried setting up the security mapping in several different ...
    (microsoft.public.sqlserver.security)
  • Re: Linked Servers - HELP GEORGE or HILARY
    ... Do you mean the account that sql server is using to connect to ... > indexing service needs to be a dbo, or do you mean that the login the we ... We have set the security options on the ... > linked server to connect to indexing server using the sql login's current ...
    (microsoft.public.inetserver.indexserver)
  • Re: deny select on linked server
    ... Here is a way to disable one login from using the linked server, while allowing all other logins through. ... -- Grant the excluded login rights to login with a non-existing login and password ... In the radio buttons below, select "Be made using the login's current security context" ...
    (microsoft.public.sqlserver.security)
  • Update
    ... Seems to have something to do with security. ... Windows NT user activated by SETUSER. ... I gather that the SQL Agent Job ... >linked server, and these work via Query Analyzer. ...
    (microsoft.public.sqlserver.security)
  • Update
    ... queries against a linked server (DB2 UDB). ... Servers security properties, ... ID and password for the linked server. ... to be that the job owner is a SQL Server login that is not ...
    (microsoft.public.sqlserver.security)