This dialogue allows you to test the connection to the specified DSN on the remote server machine. It is a complete test of server address/port, server operating system authentication, remote system DSN existance and database authentication (if necessary). To test just the OOB Server settings use the Test button on the Servers dialogue off the Server tab.
Initially the main Test window will show all the connection attributes and the values you have set. Passwords are replaced with "**********". Check boxes which are checked have a value of 1 else they are 0 for unchecked.
When you click on the Test button the following test process is run:
The client connects to the port on the specified server. The server machine needs to have an OOB Server running on it and listening on the specified port.
The LogonUser/LogonAuth attributes (Username and Password fields on the Server tab) are sent encrypted to the OOB Server and passed to the operating system for validation.
The OOB Client needs the name of a server where the OOB Server is installed and the port the OOB Server is listening on. When the OOB Client connects to a server it passes the LogonUser/LogonAuth, the Server validates this with the standard operating system password APIs and then the server becomes that user for the duration of the connection.
The OOB Client will make "Connect Attempts" (see settings tab) attempts to connect to a server before giving up.
If you specify multiple OOB Servers then if the Client fails to connect to the first server, it will attempt to connect to the next server until a connection is made or until there are no servers left. If you want to use this facility you should probably reduce Connect Attempts on the settings tab to 1.
When you click on the test button in this dialogue the process above will be followed and you can view the results in the output pane.
If the test is sucessful it will end in "Test Successful" and you will be able to see the OOB Server name and version, the remote driver manager version and the name and version of the remote ODBC driver.
If any part of the test process is unsuccessful the test will stop and the output pane will display the reason for the failure.
Errors connecting to the OOB Server fall into these main categories:
If you are connecting to a UNIX OOB Server then the error number will always be -1 and it means the LogonUser/LogonAuth operating system username/password specified on the server tab is incorrect.
If you connecting to a Windows OOB Server then the error number is a Windows error number. These are the common ones:
Logon Failure: the user has not been granted the requested logon type at this computer. Check the user has the Logon Locally permission.
A required privilege is not held by the client. The OOB Server needs the "Act as part of the operating system" access right to authenticate and become the LogonUser.
Logon Failure: unknown username or bad password. The username is not a valid user or the password is invalid. If you have checked these are valid and the user is in an NT domain try prefixing the username with DOMAIN/ e.g. NTDOMAIN/Username.
Account logon time restriction violation. This account is has logons restricted to certain times and the current time is outside the allowable times.
The specified account password has expired. Renew the password expiration.
Logon failure: account currently disabled. Re-enable the account.
The specified domain did not exist. You are using the Domain/Username syntax in LogonUser and Domain does not exist.
The trust relationship between workstation where the OOB Server is running and the primary domain failed. Usually this means the workstation is not in the domain.
Account locked out. Unlock the account.
Parameter incorrect. You have specified an invalid username for the LogonUser attribute e.g. a zero length one. Check the LogonUser attribute is spelt correctly in your registry or ini file e.g. LogonUser is incorrect and results in the OOB client not finding a username and passing a zero length one.
The user must change his password before he logs on the first time. Check the logon settings for the user you are using or logon as that user and set the password.
An attempt was made to logon, but the network logon service was not started. Go to control panel, services and make sure the Net Logon service is running.
An access control rule has been created at the OOB Server which prevents this client accessing the OOB Server. You can view the OOB Server access control rules in the OOB Server's web administrator.
All errors reported connecting to the remote SYSTEM ODBC data source are reported using the ODBC defined statem native error code and a text message describing which element of the ODBC chain reported the problem and the error description..
The state is a 5 character code defined by ODBC.
The native error code is a code specific to the ODBC driver. For more information on the native error codes you need to consult the documentation for the remote ODBC driver you are connecting to. e.g. for MS SQL Server, native error code 18456 means the database username and/or password was incorrect.
This is split into a series of [ ] delimited ODBC elements and the error description. The ODBC element responsible for the error is that named in the rightmost [ ]. e.g. the error:
[unixODBC][OOB][Microsoft][ODBC SQL Server Driver][SQL Server]
was reported by the MS SQL Server. You can see from this chain that the connection went through the unixODBC driver manager to OOB, then the Microsoft driver manager, the MS ODBC driver and lastly MS SQL Server.
The error description should help you diagnose the exact problem. e.g.
Login failed for user 'fred'
For help diagnosing DSN connection errors see the OOB FAQ.