from PRB: Error Establishing Socket with JDBC Driver http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q3131781. The server name or IP address is incorrect. 2. The server name is correct, but the server is not running. 3. The server name is correct and it is running, but the server does not have TCP/IP enabled. 4. The server name is correct, the server is running and TCP/IP is enabled, but you have specified the incorrect port number in your JDBC connection URL. 5. If the problem is intermittent, it might be due to network problems or due to server problems (for example, the server is occasionally too busy to accept a connection). When the problem occurs, check to see if you can connect to the same server instance from another client, such as SQL Query Analyzer. It may also be useful to use a Network Sniffer such as Network Monitor (NetMon) to monitor traffic between the client and the server to determine if there is a network problem. 6. If the problem is not intermittent, it might still be a network configuration problem. For example, you may be behind a firewall that blocks certain ports.
PRB: Error Establishing Socket with JDBC Driver
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q3131781. The server name or IP address is incorrect.
2. The server name is correct, but the server is not running.
3. The server name is correct and it is running, but the server does not have TCP/IP enabled.
4. The server name is correct, the server is running and TCP/IP is enabled, but you have specified the incorrect port number in your JDBC connection URL.
5. If the problem is intermittent, it might be due to network problems or due to server problems (for example, the server is occasionally too busy to accept a connection). When the problem occurs, check to see if you can connect to the same server instance from another client, such as SQL Query Analyzer. It may also be useful to use a Network Sniffer such as Network Monitor (NetMon) to monitor traffic between the client and the server to determine if there is a network problem.
6. If the problem is not intermittent, it might still be a network configuration problem. For example, you may be behind a firewall that blocks certain ports.