"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:OGdfNnn0EHA.4004@tk2msftngp13.phx.gbl...
> The 2 standard cases this occurs are internet replication and renamed
> servers.
> Possibly this is not relevant in your case but let's start with these.
> Please can you check:
> (a) are you using an IP address to set up replication across domains? If
> so
> then you'll need to use an alias instead.
> (b) does SELECT@@Servername return a different name to your server select
> SERVERPROPERTY('ServerName').
> If so then you need to run:
>
> Use Master
> go
> Sp_DropServer 'Server1'
> GO
> Use Master
> go
> Sp_Addserver 'Server1', 'local'
> GO
> Stop and Start SQL Services
>
> Regards,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>> > (recommended sql server 2000 replication book:
>> > http://www.nwsu.com/0974973602p.html)
>
>

"JFB" <jfb@newSQL.com> wrote in message
news:Ok8Jypl1EHA.208@TK2MSFTNGP12.phx.gbl...
> Hi I can't go forward, I have the same error... Paul Ibison was helping
but
> maybe he is busy... please help.
> Error 18483: could not connect to server 'serverName' because
> 'distributor_admin' is not defined as a remote login at the server.
> a) I'm using Named pipes and TCP/IP with not alias because both servers
are
> in the same domain.
> b) The select@@serverName is giving me the server name so this is not the
> problem.
> What is the problem here.
> Tks in advance
> Johnny
>
> "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
> news:OGdfNnn0EHA.4004@tk2msftngp13.phx.gbl...
> > The 2 standard cases this occurs are internet replication and renamed
> > servers.
> > Possibly this is not relevant in your case but let's start with these.
> > Please can you check:
> > (a) are you using an IP address to set up replication across domains? If
> > so
> > then you'll need to use an alias instead.
> > (b) does SELECT@@Servername return a different name to your server
select
> > SERVERPROPERTY('ServerName').
> > If so then you need to run:
> >
> > Use Master
> > go
> > Sp_DropServer 'Server1'
> > GO
> > Use Master
> > go
> > Sp_Addserver 'Server1', 'local'
> > GO
> > Stop and Start SQL Services
> >
> > Regards,
> > Paul Ibison SQL Server MVP, www.replicationanswers.com
> >> > (recommended sql server 2000 replication book:
> >> > http://www.nwsu.com/0974973602p.html)
> >
> >
>
>
>

"Vijay [MSFT]" <vijayts@online.microsoft.com> wrote in message
news:eJIr$mn1EHA.2068@TK2MSFTNGP10.phx.gbl...
> Are you using remote distributor?
>
> The standard procedure is
> On distributor: exec sp_adddistributor @@servername
> exec sp_adddistributiondb 'distribution'
> exec sp_adddistpublisher
> @publisher='publishername',@distribution_db='distribution',@working_director
> y='whatever it is'
> On Publisher: exec sp_addistributor 'remotedistributorname'
>
> These steps should create the distributor_admin account on
> repl_distributor
> (which should map to the distributor server) and enable publisher to
> connect
> to repl_distributor using RPC link.
>
> If you still have issues I suggest you sp_dropdistpublisher,
> sp_dropdistributiondb, sp_dropdistributor on the distributor and
> sp_dropdistributor publisher in that sequence and try again.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> OR if you wish to include a script sample in your post please add "Use of
> included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm"
> "JFB" <jfb@newSQL.com> wrote in message
> news:Ok8Jypl1EHA.208@TK2MSFTNGP12.phx.gbl...
>> Hi I can't go forward, I have the same error... Paul Ibison was helping
> but
>> maybe he is busy... please help.
>> Error 18483: could not connect to server 'serverName' because
>> 'distributor_admin' is not defined as a remote login at the server.
>> a) I'm using Named pipes and TCP/IP with not alias because both servers
> are
>> in the same domain.
>> b) The select@@serverName is giving me the server name so this is not the
>> problem.
>> What is the problem here.
>> Tks in advance
>> Johnny
>>
>> "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
>> news:OGdfNnn0EHA.4004@tk2msftngp13.phx.gbl...
>> > The 2 standard cases this occurs are internet replication and renamed
>> > servers.
>> > Possibly this is not relevant in your case but let's start with these.
>> > Please can you check:
>> > (a) are you using an IP address to set up replication across domains?
>> > If
>> > so
>> > then you'll need to use an alias instead.
>> > (b) does SELECT@@Servername return a different name to your server
> select
>> > SERVERPROPERTY('ServerName').
>> > If so then you need to run:
>> >
>> > Use Master
>> > go
>> > Sp_DropServer 'Server1'
>> > GO
>> > Use Master
>> > go
>> > Sp_Addserver 'Server1', 'local'
>> > GO
>> > Stop and Start SQL Services
>> >
>> > Regards,
>> > Paul Ibison SQL Server MVP, www.replicationanswers.com
>> >> > (recommended sql server 2000 replication book:
>> >> > http://www.nwsu.com/0974973602p.html)
>> >
>> >
>>
>>
>>
>
>