Port fix for Telnet server and SQL server 2000

In Telnet server applications, our administrators often log on to SQL. Here we will introduce the port conflict during Telnet to SQL server 2000. Hope to help you. First, let's take a look at the basic path to log on to the remote SQL Server.

Check whether the server IP can be pinged.

Check whether the physical connection with the remote SQL server 2000 server exists. If not, check the network and check the configuration. Of course, make sure that the IP address of the Remote SQL server 2000 server is correctly spelled.

2. Enter the IP port of the Telnet server in Dos or command line to check whether the port can be connected.

For example, Telnet202.114.100.100 1433

Generally, the port value is 1433, because 1433 is the default listening port of SQL server 2000 for TCP/IP. If there is a problem, this step usually has a problem. The common prompt is "...... Unable to open connection, connection failed ".

If there is a problem with this step, check the following options.

1. Check whether the remote server has started the SQL server 2000 Service. If not, start the service.

2. Check whether the TCP/IP protocol is enabled on the server, because remote connection (via the Internet) depends on this protocol. the check method is to open the Start menu on the Server> program> Microsoft SQL Server> Server network utility to check whether the enabled protocol contains the TCP/IP protocol. If not, enable it.

3. Check whether the server's TCP/IP Port is configured as port 1433. check the TCP/IP attribute in the enabled protocol in the server network utility, make sure that the default port is 1433, and the check box of the hidden server is not checked.

In fact, it is okay if the default port is modified, but when the client performs a telnet test, the server port number must be consistent with the port number configured on the server. if the "Hide server" check box is selected, it means that the client cannot see this server by enumerating the server, which protects the server but does not affect the connection, however, the default port of the TCP/IP protocol is implicitly modified to 2433, which must be changed when the client is connected.

4. If the operating system on the server has been patched with sp2, you must configure windows Firewall and open port 1433 to it, usually, you can turn off the windows Firewall directly during the test (Other firewalls are also the best ).

5. Check whether the server listens on port 1433. If the server does not listen on port 1433 of the tcp connection, it cannot be connected. The check method is to enter

Netstat-a-n or netstat-an. check whether there are items similar to tcp 127.0.0.1 1433 listening in the result list. if not, you usually need to patch SQL server 2000 with at least sp3. in fact, start the query analyzer on the server and enter select @ version to execute it. The version number must be patched for versions earlier than 8.0.2039.

If there is no problem above, then you do the Telnet server ip 1433 test, you will see the screen flashing, the cursor in the upper left corner constantly flashing. congratulations, you can start to connect to the Enterprise Manager or query analyzer immediately.

3. Check client settings

Program> Microsoft SQL Server> client network tools. make sure that the client TCP/IP protocol is enabled, as in the server network utility, and the default port is 1433 (or other ports, consistent with the server ).

4. In the Enterprise Manager or query the analyzer connection test

Enterprise Manager-> right-click SQlserver group-> Create sqlserver registration-> next-> Write Remote IP-> next-> select Sqlserver login-> next-> write login name and password (sa, password)-> next-> finish

Query analyzer-> file-> connection-> Write Remote IP-> write login name and password (sa, password)-> OK

It is usually recommended to do this in the query analyzer, because by default, the timeout setting for registering another SQL Server through the Enterprise Manager is 4 seconds, and the query analyzer is 15 seconds.

Modify the default connection timeout method:

Enterprise Manager-> Tools-> options-> In the displayed "SQL Server Enterprise Manager properties" window, click the "advanced" tab-> connection settings-> logon timeout (seconds) enter a large number in the following box.

Query analyzer-> tool-> Option-> connection-> enter a large number in the box after logon timeout (seconds)

Generally, the connection can be connected. If an error is prompted, proceed to the next step.

Five error occurs because SQL Server uses the "Windows only" authentication method, so you cannot use the Logon account of SQL Server (such as sa) to connect.

The solution is as follows:

1. Use the enterprise manager on the Server side and select "use Windows Authentication" to connect to SQL Server.

2. Expand "SQL Server group", right-click the name of the SQL Server, select "properties", and then select the "Security" tab.

3. Under "authentication", select "SQL Server and Windows ".

4. Restart the SQL Server service. (In dos or command line, net stop mssqlserver to stop the service, and net start mssqlserver to start the service, which is also a quick method ).

Telnet Server logon SQL Note: When connecting to the local server, the pipe naming protocol is usually used (this is enabled in the server network utility). The default port is 445, therefore, local connectivity cannot be explained. connecting to a remote server is a completely different protocol.