Replication between 2 SQL from 2 Windows SBS 2003?

Replication between 2 SQL from 2 Windows SBS 2003?
I have 2 SBS servers with SQL 2000. I would like to do a Merge
replication, I did it using wizard and everywhere I choose not trusted
connection but SQL login and password:
Configure '192.168.10.3' as a Publisher. Use '192.168.10.3' as the
Distributor.
Use '\\192.168.10.3\f$\Microsoft SQL
Server\MSSQL\ReplData' as the root snapshot folder for
Publishers using this Distributor.
Store the distribution database 'distribution' in 'f:\Microsoft
SQL Server\MSSQL\Data'.
Store the distribution database log file in 'f:\Microsoft SQL
Server\MSSQL\Data'.
Enable the following databases on '192.168.10.3' for merge
replication:
SampleDataBase
Enable the following servers as Subscribers to
publications on '192.168.10.3':
10.9.0.1
But I receive:
SQL Server Enterprise Manager could not configure '192.168.10.3' as the
Distributor for '192.168.10.3'.
Error 18483: Could not connect to server ‘NSS’ because
‘distributor_admin’ is not defined as a remote login at the server.
But:
SELECT @.@.SERVERNAME, SERVERPROPERTY('ServerName') returns
NSS NSS
So it seems properly.
Ping nss working properly..
I need help!!! Any concepts? Maybe something connected with
distributor_admin and trusted connection – I heard somewhere that it is
possible to disable trusted connection for distributor_admin but I don’t
know how to do it?Hello,
I understand that when you try to create a merge replication, you receive
the error message "Error 18483: Could not connect to server "NSS" because
"distributor_admin" is not defined as a remote login at the server."
However, the servername is correct and it is the same as
SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
This issue could occur when the Machine name at windows level (Hostname) is
different from SQL Server Name (Select @.@.servername).
And this happens when the machine on which SQL Server is installed is
renamed after SQL Server installation. If it is so you will have to do the
following using Query Analyzer:
Sp_dropserver <server>
(Replace <server> with the name returned by Select @.@.servername query)
Sp_addserver <server>, local
(Replace <server> with the machine name (Hostname) if it is default
instance otherwise <server>\instancename for named instance)
Also, did you try to use servername "NSS" when configure merge replication
and not using IP adress directly? I suspect this issue may also related to
network name resolution.
More related information:
818334 Replication setup is not successful when SQL Server is deployed by
using a disk image
http://support.microsoft.com/defaul...kb;EN-US;818334
321822 HOW TO: Replicate Between Computers Running SQL Server in
Non-Trusted Domains or Across the Internet
http://support.microsoft.com/defaul...kb;EN-US;321822
If you have any update, please let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Peter Yang [MSFT] napisa?(a):
> Hello,
> I understand that when you try to create a merge replication, you receive
> the error message "Error 18483: Could not connect to server "NSS" because
> "distributor_admin" is not defined as a remote login at the server."
> However, the servername is correct and it is the same as
> SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
yes its true!

> This issue could occur when the Machine name at windows level (Hostname) i
s
> different from SQL Server Name (Select @.@.servername).
> And this happens when the machine on which SQL Server is installed is
> renamed after SQL Server installation. If it is so you will have to do the
> following using Query Analyzer:
Select @.@.servername
returns
NSS
and full computer name is:
nss.domain.local
it is a domain server (SBS)
so computer name is nss and never been changed!

> Sp_dropserver ?<server>?
> (Replace <server> with the name returned by Select @.@.servername query)
>
> Sp_addserver ?<server>?, ?local?
> (Replace <server> with the machine name (Hostname) if it is default
> instance otherwise <server>\instancename for named instance)
> Also, did you try to use servername "NSS" when configure merge replication
> and not using IP adress directly? I suspect this issue may also related to
> network name resolution.
> More related information:
>
> 818334 Replication setup is not successful when SQL Server is deployed by
> using a disk image
> http://support.microsoft.com/defaul...kb;EN-US;818334
>
> 321822 HOW TO: Replicate Between Computers Running SQL Server in
> Non-Trusted Domains or Across the Internet
> http://support.microsoft.com/defaul...kb;EN-US;321822
I will try it this...