JDBC connection to SQL Server 2000 port 1433 error Solution

If you encounter Error establishing socket when testing the connection to SQL Server 2000 JDBC:
Run the CMD command netstat to check the port 1433 (which is the default port and may be occupied. You can reset a new port), but it is not opened yet, first, check whether your server has been opened. If all the servers are open, it means that you have not installed the SQL SP3 or SP4 patch.
There is another way to see if you want to patch, that is, to see your version number:
You can view the version of MSSQL in the following ways:
Open Enterprise Manager> Tools> SQL query analyzer> help> about
View the detailed version number of MSSQL
If it is 8.00.194, no patch is installed.
8.00.760 is SP3.
8.00.2039 is SP4
If your version number is correct, but netstat does not check port 1433, your port 1433 may be occupied. You can change the port number.
The port change method is as follows: 1. Open the Enterprise Manager and list some database servers in the console root directory> Microsoft SQL servers> SQL Server group.
2. Right-click the database server we want to connect to, select properties, and click network configuration on the General tab to bring up a new window.
3. In the enabled Protocol area, select TCP/IP and click Properties. A new window is displayed. In this window, you can set the default network protocol. The default port is 1433.
There is another online method for your reference:
Such as running Program If the error "Error establishing socket" occurs, perform the following debugging:
1. Check whether SQL Server allows remote access. Specific steps:
1) Open "Enterprise Manager", open the console root directory> SQL Server group> Database
2) Right-click the corresponding "Database" and select "attribute"
3) Select the connection tab and check whether the RPC service is selected under remote server connection.
2. Use the Telnet IP address 1433 to check whether the system prompts a connection error. If the system prompts an error
Check whether the firewall shields the network access port of SQL Server or Java ide
If yes, disable the firewall and restart SQL Server and Java IDE for testing,
If the system still prompts the preceding error, perform the following steps:
3. Check the SQL server port number and whether the TCP/IP protocol is enabled. The procedure is as follows:
1) Open "Enterprise Manager", open the console root directory> SQL Server group> Database
2) Right-click the corresponding "Database" and select "attribute"
3) Select the "General" tab and click "network configuration". If no "TCP/IP protocol" is added to the enabled protocol
4) Select "TCP/IP protocol" and click "properties" to check whether the port number is 1433.
5) If the port number is 1433, change it to another port number, modify the JDBC connection statement, and change the port number to the newly enabled port number, such as JDBC: Microsoft: sqlserver: // SERVER_NAME: 1400 (assuming the new port number is 1400)
You can try each of the following methods:
# Check whether the SQL server connection is full.
# For authentication issues.
Go to SQL audit ice Manager> specify server> content> Security.
Change verification to SQL Server and windows.
# Click Properties to check whether the port is correct.
# Run % mssql_home % \ 80 \ tools \ binn \ svrnetcn.exe
Enable TCP/IP.
# Disable the firewall.
# Update SQL Server to SP3:
Http://www.microsoft.com/ SQL /downloads/2000/sp3.asp
After my verification, it is generally easy to upgrade to SP3!