机械毕业设计英文外文翻译419如何解决 SQL Server 中的连接问题Word文件下载.docx

1、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

2、 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-Lib

3、rary 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-Lib

4、raries Managing ClientsTroubleshoot connectivity issuesMost of the connectivity issues that you may notice in SQL Server 2000 occur because of problems with TCP/IP, Windows authentication, or a combination of TCP/IP and Windows authentication. Important Before you start to troubleshoot connectivity

5、issues in SQL Server 2000, make sure that the MSSQLServer service is started on the computer that is running SQL Server.Verify your DNS settingsThe 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

6、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 deniedGeneral Network ErrorCannot Generate SSPI ContextTo verify that the name resolution process is resolving the correct

7、 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 command prompt, run the following command:ping Note the IP addre

8、ss that is returned.4. At the command prompt, run the following command （where IP address is the IP address that you noted in step 3）:ping a Verify that the command resolves to the correct server name. If either of the specified commands are not successful, time out, or do not return the correct val

9、ues, 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 /allTo work around this problem, add an entry for the server to the %systemroot%system32d-riverse

10、tchosts file on the client 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 aliasesConnectivity problems may occur if the alias on the client computer is set incorrectly. You can view the aliases by using

11、 Client Network Utility. To do so, follow these steps:1. 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 Client Network Utility:a. Click Start, and then point to Programs.b. Point to Micros

12、oft SQL Server, and then click Client Network Utility.If the SQL Server client tools are not installed on the client computer, follow these steps to start Client Network Utility:a. Click Start, and then click Run.b. In the Run dialog box, type cliconfg in the Open box, and then click OK.2. In the SQ

13、L Server Client Network Utility window, click the General tab, and then enable all the protocols that you want to use.Note You must at least enable the TCP/IP protocol and the named pipes protocol.3. Click the Alias tab, and then verify the aliases that are configured for the instance of SQL Server.

14、 4. Verify the properties of the aliases to make sure that the server name or IP address and the protocol are configured correctly.You can create a new alias to test the connectivity by using the server name, the IP address, or even by using a different protocol.Note Earlier versions of Microsoft Da

15、ta 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 computer that is running the client application.Verify that the instance of SQL Server is listening

16、 correctlyTo 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 SQL Server error log file may contain entries that are similar to the following:2003-11-06 09:49:

17、36.17 server SQL server listening on TCP, Shared Memory, Named Pipes. 2003-11-06 09:36.17 server SQL server listening on 192.168.1.5:1433, 127.0.0.1:1433.If you analyze the entries in the SQL Server error log file, you can verify that the instance of SQL Server is listening on the correct IP address

18、 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 and to change the properties in SQL Server, including the protocols that can connect to SQL Server and the ports tha

19、t 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 port 1433 or any other specified port. This problem may occur if the port is being used by another application or if

20、 you are trying to connect by using an IP address that is not correct. Therefore, the TCP/IP connections to SQL Server may not be successful and you may receive the following error message in the SQL Server error log file:2001-11-14 15:14.12 server SuperSocket Info: Bind failed on TCP port 1433.If y

21、ou 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 command prompt to obtain information about the ports that are in use:NETSTAT anYou can also use the Portqry command-line uti

22、lity 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 port. Therefore, when you start the named instance of SQL Server, SQL Server tries to listen on the port that was previousl

23、y being used. If SQL Server cannot bind to that port, the named instance may dynamically bind to a different port. In that situation, make sure that the client application is also set to determine the port dynamically. Alternatively, you can also specify a static port for the named instance to bind

24、to and to listen on by using Client Network Utility.Troubleshoot MDAC IssuesConnectivity problems may also occur because of problems with MDAC. For example, a software installation may overwrite some of the MDAC files or change the permissions that you must have to access the MDAC files. You can run

25、 the MDAC Component Checker to verify the MDAC installation on your computer. Note If you are connecting to a named instance of SQL Server, make sure that you are running MDAC 2.6 or later on your computer. Earlier versions of MDAC do not recognize named instances of SQL Server. Therefore, connectio

26、ns to named instances may not be successful.You can use the Odbcping.exe utility to verify connections through the SQL Server ODBC driver.You can also test connectivity to the instance of SQL Server by using a .udl file.Troubleshoot firewall issuesIf firewall exists between the client computer and t

27、he computer that is running SQL Server, make sure that the ports that are required to communicate through the firewall are open.If you use the TCP/IP protocol to connect to the instance of SQL Server, make sure that you can use the Telnet program to connect to the port where SQL Server is listening. To use the Telnet program, run the following command at a command prompt:Telnet If the Tel