SQL Server 2008 allows remote linking for WAN and LAN

When a user uses the SQL Server 2008 Remote link, the following dialog box may appear:

A network link error or a specific instance error occurred while linking the SQL Server. The SQL Server does not exist or the link is unsuccessful. Verify that the user name is correct or that the SQL Server has the Remote link feature configured. (Error Discovery Party: Named pipe provider.) Error code:---cannot be linked to SQL Server)

How to deal with this problem?

If the user finds this error alert, it needs to check the configuration of three aspects and make the relevant changes. (The configuration measures shown below are in the SQL 2008 Server template)

1. The first thing a user needs to do is to check whether a remote link is allowed in the SQL database server.

This check can be done in SQL 2008 server by opening the SQL Server 2008 management project (SQL Server Management Studio). The specific actions are:

(1) Right-click the SQL Server 2008 option and select SQL Server Management Studio:

(2) Open "Server Properties"

After you select the Allow users to remotely link to this server option, check to see if the issue is excluded. If the remote link is successful, the process is complete. If the user finds the Reminder error dialog box still pops up, continue.

2. Configure the appropriate protocol for Microsoft SQL Server (MSSQLServer).

At this point the user is to check the SQL network link configuration. Open the SQL Server Configuration Management option > Open the SQL Server network configuration options for this node > select the Microsoft SQL Server network Protocol option (or the option to configure the network protocol for the SQL Server in the user's SQL Server, different versions of the SQL name may differ):

Determining the TCP/IP protocol in the Microsoft SQL Server Network Options protocol is valid for the server. Check again to see if you can perform the remote link. If the Error alert dialog box still pops up, we need to check the SQL Server firewall option further. If the TCP/IP protocol uses a dynamic port, set 1433 in Ipall, and the app is saved.

3. Check SQL Server firewall settings

Open the Control Panel and select the Windows Firewall option:

After you select Advanced Settings, in the right menu bar, find Windows Firewall with Advanced Security options and open it. When you open it, you will find the "inbound rules" option in the left menu bar. Inboud Open the option and select the new Rule option in the right-hand menu bar:

After opening the new Rule option, configure the internal binding protocol for port 1433 with the new built-in binding Rule Wizard to apply to the TCP/IP protocol. (provided that you need to complete all the steps previously described in this step), the 1433 port configuration for port 1433 is available according to the following diagram:

After completing these three major steps and confirming that each step is correct, the user's SQL Server can support remote links after restarting the computer. Everything is OK.

SQL Server 2008 allows remote linking for WAN and LAN