【正文】 erver 實(shí)例的計(jì)算機(jī)的 IP 地址相應(yīng)的條目。 測(cè)試連接到 SQL Server 實(shí)例的不同方法 當(dāng)你連接到 SQL Server 實(shí)例時(shí)，如果遇到了連接問題，可以使用下面的一種或多種方法來解決連接問題。指定的應(yīng)用程序可能自動(dòng)地連接到使用唯一可用連接的 SQL Server 實(shí)例，從而安裝不成功。有時(shí)， Web 服務(wù)器和 JDBC 驅(qū)動(dòng)程序也會(huì)嘗試連接到 SQL Server 實(shí)例。 2. 嘗試使用其他 Windows 帳戶或 SQL Server 登錄帳戶連接到 SQL Server 實(shí)例。username39。null39。要使用 Tel 程序，在命令提示符下運(yùn)行下列命令： Tel IP Address Port Number 如果 Tel 程序沒有成功，并且你接收到錯(cuò)誤信息，請(qǐng)解決此錯(cuò)誤然后嘗試再次連接。例如，安裝一個(gè)軟件可能會(huì)覆蓋一些 MDAC 文件或更改權(quán)限，而你需要這些權(quán)限才能訪問 MDAC 文件。如果端口正被其他應(yīng)用程序使用，或者如果你正在嘗試使用一個(gè)錯(cuò)誤的 IP 地址進(jìn)行連接，就可能會(huì)出現(xiàn)此問題。 注意 ：在 Microsoft 數(shù)據(jù)存取部件 (MDAC) 的早期版本中，客戶端網(wǎng)絡(luò)實(shí)用程序的用戶界面是不同的。 b. 指向 “Microsoft SQL Server”，然后單擊 “客戶端網(wǎng)絡(luò)實(shí)用程序 ”。 4. 在命令提示符下，運(yùn)行下列命令（此處的 IP address 就是你在步驟 3 中記錄的 IP 地址）： ping –a IP address 確認(rèn)指令跟正確的服務(wù)器名字解決。因此，讓一個(gè)客戶端對(duì)一部服務(wù)器計(jì)算機(jī)連接，客戶端一定使用一個(gè)客戶端網(wǎng)絡(luò)庫，該網(wǎng)絡(luò)庫匹配與 SQL Server 實(shí)例正在使用的服務(wù)器網(wǎng)絡(luò)庫之一 。 舉例來說，如果你想要使一個(gè)客戶申請(qǐng)能夠與通過 TCP/IP的一個(gè) SQL Server的特定例證溝通 , 客戶 TCP/IP套接字網(wǎng)絡(luò)控件庫 () 一定配置成在客戶計(jì)算機(jī)上對(duì)伺候器連接。username39。 1 附錄 B 外文資料與中文譯文 B1 外文資料 How to troubleshoot connectivity issues in SQL Server 2021 Chris Tull, Microsoft Help and Support This article can help you to resolve connectivity problems with Microsoft SQL Server 2021. This article contains descriptions of mon connectivity problems and the steps that you can take to help resolve your connectivity problems. SQL Server 2021 supports several methods of munication between the instance of SQL Server and the client applications. If your client application and the instance of SQL Server reside on the same puter, Microsoft Windows interprocess munication (IPC) ponents, such as local named pipes or the Shared Memory protocol, are used to municate. However, when the client application and the instance of SQL Server reside on different puters, a work IPC, such as TCP/IP or named pipes, is used to municate. SQL Server 2021 uses NetLibrary, a DLL, to municate with a particular work protocol. A matching pair of NetLibraries must be active on the client puter and the server puter to support the work protocol that you want to use. For example, if you want to enable a client application to municate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets NetLibrary () must be configured to connect to the server on the client puter. Likewise, the server TCP/IP Sockets NetLibrary () must listen on the server puter. In this scenario, the TCP/IP protocol stack must be installed on both the client puter and the server puter. After you install SQL Server 2021, you can configure the properties of the client NetLibraries by using Client Network Utility. You can configure the properties of the server NetLibraries by using Server Network Utility (). The server NetLibraries are installed during the installation of the server tools in SQL Server Setup. However, some of the server NetLibraries may not be active. By default, SQL Server 2021 enables and listens on TCP/IP, named pipes, and Shared Memory. Therefore, for a client to connect to a server puter, the client must connect by using a client NetLibrary that matches one of the server NetLibraries that is currently being used by the instance of SQL Server. For additional information about SQL Server munication ponents and NetLibraries, see the following topics in SQL Server Books Online: ? Communication Components ? Client and Server NetLibraries ? Managing Clients Troubleshoot connectivity issues 2 Most of the connectivity issues that you may notice in SQL Server 2021 occur because of problems with TCP/IP, Windows authentication, or a bination of TCP/IP and Windows authentication. Important Before you start to troubleshoot connectivity issues in SQL Server 2021, make sure that the MSSQLServer service is started on the puter that is running SQL Server. Verify your DNS settings The name resolution process in Domain Name System (DNS) is used to resolve the IP address to the name of the instance of SQL Server. If the name resolution process does not work correctly, the instance of SQL Server is not reachable, and you may receive one or more of the following error messages: SQL Server does not exist or access denied General Network Error Cannot Generate SSPI Context To verify that the name resolution process is resolving the correct server, you can ping the server by using the server name and the IP address of the server. To do so, follow these steps: 1. Click Start, and then click Run. 2. In the Run dialog box, type cmd in the Open box, and then click OK. 3. At the mand prompt, run the following mand: ping Server Name Note the IP address that is returned. 4. At the mand prompt, run the following mand (where IP address is the IP address that you noted in step 3): ping –a IP address Verify that the mand resolves to the correct server name. If either of the specified mands are not successful, time out, or do not return the correct values, the DNS lookup is not working correctly or the problem occurs because of other working or routing issues. To see your current DNS settings, run the following mand at a mand prompt: ipconfig /all To work around this problem, add an entry for the server to the %systemroot%\system32\drivers\etc\hosts file on the client puter. You can also work around the problem by connecting to the server by using the Named Pipes Netlibrary. Verify the enabled protocols and aliases Connectivity problems may occur if the alias on the client puter is set incorrectly. You can view the aliases by using Client Network Utility. To do so, follow these steps: 1. Start Client Network Utility. If the SQL Server client tools are installed on the puter that is running the client application, follow these steps to start Client Network Utility: a. Click Start, and then point to Programs. b. Point to Microsoft SQL Server, and