SQL Server Client Remote access configuration

SQL2008 Error "Verify that the instance name is correct, and that SQL Server is configured to allow remote connections"

The first step:

SQL2008 error when connecting to remote server "Verify that the instance name is correct and that SQL Server is configured to allow remote connections"

For the error content, see:

Workaround:

1, first connected to the machine,

2. Then right-click "Aspect" in Object Explorer to enter the server Configuration page,

3. Choose to go to "surface area Configurator"

4. Set the Remotedacenbled property to Ture

5, click "OK", done!

If this step doesn't solve the problem

Step Two:

First look at the port to see if there is 1433 (the default port for SQL Server)

1. Running->cmd->netstat–ano

See if there is

TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING * * * * *

If this is not the case, the remote connection is not connected

2. The database engine is not started. There are two ways to start :
(1) Start-up Program->microsoft SQL Server 2005->sql Server 2005 surface Area Configuration, in the Open interface, click the connected surface Area configuration of the service, locate the database in the Open interface Engine, click on "Services", on the right side to see if it is started, if not started, click "Start" and make sure "Startup Type" is automatic, do not manually, or the next time you start the boot manually;
(2) Open: Start-up program->microsoft SQL Server 2005-> Configuration tool->sql Server config Manager, select SQL Server 2005 service in SQL Server (MSSQLSERVER), and click the "Start Service" button in the toolbar to change the service status to start;
When using either of these methods, sometimes errors may occur at startup and cannot be started, so you should see if via is enabled in SQL Server 2005 Network Configuration->mssqlserver protocol in SQL Server 2005 Configuration Manager. If it is enabled, disable it. Then perform one of the above actions.

3. Whether remote connections are already allowed. This section can be easily divided into 4 areas, namely, enabling remote connections on SQL Server, enabling the SQL Server browsing service, creating exceptions for SQL Server 2005 in Windows Firewall, and "SQLBrowser" in Windows Firewall Create an exception. Here are a few specific ways to do this:
To enable remote connections on a SQL Server instance

(1) point to Start Program->microsoft SQL Server 2005-> Configuration tool->sql Server surface Area Configuration

(2) on the SQL Server 2005 Surface Area Configuration page, click the surface area Configuration for services and connections

(3). Then click to expand Database Engine, select Remote connection, select Local Area Connection and remote connection on the right, and select the protocol to use (this place should enable the TCP/IP and Named Pipes service!). Click "Apply" and you will see the following message:
"Changes made to the connection settings will not take effect until the Database engine service is restarted. ”，

Click the OK button to return
(4). Expand Database Engine, select Services, click Stop on the right, and wait until the MSSQLSERVER service stops.
Then click Start to restart the MSSQLServer service.

4. Enable SQL Server Browser service (only native access when the service stops ) )
(1). Point to Start Program->microsoft SQL Server 2005-> Configuration tool->sql Server surface Area Configuration
(2). On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for services and connections
(3). Then click to expand SQL Server Browser, select Services, select Automatic on the right startup type, click Start, click OK to return

5. Open the 1433 port of SQL Server 2005

Start-Up Program->microsoft SQL Server 2005-> Configuration tool->sql Server Config Manager->mssqlserver protocol
See if the TCP/IP protocol starts, if it starts, right-click on the "Properties" menu, select "IP Address" in the paging menu, "TCP port" in "IP1" and "IP2" to "1433", "Enabled" to "Yes"

Must be ipall TCP dynamic port deletion, TCP port changed to 1433, only change IP1, IP2 bad use, in this problem a lot of online solutions are not clear, go a lot of detours!
Start-to-Program->microsoft SQL Server 2005 Configuration Tool->sql Server configuration manager->sql Native client-side protocol- >tcp/ip
Select "Properties" in the TCP/IP right-click menu to confirm that the "default port" is 1433, "enabled" is "Yes" (which is most important)

6, in Windows Firewall settings, someone simply shut down the firewall, of course you can in Windows Firewall for "SQL Server 2005", "SQLBrowser" Create an exception

Create an exception for SQL Server 2005 in Windows Firewall:

In the Windows firewall settings interface, select the Exceptions tab, and then click Add Program
. In the Add Program window, click Browse
Then find "C:/programfiles/microsoft files/microsoft SQL server/mssql.1/mssql/binn/sqlservr.exe" and click "OK" to return
Note: The path may vary depending on the SQL Server 2005 installation. MSSQL.1 is a placeholder that corresponds to the database instance ID.
Repeat steps 1 through 3 for each instance of SQL Server 2005 that needs to open remote access.
Create an exception for "SQLBrowser" in Windows Firewall
In the Windows firewall settings interface, select the Exceptions tab, and then click Add Program
In the Add Program window, click Browse
Then find "C:/programfiles/microsoft files/microsoft SQL Server/90/shared/sqlbrowser.exe",
Click "OK" to return

7. Check the port again to see if there is a 1433 (default port for SQL Server)

1. Running->cmd->netstat–ano

TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING * * * * *

With the

Now make the remote connection just fine!

SQL Server Client Remote access configuration