Sql2005:
Open sql2005's configuration tool --> SQL Server 2005 peripheral application configurator --> service and connected peripheral application configurator --> database engine --> remote connection, select the local connection and remote connection, and use TCP/IP and named pipes at the same time.
(Appendix: how to configure SQL Server 2005 to allow remote connection: http://support.microsoft.com/kb/914277/zh-cn)
Sql2008:
Open SQL Server Management studio --> select the first item (master database engine) in [object Resource Manager] on the left) --> right-click --> aspect --> select [peripheral application configurator] From the aspect drop-down list --> set remotedacenable to true.
In addition:
If XP has a firewall, add the following two to the exception:Program:
C: \ Program Files \ Microsoft SQL Server \ mssql.1 \ MSSQL \ binn \ sqlservr.exe,
C: \ Program Files \ Microsoft SQL Server \ 90 \ shared \ sqlbrowser.exe
Sql2005:
Open sql2005's configuration tool --> SQL Server 2005 peripheral application configurator --> service and connected peripheral application configurator --> database engine --> remote connection, select the local connection and remote connection, and use TCP/IP and named pipes at the same time.
(Appendix: how to configure SQL Server 2005 to allow remote connection: http://support.microsoft.com/kb/914277/zh-cn)
Sql2008:
Open SQL Server Management studio --> select the first item (master database engine) in [object Resource Manager] on the left) --> right-click --> aspect --> select [peripheral application configurator] From the aspect drop-down list --> set remotedacenable to true.
In addition:
If XP has a firewall, 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