Easysoft ODBC-ODBC Bridge

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

Last Reviewed:
19th January 2024

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:
    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

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

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 will 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 specified access control rules in the ODBC-ODBC Bridge Server, you might see an error such as this:

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

Here, the machine you are running oobping on has been denied access to the ODBC-ODBC Bridge Server. You should check the ODBC-ODBC Bridge Server access control rules on the security page of the ODBC-ODBC Bridge web administrator.

Applies To

Knowledge Base Feedback

* Did this content help you?
* Please select one option based on your first choice:

(* Required Fields)