Solution for SQL Server Remote connection error

SQL Server remote connection error? It doesn't matter, the following is an analysis of the causes of the error in SQL Server remote connection and provides a way to solve the problem, and hopefully it will help you learn about SQL Server remote connections.

In my case for SQL Server replication, I connected a remote SQL Server database servers in local Management Studio with a default port number, no browser service, and a named instance, not a default instance , the attached server name must be connected in a mode such as Abcabcserver,port, and then configure its replication distribution (including new publications, and so on with replication-related operations), and the program will report two error messages:

SQL Server could not connect to the server "abcabcserver,1369". (Configure Distribution Wizard)

SQL Server replication requires an actual server name to connect to the server. Connections are not supported through server aliases, IP addresses, or any other alternate name. Please specify the actual server name "Abcabcserver". (replication.utilities)

To be honest, I got dizzy with the exact reason. Inexplicably, but the cause of the error is the name of the server that was filled in when the connection to the server was made using Management Studio. Because the port is not the default, so remote connection, to write in the back of ", port number" To connect, but in the distribution of the configuration, it is connected with this abcabcserver,1369 name, but in the configuration distribution when the connection, SQL Server is reported not connected.

If you want to connect successfully must have to use Abcabcserver this server name can be (I also did a test in abcabcserver local, only use this name to connect after the configuration will not report this fault, even if the local, in other ways even will be an error). and the SQL Server error prompt also said that it does not support the connection through the servers alias, but this problem can be solved by alias.

workaround, since SQL Server can only be connected by the name of the servers that are used to connect to the server, the server name that is filled in when the connection is made to SQL Server is written in the standard abcabcserver mode that it requires.

Specific solution: It's like this with a non-default port and no Browser service, only the alias to solve the problem, in SQL Server Configuration Manager, configure a abcabcserver with no port number for this pattern alias, The alias name is named after the server that you want to connect to, with the name of the actual column, and then with the top number in it, so that when you connect to SQL Server, you can connect to SQL Server by using this alias (in fact, fewer, port numbers), and then configure it without an error.

Of course, if you can adjust the SQL Server servers you want to connect to, open its browser service, so that when the remote connection does not need to write the port number, in short, to report this error, the server name used in the connection can only be the Server service instance name (if any), The other server names are not in any way.