This dialogue allows you to test connections to the specified OOB servers and the authentication on the server machine using LogonUser/LogonAuth on the server tab.
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.
Note: The Test button on this dialogue only tests connection to the OOB Server and operating system authentication. It does not test connection to a remote DSN (use the Test button on the main tab for that).
When you click on the test button in this dialogue each server will be tested using the process above. The Test Log window displays a progress report. The colouring used in the test log is:
Once all the servers have been tested either a green tick (for successful) or a red cross (unsuccessful) will be placed next to each server.
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.