Telnet port 1433 port failure listening

The Telnet service cannot be started or connected, which directly affects our use. We have analyzed the causes of port 1433 failure in Telnet. Here we will mainly explain how to check whether 1433 is being listened? Or check which ports are listening? We hope that the content of this article will help you.

1. If SQL sp3 is enabled and the windows 2003 firewall is disabled, run netstat-na at the command prompt to check that tcp 1433 is listening.

2. Start the Enterprise Manager to view the system logs of SQL server 2000. In the log, you can see the protocols that SQL SERVER starts to wait for remote connection. remember to finish patching, restart the machine, or restart the service. solution steps for remotely connecting to the SQL server 2000 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, Telnet 202.114.100.100 1433

The port value is usually 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. generally, when Telnet port 1433 fails, the following error occurs "...... Unable to open the connection, connection failed ". If there is a problem in 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 the remote connection is over the Internet. 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, it is usually best to turn off the windows Firewall and other firewalls during testing ). 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. check whether there are items similar to tcp 127.0.0.11433 listening in the result list by entering netstat-a-n or netstat-an Under the dos or command line of the server. 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 the client's Telnet port 1433 settings

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

4. Test the connection in the Enterprise Manager or query Analyzer

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-> complete query analyzer-> file-> connection-> Write Remote IP-> write login name and password sa, password) -> it is usually recommended that you do this in the query analyzer. 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 pop-up "SQL Server Enterprise Manager properties" window, click the "advanced" tab-> connection settings-> login timeout seconds) enter a large digital query analyzer in the box below-> Tools-> options-> connection-> login timeout seconds) enter a large number in the following box to connect. If an error is prompted, proceed to the next step.

Five errors may cause port 1433 to fail over via Telnet because SQL Server uses the "Windows only" authentication method. Therefore, you cannot use the Logon account of SQL Server, such as sa, to connect to the port. 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. net stop mssqlserver to stop the service under dos or command line, and net startmssqlserver to start the service, which is also a quick method ).

Note: When connecting to the local server, the named pipe protocol is usually used. The enabled protocol is shown 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 ).