Is the account you are using part of the PAL, or does it have rights to
access the publisher/distributor?
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com [quoted text, click to view] "GRP" <GRP@discussions.microsoft.com> wrote in message
news:AFC5E159-D19F-453F-BD61-01D392E6A154@microsoft.com...
> We have a replication setup that has been working for a long time which
> involves one server acting as the Publisher and Distributer. We have over
> 400
> clients that replicate using 1 trans and 1 merge subscription each. We
> have a
> windows account that we use to manage security on both sides by using it
> to
> start the SQL Server agent on the clients and host server. The problem is
> that we have been asked to move away from this common account or we have
> to
> change the password on it every 60 days.
>
> I started looking for alternatives and found I can used the securitymode
> parameters to specify SQL Server accounts and then the offload parameters
> to
> configure the Publisher so that it uses the SQL Server accounts to run the
> synchronize.
>
> The setup goes fine but when I go to synchronize I get the following:
>
> "The specified remote server name may not be the network name of the
> remote
> server or the remote server is unreachable due to network problems. The
> step
> failed."
>
> Any help is appreciated.