Home > database >  The local machine, SQL server, remote connection virtual machine through the virtual machine IP remo
The local machine, SQL server, remote connection virtual machine through the virtual machine IP remo

Time:09-26

Hosting the SQL server default port changed to 1488, the virtual machine's default port is 1433
Stated all of my first try to plan:
1. Using navicat, through url IP + 1433 ports to connect to the virtual machine is hosting the SQL server
2. Using navicat, virtual machine via the url hostname + instance name + 1433 port to connect to the virtual machine is SQL server
3. Using navicat, virtual machine via the url hostname + instance name, do not add port to connect to the virtual machine is SQL server
4. Using navicat, via the url hosting IP + 1433 port is connected to the host machine of SQL server
5. Using navicat, via the url hosting IP + 1488 ports to connect to is hosting the SQL server
6. Java programs using the url of the scheme 1, the operation is hosting the SQL server
7. Java programs using the url of the scheme 2, an error is as follows:
Com. Microsoft. Essentially, JDBC SQLServerException: through port 1433 Connection to a host of XXXXXXX TCP/IP Connection fails, an error: "Connection refused: connect, please verify the Connection properties, make sure that the SQL Server instance is running on the host, and TCP/IP connections at the port, but also ensure the firewall didn't stop to the port of TCP connections,"

Confirm the SQL server instance is running state, and 1433 TCP port is enabled, the firewall has been closed, the inbound rules have also been open port 1433,

8. Java programs using the url of the scheme 3, an error is as follows:
Com. Microsoft. Essentially, JDBC SQLServerException: to host the XXXXXXX named instance sqlexpress connection fails, an error: "java.net.SocketTimeoutException: Receive timed out", please verify the Server and the instance name, and check the firewall is not block to port 1434 UDP communication, but also for SQL Server 2005 or higher, to validate the SQL Server Browser service is running on the host,

Online said that the reason is that the SQL Server Browser service has not started, I confirm that has launched the