A workaround for remote connections that SQL Server does not allow

The database system just installed, by default, is likely to be a remote connection times wrong, usually error: "When connecting to SQL Server 2005, the default setting for SQL Server to disallow remote connections may cause this failure."

(provider: Named pipe provider, error:40-cannot open a connection to SQL Server) , now summarize the issue as follows:

Understand that SQL Server is a network database can be solved, simple to be divided into the following several situations.

1. The database engine did not start. There are two ways to start:

(1) Start-> program->microsoft SQL Server 2005->SQL Server 2005 peripheral configuration, click on the "Perimeter of Service Connection Configuration" in an open interface, and locate the database in an open interface Engine, click Services, see if it is started on the right, or click "Start" if it is not started, and make sure the "Startup Type" is automatic, not manual, otherwise start manually on the next boot;

(2) Open: Start-> program->microsoft SQL Server 2005-> Configuration Tool->sql Server Configuration Manager, select SQL Server 2005 Service Server (MSSQLServer) and click the "Start Service" button in the toolbar to change the service status to start;

When you use both of these methods, sometimes you may get an error at startup, and you will need to see if the VIA is enabled in the SQL Server 2005 Network Configuration->mssqlserver protocol in SQL Server 2005 Configuration Manager if Enabled, it is prohibited. And then do one of these things.

2. Whether remote connections have been allowed. This section can be easily divided into 4 areas, namely enabling remote connections on SQL Server, enabling SQL Server Browsing service, creating exceptions for SQL Server 2005 in Windows Firewall, and "SQLBrowser" in Windows Firewall Build an exception. Here are a few specific ways to operate:

Enable remote connections on a SQL Server instance

1. Point to start-> program->microsoft SQL Server 2005-> Configuration tool->sql Server perimeter Application Configurator

2. On the SQL Server 2005 Perimeter Configuration page, click the perimeter application configurator for services and connections

3. Then click to expand Database engine, select remote connections, and on the right, select local and remote connections.

Then select the protocol you want to use, where you should enable the TCP/IP and Named Pipes service! Click Apply, and you will see the following message:

"The changes to the connection settings will not take effect until the Database engine service is restarted. ", click OK to return

4. Expand the database engine, select Services, click Stop on the right, and wait until the MSSQLServer service stops,