Telnet port 1433 is unavailable

For some Telnet faults, we sometimes encounter port problems. We have mentioned that Telnet port 1433 does not know whether you are still impressed. Here we will discuss some problems related to this port. See how to solve the problem that port 1433 cannot be opened.

1. The database service is not started.

2. the firewall shields the telnet response.

3. the SQL service does not start listening on port 1433.

If you can use the query analyzer to connect to the server, the application software can connect to the server, but Telnet port 1433 fails, and the service port has not been changed. The other operations are normal, this problem is most common in XP2 + SQL SERVER 2000 environments. there are several solutions:

1. Install the XP2 patch instead, so that the SQL SERVER cannot be connected normally.

2. Install the SP3 patch of SQL SERVER 2000 in the XP2 operating system to solve the problem that port Telnet 1433 cannot be opened.

3. For other operating systems such as 2003, it is best to supplement SQL SP4.

Check whether your SQL has been patched. If not, install a patch. You can run the patch in the query Analyzer:

Select @ version

If the version is 8.00.2039 or earlier, it indicates that you have not installed the sp4 patch.

SQL patch download:

Positions of All Patches

Http://www.microsoft.com/downloads/details.aspx? FamilyId = 8e2dfc8d-c20e-4446-99a9-b7f0127f8bc5 & displaylang = zh-cn

Which of the following statements should be installed?

Http://download.microsoft.com/download/9/ B /f/9bff6646-2cdb-4069-ada0-548be9cb9338/SQL2000-KB884525-SP4-x86-CHS.EXE

Note that after downloading the package, decompress the package and execute setup. bat in the decompressed directory.

If your operating system is xp, you must install xp sp2 again no matter whether or not SQL sp4 has been installed before and enable port 1433 in the firewall, otherwise, it cannot be accessed by other computers.

How do I check whether Telnet port 1433 is listening? Or check which ports are listening?

1. If SQL sp3 is enabled and Windows Firewall is disabled, run

Netstat-na should be able to see tcp 1433 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.

Original article: http://hi.baidu.com/whsjsoft/blog/item/66d5fb50eebce6581038c289.html