一般性网络错误（General network error）.docVIP

一般性网络错误（General network error） Microsoft] [ODBC SQL Server Driver] [TCPIP Sockets] general network error. The four most common errors in SQL Server connectivity: One. SQL Server does not exist or access is rejected Generally speaking, there are several possibilities: 1. Incorrect spelling of SQL Server name or IP address 2, the server-side network configuration is wrong 3. The client network configuration is wrong First, check the network physical connection Ping server IP address/server name If ping server IP address is not successful, it indicates that there is a problem with the physical connection, and then check the hardware device, such as network card, HUB, router, etc. Another possibility is that there are firewall software installed between client and Server, such as ISA Server. Firewall software may block response to ping, Telnet, etc Therefore, when checking the connection problem, we must first turn off the firewall software or open all the closed ports. If ping server IP address success, ping server name failed The name resolution has a problem, and its time to check whether the DNS service is normal. Sometimes the client and the server is not in the same local area network (LAN), then it is unlikely to directly use the server name to identify the server, then we can use the HOSTS file for name resolution, The specific method is: 1. Open the HOSTS file using notepad (usually in C: \ WINNT \ system32 \ drivers \ etc). Add an IP address to the corresponding record of the server name, such as: 172.168.10.24 myserver 2. Or in SQL Servers client network utility, which is configured in detail. Second, check the SQL Server Server working state using the Telnet command Telnet server IP address 1433 If the command executes successfully, you can see the cursor blinking in the top left corner after a flash of the screen, indicating that the SQL Server Server is working properly and is listening for TCP/IP connectivity on port 1433 If the command returns