"reprint" SQL Server LAN Access failure reason

http://xwqlzjtu.blog.163.com/blog/static/124185339201172354655857/

In project development, it is common for LAN to simulate remote access SQL Server database, but always fail. Strangely, there is no problem with the computers deployed on site, so why not the machines in development?

This is true: on-site development of the machine installed in the deployment environment without any system optimization, so the installation of SQL Server services are turned on by default, SQL Server on the development machine only open the data service, the other services are not turned on by default. Here's why--the SQL Server Browser service is not turned on. The SQL Server Browser service provides the instance name and version number for each instance of the database Engine and SSAS. So without opening the SQL Server Browser service, SSMS will not be able to find other instance names in LAN. Create an exception for SQL Server 2005 in Windows Firewall

1. In the Windows Firewall Settings screen, select the Exceptions tab, and then click Add Program
2. In the Add Program window, click Browse
3. Then find "C:/programfiles/microsoft files/microsoft SQL Server/mssql.1/mssql/binn/sqlservr.exe",
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.
4. 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
1. In the Windows Firewall Settings screen, select the Exceptions tab, and then click Add Program
2. In the Add Program window, click Browse
3. Then find "C:/programfiles/microsoft files/microsoft SQL Server/90/shared/sqlbrowser.exe",
Click "OK" to return