Download ODBC Drivers for Oracle, SQL Server, Salesforce, MongoDB, Access, Derby, InterBase & DB2.

How do I use oobping to diagnose connection problems to the ODBC-ODBC Bridge server?

Check the Easysoft ODBC-ODBC Bridge server is running on the correct machine and listening on the correct port:

oobping -h myserver -t 8888
Host: myserver, Port: 8888
Attempting connection...OK
Examining Server...
    ODBC-ODBC Bridge Server Version: 1.1.0.00
    ODBC-ODBC Bridge Server Name: ODBC-ODBC Bridge

(oobping defaults the port to 8888, so you can omit -t.)

Here oobping connects to port 8888 on the machine myserver. The ODBC-ODBC Bridge server is clearly running, as oobping reports it finds ODBC-ODBC Bridge server version 1.1.0.00.

If you specify the wrong port and some other service is listening on it, you will get a variety or errors. For example:

oobping -h myserver -t 25
Host: myserver, Port: 25

Failed to receive data
Packet (size=842149920) too big for buffer (size=256)

If there is nothing listening on the specified port, you get a connection refused error. Check the ODBC-ODBC Bridge server is configured to use the port you specified and is running. For example:

oobping -h myserver -t 8889
Host: myserver, Port: 8889
Connection refused, connect(), after 5 attempts

If you have set up access control rules in the ODBC-ODBC Bridge server, you might get an error like:

oobping -h myserver -t 8888
Host: myserver, Port: 8888
Client denied access due to access control rule.

Here, the machine you're running oobping on has been denied access to the ODBC-ODBC Bridge server. Check the ODBC-ODBC Bridge server access control rules on the security page of the ODBC-ODBC Bridge web administrator.