Hi
Our Sql Server Agent is set up to use a domain account.
ourdomain\our_special_account
All of our sql servers on the same domain (even in different locations) use
this special domain account that our administrators created for us.
I can not seem to create a linked server using this domain account.
Therefore I set it up to use the sa account of the server.
all our servers also have the same sa sql account and password because these
servers were created from the same virtual machine templates ....
[quoted text, click to view] "Hilary Cotter" wrote:
> The security context used is whatever security context you configured your
> distribution agent to connect to the subscriber with. By default this will
> be the Publisher SQL Server Agent account if you are using a push
> subscription.
>
> When you created your subscription you define this in the Distribution Agent
> dialog box, in the Connect to subscriber section.
>
> "I.W Coetzer" <IWCoetzer@discussions.microsoft.com> wrote in message
> news:ACE5DB2B-1A03-48EC-BA15-3005F0C41A16@microsoft.com...
> > Hi
> >
> > We have set up Transactional Replication between two servers.
> > However the linked server that is created at the subscriber does not work
> > be
> > default.
> >
> > I therefore selected the last option "Be made using this security context"
> > and entered the sa username and password.
> >
> > This solves the problem - linked server can then connect.
> >
> > But what I want to know is how to get the first option working by
> > specifying
> > a local login and remote user and remote password.
> > I have tried all users on the servers and in different combinations with
> > impersonate options ticked on some! but could not get it working.
> >
> > So for now it is running using the sa username and password.
> >
> > How does login-mapping work? why can I not get it to work?
> >
> > Please advise
>
>
