This article can help you to resolve connectivity problems with Microsoft SQL Server 2000. This article contains descriptions of common connectivity problems and the steps that you can take to help resolve your connectivity problems.
SQL Server 2000 supports several methods of communication between the instance of SQL Server and the client applications. If your client application and the instance of SQL Server reside on the same computer, Microsoft Windows interprocess communication (IPC) components, such as local named pipes or the Shared Memory protocol, are used to communicate. However, when the client application and the instance of SQL Server reside on different computers, a network IPC, such as TCP/IP or named pipes, is used to communicate.
SQL Server 2000 uses Net-Library, a DLL, to communicate with a particular network protocol. A matching pair of Net-Libraries must be active on the client computer and the server computer to support the network protocol that you want to use. For example, if you want to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net-Library (Dbnetlib.dll) must be configured to connect to the server on the client computer. Likewise, the server TCP/IP Sockets Net-Library (Ssnetlib.dll) must listen on the server computer. In this scenario, the TCP/IP protocol stack must be installed on both the client computer and the server computer.
After you install SQL Server 2000, you can configure the properties of the client Net-Libraries by using Client Network Utility. You can configure the properties of the server Net-Libraries by using Server Network Utility (Svrnetcn.exe). The server Net-Libraries are installed during the installation of the server tools in SQL Server Setup. However, some of the server Net-Libraries may not be active. By default, SQL Server 2000 enables and listens on TCP/IP, named pipes, and Shared Memory. Therefore, for a client to connect to a server computer, the client must connect by using a client Net-Library that matches one of the server Net-Libraries that is currently being used by the instance of SQL Server.
For additional information about SQL Server communication components and Net-Libraries, see the following topics in SQL Server Books Online:
• Communication Components
• Client and Server Net-Libraries
• Managing Clients



這一篇文章能幫助你解決微軟 SQL 伺候器 2000 的連接性問題。這一篇文章包含你能拿幫助解決你的連接性問題的通常連接性問題和步驟的描述。
SQL Server的例證和客戶端申請之間的溝通的 SQL Server 2000 支持一些方法。如果你的客戶申請和SQL Server的例證在相同的計算機上住, Microsoft Windows 處理之間的溝通 (IPC) 成份（像是當?shù)氐拿芑蛘弑环窒淼挠洃浻涗洠┯脕頊贤ā?然而, 當客戶端申請和SQL Server的例證在不同的計算機，網(wǎng)絡IPC（像是TCP/IP上住的時候或者命名管道）用來溝通。
SQL Sever 2000 使用網(wǎng)絡控件庫（一個DLL）與一個特別的網(wǎng)絡記錄溝通。 一雙相配網(wǎng)絡控件庫一定在客戶計算機和服務器計算機上是活躍的支援你想要使用的網(wǎng)絡記錄。 舉例來說，如果你想要使一個客戶申請能夠與通過TCP/IP的一個 SQL Server的特定例證溝通, 客戶TCP/IP套接字網(wǎng)絡控件庫 (Dbnetlib.dll) 一定配置成在客戶計算機上對伺候器連接。 同樣地, 服務器TCP/IP套接字網(wǎng)絡控件庫 (Ssnetlib.dll) 一定在伺候器計算機上聽。 在這一個情節(jié)中, TCP/IP協(xié)議堆棧一定是裝置在客戶計算機和服務器計算機。
在你安裝SQL Server 2000 之后，你能配置客戶端網(wǎng)絡的特性使用客戶端網(wǎng)絡公用程序的網(wǎng)絡庫屬性。你能配置服務器網(wǎng)絡的特性使用服務器網(wǎng)絡公用程序(Svrnetcn.exe)的網(wǎng)絡控件庫屬性。在安裝 SQL Server 安裝程序中的服務器工具期間，服務器的網(wǎng)絡庫也被同時安裝了。然而，一些服務器的網(wǎng)絡庫可能不是激活的。如此，SQL Server 2000 啟用并偵聽 TCP/IP、命名管道和共享內(nèi)存。因此，讓一個客戶端對一部服務器計算機連接，客戶端一定使用一個客戶端網(wǎng)絡庫，該網(wǎng)絡庫匹配與SQL Server實例正在使用的服務器網(wǎng)絡庫之一。
對于關于SQL Server通訊部件和網(wǎng)絡庫的其它信息，請參見“SQL Server 在線參考書”中的下列主題：
• 通信部件
• 客戶端和服務器網(wǎng)絡庫
• 管理客戶端