SQL Server 2008 Remote link when SQL database is unsuccessful

Remote connection SQL Server 2008, server-side and client configuration

Key settings:

The first step (SQL2005, SQL2008):

Start--> program-->microsoft SQL Server 2008 (or the)--> Configuration Tool-->sql Server Configuration Manager-->sql Server network configuration--> MSSQLServer (this name is the exact instance name) of the protocol-->tcp/ip--> the right key--> enabled

Step Two:

SQL2005:

Start--> program-->microsoft SQL Server 2005--> Configuration tool-->sql Server 2005 perimeter Application Configurator--> service and connection's perimeter configurator-->database Engine--> remote connection, select local and remote connections and choose to use both TCP/IP and named pipes.

(attachment: How to configure SQL Server 2005 to allow remote connections: HTTP://SUPPORT.MICROSOFT.COM/KB/914277/ZH-CN)

SQL2008:

Open SQL Server Management studio--> in the left [Object Explorer], select the first item (primary database engine)--> right button--> aspect--> Select the perimeter application configurator in the Aspect drop-down list []--> Set Remotedacenable to True. (This step is critical)

Express:

If XP has a firewall open, add the following two programs to the exception:

C:/Program Files/microsoft SQL Server/mssql.1/mssql/binn/sqlservr.exe,

C:/Program Files/microsoft SQL Server/90/shared/sqlbrowser.exe

Step Three:

Start--> program-->microsoft SQL Server 2008 (or the)--> Configuration Tool-->sql Server Configuration Manager-->sql Server service--> Right-click SQL Server ( MSSQLSERVER) (note: In parentheses with the specific instance name)--> reboot

Fourth Step:

The server side opens the SA user. Start-> program-> Microsoft SQL Server 2008-> Microsoft SQL Server Management Studio-> primary Database engine-> security-> login Name -> SA, set password.

Fifth Step:

Log on to the server side database on the client. As shown in the following illustration:

Sixth step:

C # Engineering changes the database connection string. Open the C # Engineering-> Solution Explorer-> app.config-> changes. Examples are as follows:

[C-sharp]

connectionstring= "Data source= server ip/instance name; initial catalog= database name; User id= username; password= password "

Seventh Step:

Good luck! Enjoy ...

When users use SQL Server 2008 Remote links, the following dialog box may pop up:

A network link error or a specific instance error occurred while linking to 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 configured remote link functionality. (Error Discovery Party: Named pipe supplier.) Error code:---Cannot link to SQL Server)

How to deal with this problem?

If the user discovers this error reminder, need to check three aspects of the configuration, and make related changes. (The configuration measures listed below are based on the SQL 2008 Server template)

(a) The first thing users need to do is check to see if remote links are allowed in the SQL database server. You can do this by opening the SQL Server 2008 management project (SQL Server 2008 Management Studio) on a SQL 2008 server. Its specific actions are:

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

(2) Open Server properties (right-key connection name-properties)

After you select the Allow users to make remote links to this server option, check to see if the problem has been excluded. If the remote link is successful, the process is complete. If the user finds that the Reminder error dialog box still pops up, then what you need to do is:

(ii) Configure the corresponding protocol for the Microsoft SQL Server (MSSQLSERVER).

What the user is doing now is checking 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 a network protocol for the SQL Server in the user's SQL Server, different versions of the SQL name may be different):

Determine that the TCP/IP protocol in the Microsoft SQL Server Network Options protocol is valid for the server. Check again to see if remote links can be performed. If the Error alert dialog box still pops up, we need to check the SQL Server firewall option further.

(iii) Check SQL Server firewall settings (Quick Step-close the firewall directly (unsafe))

If the client computer still cannot link to the SQL Server remotely after the last two steps, what the user needs to do is reconfigure the SQL Server firewall. In this step, first locate the port on the SQL Server that supports the TCP/IP protocol. Users can click the TCP/IP protocol to select Properties when the SQL Server firewall is already running:

As we can see from the image above, the TCP/IP protocol on this SQL Server is 1433 ports. The next step is to allow 1433 ports to support the TCP/IP protocol in the configuration of the firewall. If the Windows 7 operating system is running on the server, and its configuration steps are (similar to other Microsoft operating systems), open Control Panel and choose Windows Firewall option:

After you select Advanced Settings, locate and open Windows Firewall with Advanced security options in the right menu bar. When you open it, you will find the "inbound rules (Inboud rules)" option in the left menu bar. Open this option and select the new Rule option in the right 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. (If you need to complete all the steps previously described in this step), apply to port 1433 for the 1433 port configuration according to the following diagram:

Complete the three major steps above and confirm that each step is correct, the user's SQL Server can support remote links, everything OK.

(Note: You must restart the SQL service before you can complete the second step) (net stop mssqlserver net start MSSQLServer).