[SQL] for "unable to connect to the remote SQL Server database using TCP/IP protocol"

To solve the problem of "unable to connect to the remote SQL Server database using the TCPIP protocol", it is important to determine your SQL Server version and the patches it has installed. If the Patch Is Not Installed or the latest ServicePack is not installed, install it first. Then, you can try telnetSqlServerName1433 to see if it can be connected.

It is important to determine your SQL Server version and the patches it has installed for the problem of "unable to connect to the remote SQL Server database using TCP/IP protocol. If the Patch Is Not Installed or the latest ServicePack is not installed, install it first. Then, try telnet SqlServerName 1433 to see if it can be connected.

"Unable to connect to the remote SQL Server database using TCP/IP protocol"

First, it is important to determine your SQL Server version and the patches it has installed. If the Patch Is Not Installed or the latest ServicePack is not installed, install it first.

Then, try telnet SqlServerName 1433 to see if it can be connected. 1433 is the default port for SQL Server to use the TCP/IP protocol. If you cannot connect to this port, check the network configuration.

3rd. The error description you get is "[TCP/IP Sockets] General network error". Can I use the Named Pipe for connection?

4th. If your program uses a connection string to connect to the database, try using the IP address of the database server and the HostNetBIOS name?

Finally, what is the running identity of the Program on the abnormal server used to execute the connection to SQLServer? Can this identity access remote resources? In addition, if your SQLServer machine is started before or after your domain controller is started, can SQLServer successfully verify your running identity? We recommend that you restart your SQLServer to ensure that it can obtain domain account information from the domain controller. I once had an SQLserver server. Due to power failure, the domain controller was not started, but only the SQLServer machine was started. At this time, access to SQlServer was extremely abnormal.

Trackback: http://tb.blog.csdn.net/TrackBack.aspx? PostId = 78209