SQL Server Remote connection error Solution

SQL Server Remote connection error? It doesn't matter. Here we will analyze the cause of SQL Server Remote connection error and provide a solution to the problem, hoping to help you learn about SQL Server Remote connection.

This is the case when I perform replication. I connected a remote sqlserver database server in local management studio, instead of the default port number, the browser service is not enabled, and the Instance name is not the default instance. Therefore, the connection server name must be connected in the abcabcserver or port mode, then configure its replication distribution (including new publishing and other replication-related operations). The program will report the following two errors:

SQL Server cannot connect to the Server "abcabcserver, 1369". (configure the distribution wizard)

SQL Server replication requires an actual Server name to connect to the Server. server alias, IP address, or any other backup name are not supported. specify the actual server name "abcabcserver ". (Replication. utilities)

To be honest, I am confused about the specific cause, but the cause of the error is the name of the server that I entered when I used management studio to connect to the server. because non-default ports are used, you must enter ", port number" at the end of remote connection. However, during configuration distribution, it uses the abcabcserver and 1369 name for connection. However, when configuring distribution, sqlserver reports that the connection fails.

If the connection is successful, you must use the server name abcabcserver (I also tested it locally on abcabcserver. This error is not reported only after the connection is configured with this name, an error will be reported even if the connection is in another way ). in addition, the error message of sqlserver also says that connection via server alias is not supported, but this problem can be solved by alias.

Solution Principle: Since sqlserver can only use the name of the server used to connect to the server, the server name entered when you connect to sqlserver is written in the standard abcabcserver mode that it requires.

Specific solution: in this case, non-default ports and browser services are not enabled, only aliases are used to solve the problem. In the sqlserver Configuration Manager, configure an alias for the "abcabcserver" mode without a port number. The alias name is named by the name of the sqlserver Real Name of the server to be connected, and then the port number is configured in it. In this way, when you connect to sqlserver, use this alias (in fact, the port number is missing) to connect to sqlserver, and no error will be reported during configuration.

Of course, if you can adjust the sqlserver server to be connected, open its browser Service so that you do not need to write the port number for remote connection. In short, you should not report this error, the server name used for connection can only be the server service instance name (if any). Other server names cannot be used.