|Message:||Could not connect to server ‘%ls’ because ‘%ls’ is not defined as a remote login at the server.|
|Setting up security for executing remote procedure calls (RPC) against a remote server involves setting up login mappings in the remote server and possibly in the local server running an instance of Microsoft SQL Server. The mapping is specific to a given server\instance name, usually the NetBIOS name for a default instance and the NetBIOS name plus the instance name for a named instance. If the login mapping does not exist or if the name of the server specified in the connection string does not match the exact name in the sysremotelogins table, and the guest account does not have a mapping in sysremotelogins, you will receive this error. You will also see this error if the remote user is found to have a null or empty login name.
Special Considerations for Replication
Replication uses remote server definitions to connect to the Distributor, Publisher, and Subscriber. At the time you enable and configure replication, you implicitly create remote servers and add login mappings for those remote SQL Server instances. Replication connection strings will always specify the NetBios name for a default instance and the NetBIOS name plus the instance name for a named instance. Therefore replication will not find or use remote server names that were defined for IP addresses or for fully qualified domain names. When the replication connection attempt cannot find the NetBIOS name in sysremotelogins, you will receive the above error.
Microsoft SQL Server replication is supported when the servers involved are registered by NetBIOS (network) name, but not when the servers involved are registered by IP address or fully qualified domain name. For more information about how to replicate between computers running SQL Server in non-trusted domains or across the internet, see Microsoft Knowledge Base article 321822.
Note Support for remote servers is provided for backward compatibility only. New applications that must execute stored procedures against remote instances of SQL Server should use linked servers instead.
|If any of the servers involved in the query or used in replication have ever been renamed or were created from an image, you must ensure that the NetBIOS (network) name matches the machine portion of SQL Server’s @@SERVERNAME. If they do not match, you can follow the steps in the Books Online (Updated – SP3) topic, “Renaming a Server,” to update the value of @@SERVERNAME. This change does require that you restart the SQL Server instance. For more information about why replication setup is not successful when SQL Server 2000 is deployed by using a disk image, see Microsoft Knowledge Base article 818334.
If this error occurs during replication, verify that you configured the Distributor, Publisher, and Subscriber using the NetBIOS (network) name, not the IP address or fully qualified domain name.