How to turn on 1433 port resolution

This article is mainly for Win2003 system installation SQL Sever2000 after the 1433 port is not open, how to open the 1433 port solution.

A few years of Windows2003 and SQL Server2000, but this problem is the first encounter. Recently debugging a Jsp+sql2000web program encountered a phenomenon, the Win2003 Simplified Chinese Server version of the SQL Server2000 installed, the default installation, everything is OK, but after the installation is complete Tomcat runs normally, the JSP program is unable to connect SQL2000 database , look at the port, 1433 ports actually not open, certainly not to mention remote connection. The general analysis is this: 1, the SQL Server service does not start, check service startup, restart service failure is still. 2, modified the port number, open the Network Utility, check the protocol enabled TCP/IP protocol, view port, is 1433 yes. 3, the client utility has been changed; Open Client utility, check protocol port OK, re-create an alias, still not. 4, installation problems; suspect installation steps are problematic. So unloading load, all default, fault remains. 5, the installation version of the problem; View the installation CD, is a proven installation disk, should not have problems. 6, the problem of the system, also do not see any other problems, is it a systemic problem? But re-install the system can be too troublesome, or first think of other ways to see if you can find the problem. Check the system log, this should be a better habit. After careful re-installation of the log, impressively found the following: You are running a Microsoft SQL Server 2000 version or Microsoft SQL Server Edition Desktop Engine (also known as MSDE) and Microsof There are known security weaknesses in the use of the Windows Server 2003 family. To reduce the computer being attacked by certain viruses, the TCP/IP and UDP network ports for Microsoft SQL Server 2000,MSDE or both are disabled. To enable these ports, you must be from www.microsoft.com/sql/downloads/default.asp or www.microsoft.com/china/sql/downloads/default.asp You install a hotfix, or the latest service pack for Microsoft SQL Server 2000 or MSDE. Http://www.microsoft.com/downloads/details.aspx?familyid=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&dispLaylang=en For more information, see Help and support at go.microsoft.com/fwlink/events.asp finally found the problem, it turned out to be a small security concern for Windows. Then why did not meet before, the original used to secure the person, after the installation of SQL, before use will be sure to repair the vulnerability, so has not been aware of this problem. It seems that what kind of habits will have some drawbacks! Since the problem is easy to find, immediately to the Microsoft website: http://www.microsoft.com/downloads/details.aspx? Displaylang=zh-cn&familyid=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5

Download SP4 "Database Components (download files: sql2000-kb884525-sp4-x86.exe)" After installing SQL Server SP4, the browser address bar tests www.ITstudy.cn everything is OK.

Attached: Solution for remote connection to SQL Server 2000 Server

Solution Step: A look at ping server IP can ping pass. This is actually to see if the physical connection to the remote SQL Server 2000 Server exists. If not, check the network to see the configuration and, of course, make sure that the IP of the remote SQL Server 2000 server is spelled correctly. II Enter the Telnet server IP port under DOS or command line to see if it can be connected. For example, Telnet 202.114.100.100 1433 typically has a port value of 1433, because 1433 is the default listening port for TCP/IP for SQL Server 2000. If there is a problem, this step usually goes wrong. The usual hint is "... Unable to open connection, connection failed. " If there is a problem with this step, you should check the following options. 1 Check whether the remote server started the SQL Server 2000 service. If not, it starts. 2 Check that the TCP/IP protocol is not enabled on the server side because remote connections (via the Internet) require this protocol. The check method is to open the Start menu, the program->microsoft SQL server-> Server Network Utility on the server, to see if there is a TCP/IP protocol in the enabled Protocol, and if not, enable it. 3 Check that the TCP/IP port of the server is configured as 1433 port. In the Server Network Utility, check the TCP/IP properties in the Enable protocol, make sure the default port is 1433, and the Hide server check box is not checked. In fact, if the default port is modified, it is also possible, but when the client does the Telnet test, the server port number must be the same as the port number configured by the server. If the Hide Server check box is checked, it means that the client cannot enumerate the server to see this server, but does not affect the connection, but the TCP/IP protocol default port will be implicitly modified to 2433, when the client connection must be changed accordingly. 4 If the server-side operating system has SP2 patch, you have to configure the Windows Firewall, to open 1433 ports to it, usually in the test can be directly shut down the Windows Firewall (the other firewall is also turned off the best). 5 Check if the server is listening on port 1433. If the server is not listening on port 1433 on a TCP connection, it is not connected. The check method is to enter Netstat-a-N or Netstat-an under the DOS or command line of the server, and see if there are items like TCP 127.0.0.1 1433 listening in the results list. If not, you will typically need to make at least SP3 patches to SQL Server 2000.In fact, start the Query Analyzer on the server side, enter the SELECT @ @version can see the version number, the version number in 8.0.2039 or less needs to be patched. If the above is not a problem, then you do telnet server IP 1433 test, you will see the screen flash after the cursor is flashing in the upper left corner. Congratulations, you can start right away. The Enterprise Manager or Query Analyzer is connected.

Three check the client setup program->microsoft SQL server-> Client Network usage tool. As in the server Network Utility, make sure that the client TCP/IP protocol is enabled and that the default port is 1433 (or another port that is consistent with the server side).

Four in Enterprise Manager or Query Analyzer connection Test Enterprise Manager, right-click SQL Server Group, new SQL Server enrollment--next--write remote ip-> Next, click SQL Server Login--Next Step-by-write login name and password (sa,password), next to file-and-password (s)--write remote ip-> write logins and Passwords (Sa,password)- > OK is usually recommended in Query Analyzer because by default the timeout setting for registering another SQL Server through Enterprise Manager is 4 seconds, and the Query Analyzer is 15 seconds. To modify the default connection time-out: In the SQL Server Enterprise Manager Properties window that pops up with options, tools, Enterprise Manager, click Enter a larger number in the box after login time-out (seconds) on the Advanced tab, connection settings Connection, tools----Tool, Query Analyzer, and so on, enter a larger number in the box after login timeout (seconds), and then go to the next step if you are prompted with an error. The five errors occur because SQL Server uses Windows-only authentication so that users cannot connect using SQL Server's logon account, such as SA. 　　The workaround is as follows: 1 Use Enterprise Manager on the server side, and select Use Windows authentication to connect on SQL Server. 　　2 Expand SQL Server Group, right-click the name of your SQL Server server, select Properties, and then select the Security tab. 　　3 under Authentication, select SQL Server and Windows. 4 Restart the SQL Server service. (under DOS or command line, net stop MSSQLSERVER stop service, net start MSSQLServer start service, is also a quick method).

Note: When connecting to a local server, it is common to use the named pipe protocol (which can be seen in the Server Network Utility), the default port is 445, so the local connectivity is not an indication of the problem, the connection to the remote server is a completely different protocol.

How to turn on 1433 port resolution