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

How do I use oobping to diagnose ODBC-ODBC Bridge authentication problems?

Once you've checked the Easysoft ODBC-ODBC Bridge connection, use oobping to check ODBC-ODBC Bridge authentication.

Use the -u and -p oobping arguments to specify a valid operating system user name and password.

Note If you've turned authentication off in the ODBC-ODBC Bridge server, any user name and password you specify should work.

Note If the user names or passwords contain spaces or characters that the shell might interpret, enclose them in single quotes (Linux and UNIX) or double quotes (Windows).

Note The -u and -p values are equivalent to the ODBC-ODBC Bridge client DSN attributes LogonUser and LogonAuth.

Here's an example oobping command that checks ODBC-ODBC Bridge server authentication:

oobpings -h myserver -t 8888 -u 'A User' -p 'mypassword'
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
Trying to authenticate...OK

If there is something wrong with the user name or password, the output will look something like this:

oobpings -h myserver -t 8888 -u 'A User' -p 'mypassword'
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
Trying to authenticate...Fail
Authentication failure (error number 1326)

The Windows error returned by the remote authentication service is 1326. For information about this and other common error codes, refer to Why do I get "Invalid authorization specification" or "authentication error number nnnn" when LogonUser and LogonAuth specify a valid user name and password?