计算机专业外文翻译--- 如何解决SQL Server 2000中的连接问题

《计算机专业外文翻译--- 如何解决SQL Server 2000中的连接问题》由会员分享，可在线阅读，更多相关《计算机专业外文翻译--- 如何解决SQL Server 2000中的连接问题（14页珍藏版）》请在毕设资料网上搜索。

1、How to troubleshoot connectivity issues in SQL Server 2000 Chris Tull, Microsoft Help and Support 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 reso

2、lve 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) componen

3、ts, 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 ditTerent computers. a neiwork IPC, such as TCP/IP or named pipes, is used to communicate. SQL Server 2000 uses Net-Library, a DLL, to c

4、ommunicate 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 S

5、erver 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 install

6、ed 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 se

7、rver Net-Libraries are installed during the installation of the server tools in SQL Servef 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 com

8、puter, 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 O

9、nline: . Communication Components . Client and Server Net-Libraries . Managing Clients Troubleshoot connectivity issues Most of the connectivity issues that you may notice in SQL Server 2000 0ccur because of problems with TCP/IP, Windows authentication, or a combination of TCP/IP and Windows authent

10、ication. 8 Important Before you start to troubleshoot connectivity issues in SQL Server 2000, make sure that the MSSQLServer service is started on the computer that is running SQL Server. Verify your DNS settings The name resolution process in Domain Name System (DNS) is used to resolve the IP addre

11、ss 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 Co

12、ntext To verify that the name resolution process is resolving the correct server, you can ping the server by using the server name and the lP 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

13、. 3. At the command prompt, run the following command: ping Note the lP address that is returned. 4. At the command prompt, run the following command (where IP address is the lP address that you noted in step 3): ping -a Verify that the command resolves to the correct server name. If either of the s

14、pecified commands 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 networking or routing issues. To see your current DNS settings, run the following command at a command prompt: ipconfig /all To work aro

15、und this problem, add an entry for the server to the %systemroot%system32driversetchosts file on the clienr computer. You can also work around the problem by connecting to the server by using the Named Pipes Net-library. Verify the enabled protocols and aliases Connectivity problems may occur if the

16、 alias on the client computer is set incorrectly. You can view the aliases by using Client Network Utility. To do so, follow these steps: l. Start Client Network Utility. If the SQL Server client tools are installed on the computer that is running the client application, follow these steps to start

17、Client Network Utility: a. Click Start, and then point to Programs. b. Point to Microsoft SQL Server, and then click Client Network Utility. If the SQL Server client tools are not installed on the clieni computer, follow these steps ro start Client Network Utility: a. Click Start, and then click Run

18、. b. In the Run dialog box, type cliconfg in the Open box, and then click OK. 2. In the SQL Server Client Network Utility window, click the General tab, and ihen enable all the protocols that you want to use. Note You must at least enable the TCP/IP protocol and the named pipes protocol. 9 3. Click

19、the Alias tab, and then verify the aliases that are configured for the instance of SQL Server. 4. Verify the properties of the aliases to make sure that the server name or IP address and the protocol are configured corfectly. You can create a new alias to test the connectivity by using the server na

20、me, the lP address, Of even by using a different protocoL Note Earlier versions of Microsoft Data Access Components (MDAC) have a different user interface for Client Network Utility. Therefore, if you do not see the options that are listed in this article, install a later version of MDAC on the comp

21、uter that is running the client application. Verify that the instance of SQL Server i.s listening correctly To verify that the instance of SQL Server is listening on named pipes, TCP/IP, or another protocol that you are using at the client application, open the current SQL Server error log file. The

22、 SQL Server error log file may contain entries that are similar to the following: 2003-11-06 09:49:36.17 server SQL server listening on TCP, Shared Memory, Named Pipes. 2003-1 I -06 09:49:36. 1 7 server SQL server listening on I 92.1 68.1.5: 1433, 1 27.0.0. I : 1433. If you analyze the entries in th

23、e SQL Server erfor log file, you can verify that the instance of SQL Server is listening on the correct IP address and on the correct port. By default, a default instance of SQL Server listens on the port 1433. You can also use Server Network Utility to verify the protocol settings for SQL Server an

24、d to change the properties in SQL Server, including the protocols that can connect to SQL Server and the ports that can be used. For more information about using Server Network Utility, see the SQL Server Network Utility topic in SQL Server Books Online. Sometimes, SQL Server 2000 may not bind to po

25、rt 1433 0r any other specified porc. This problem may occur if the port is being used by another application or if you are trying to connect by using an lP address that is not correct. Therefore, the TCP/IP connections to SQL Server may not be successful and you may receive the following error messa

26、ge in the SQL Server error log file: 2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433. If you cannot connect to the instance of SQL Server by using a TCP/IP connection, try to use the named pipes protocol or the Shared Memory protocol. Run the following command at a comma

27、nd prompt to obtain information about the ports that are in use: NETSTAT -an You can also use the Portqry command-line utility to obtain more information about the ports that are in use. Note For named instances of SQL Server, SQL Server dynamically determines the port and listens on the determined

28、port. Therefore, when you start the named instance of SQL Server, SQL Server tries to listen on the port that was pfeviously being used. If SQL Server cannot bind to that port, the named instance may dynamically bind to a different port. In thai situalion, make sure ihat the client application is also set to determine the port dynamically. Alternatively, you can also specify