WIN2000 sp4, SQL2000 sp3
I created an alias on the local server for the SQL 2000 server installed
there, I can view and modify most sql server properties using this alias,
but when I attempt to configure the local sql server for replication, as
both a distributor and publisher, I receive the following message - "Error
18483: Could not connect to server 'servername' because 'distributor_ad min'
is not defined as a remote login at the server'.
Can you configure a sql server for replication using the alias?
My main issue is that I have 10 sql servers which need to replicate data to
the main server, the 10 servers do not have descriptive names, and would
like to assign descriptive names to servers to make management easier and to
avoid confusion. Each server is behind a NAT enabled router with 1433
pointing to the local address, each server is on a separate local domain.
Several of the server have the same name, although they belong to different
domains.
Thanks
Steve
I created an alias on the local server for the SQL 2000 server installed
there, I can view and modify most sql server properties using this alias,
but when I attempt to configure the local sql server for replication, as
both a distributor and publisher, I receive the following message - "Error
18483: Could not connect to server 'servername' because 'distributor_ad min'
is not defined as a remote login at the server'.
Can you configure a sql server for replication using the alias?
My main issue is that I have 10 sql servers which need to replicate data to
the main server, the 10 servers do not have descriptive names, and would
like to assign descriptive names to servers to make management easier and to
avoid confusion. Each server is behind a NAT enabled router with 1433
pointing to the local address, each server is on a separate local domain.
Several of the server have the same name, although they belong to different
domains.
Thanks
Steve