Remote connection to port SQL 2000 cannot be achieved

Follow the practices in the following articles to finally solve the problem. The patch for SQL SP4 was not installed.

 

1. SQL2000 telnet port 1433 cannot connect to, and 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 1433 of Telnet SQL Server 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 1433 is being monitored? 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 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.

Remote connection to SQL Server 2000 Server Solution

Solution steps:
Check whether the IP address of the ping server can be pinged.
This is to see whether the physical connection to the remote SQL Server 2000 Server exists. If not, check the network and view 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 you have any questions, this step will usually be asked.
Question. The common prompt is "... Unable to open the 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.
2. Check whether the TCP/IP protocol is enabled on the server. This Protocol is required for remote connection (over the Internet. The check method is: on the server
Choose Start> program> Microsoft SQL Server> server network utility to check whether the enabled Protocol has the TCP/IP protocol. If
No, enable it.
3. Check whether the server's TCP/IP Port is configured as port 1433. View the TCP/IP in the enabled protocol in the server network utility
Ensure 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 configured with the server
The port number must be the same. If the "Hide server" check box is selected, the client cannot view the server by enumerating the server,
But does not affect the connection, but the default port of TCP/IP protocol is implicitly changed to 2433.
Changes.
4 if the server operating system has been patched with SP2, you must configure Windows Firewall to open port 1433 to it.
You can directly turn off the Windows Firewall (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 in
Enter netstat-a-n or netstat-an in the DoS or command line of the server to check whether TCP 127.0.0.1 is similar
1433 listening. If not, you usually need to patch SQL Server 2000 with at least SP3. In fact, start the query on the server side
Analyzer, enter select @ version to execute and you will see the version number. All Versions earlier than 8.0.2039 must be patched.
If there is no problem above, then you can perform the telnet server IP 1433 test. The screen will flash and the cursor will not stop flashing in the upper left corner. Gong
Hi, you can now connect to the Enterprise Manager or query analyzer.

3. Check client settings
Program> Microsoft SQL Server> client network tools. Make sure that the client TCP/IP protocol is the same as in the server network utility.
Enabled, and the default port is 1433 (or other ports, consistent with the server side ).

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
Step-> write the login name and password (SA, password)-> next-> complete
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
The 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-> log on
Enter a large number in the box after the recording timeout (seconds)
Query analyzer-> tool-> Option-> connection-> enter a large number in the box after logon timeout (seconds)
Generally, you can connect to IOT platform. If an error is prompted, proceed to the next step.
Five errors are usually caused by SQL Server's "Windows only" authentication method, so you cannot use SQL Server's
Log on to the Account (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 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, Net start
MSSQLServer is also a quick way to start the service ).

Note: When connecting to the local server, the named pipe protocol is usually used (you can see in the server network utility that the enabled protocol has this)
The default port is 445. Therefore, local connectivity cannot be explained. connecting to a remote server is a completely different protocol ).