SQL Server外文文献及翻译 第5页
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 SQL 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.
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 Data Access Components (MDAC) have a different user interface for Client Network Utility. 辣,文-论'文.网
http://www.751com.cn 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:36.17 server SQL server listening on TCP, Shared Memory, Named Pipes. 2003-11-06 09:49: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 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 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 port 1433 or any other specified port. This problem may occur if the port is being used by another application or if 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: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 command 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 port. Therefore, when you start the named instance of SQL Server, SQL Server tries to listen on the port that was previously 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 to and to listen on by using Client Network Utility.
Troubleshoot MDAC Issues
Connectivity 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 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, connections 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 issues
If firewall exists between the client computer and the 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 <IP Address> <Port Number>
If the Telnet program is not successful and you receive an error message, resolve the error and then try to connect again.
Note Because of issues that were caused by the Slammer virus, the User Datagram Protocol (UDP) port 1434 may be blocked on your firewall.
Troubleshoot authentication and security issues
Connections to SQL Server may not be successful because of authentication failures. If the authentication fails, you may receive one of the following error messages:
Login failed for user '<username>'
Login failed for user 'NTAUTHORITY\ANONYMOUS LOGON'
Login failed for user 'null'
If you receive an error message because of an authentication failure and the error message does not mention a specific SQL Server login name, troubleshoot the problem with Windows authentication. You may receive the following error message because of problems with Windows authentication:
Cannot generate SSPI Context
The following problems may cause authentication and security issues:
• Problems occur with NTLM authentication or with Kerberos authentication.
• The domain controller cannot be contacted because of connectivity issues.
• Problems occur with trust relationships across domains.
For more information about possible causes, see the event logs on the computer. To work around connectivity problems with Windows authentication, you can use SQL Server Authentication to connect to the instance of SQL Server.
If the connection is not successful when you use SQL Server Authentication, you receive the following error message:
Login failed for user '<辣,文-论'文.网
http://www.751com.cn these steps.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
1. Make sure that the instance of SQL Server is configured to use Windows authentication and SQL Server Authentication. To do so, make sure that the following registry keys are on the computer that is running SQL Server. For the default instance of SQL Server:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer\LoginMode
For the named instance of SQL Server:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer\LoginMode
Make sure that the following registry key values are set:
Authentication type Value
Windows authentication only 1
Mixed mode (SQL Server Authentication and Windows authentication) 2
Note If you make any changes to the registry, you must stop and then restart the instance of SQL Server for the changes to take effect.
2. Try to connect to the instance of SQL Server by using different Windows accounts or SQL Server login accounts. This can help determine if the connection is not successful because of problems with a particular login account. For example, the password of the login account may have been changed.
上一页 [1] [2] [3] [4] [5] [6] 下一页
SQL Server外文文献及翻译 第5页下载如图片无法显示或论文不完整，请联系qq752018766
