Informix on NT4 server registry settings

Hi! I was wondering anybody here could help with the issue mentioned above..... We are encountering what we think is a NT/Informix authentication issue in that initial access (datbase connection) to the DB is extremely slow... up to 2mins! Reading thru the relase notes we found the following document. The PDC is available and there is no BDC... does the following still affect us ?.. any help would be appreciated! The domain is only 30 users so the speed shouldnt be a problem!. The registry keys we have on the db server are not correct for the environment...... are they still used even tho the PDC is available? Thanks Special Conditions when the Primary Domain Controller is Unavailable -------------------------------------------------------------------- The following information might apply to you if you upgraded from an earlier version of the database server. The 7.31 install always sets REGMACHINE to point to the local machine. Earlier versions sometimes set REGMACHINE (and INFORMIXSQLHOSTS) to the Primary Domain Controller for the domain when a domain install was performed. When Informix Dynamic Server is installed on a Backup Domain Controller (BDC) and the Primary Domain Controller (PDC) is unavailable, the engine will automatically switch to the BDC for dealing with Windows NT group and user accounts for authentication. This includes determining whether a user belongs to a group (Informix-Admin, for instance). In this situation, the Administrator must perform the following steps in order to support this functionality: 1. Dynamic Server must be shut down. 2. In the registry under HKEY_LOCAL_MACHINE\\Software\\Informix\\OnLine\\<%INFORMIXSERVER%>\\Environment change the values of REGMACHINE and INFORMIXSQLHOSTS to the name of the local machine (BDC), preceded with 2 back-slashes. 3. Copy the Security key located under HKEY_LOCAL_MACHINE\\Software\\Informix\\OnLine\\<%INFORMIXSERVER%>\\ from the PDC to the BDC, including all subkeys. 4. In %INFORMIXDIR%, edit the file setenv.cmd and change the INFORMIXSQLHOSTS value to the name of BDC. The PDC can now be shut down and Dynamic Server can be restarted on the BDC. There will be a several-second delay when Dynamic Server and any of the command-line utilities, such as onstat, onmode, or dbaccess are started, while they try to determine that the PDC is down and switch to the BDC. After the initial delay, the performance will be the same as when the PDC was running. When the PDC is not available, the following might also have to be done, if the server is not running on a BDC machine. 1. Shut down the database server. 2. Set the AUTHENTICATION_MACHINE environment variable for the the server in the registry to point to a BDC machine in the same domain. For example, under HKEY_LOCAL_MACHINE\\Software\\Informix\\OnLine\\%INFORMIXSERVER%\\Environment create a new value called AUTHENTICATION_SERVER and set it to the string: "\\DOM_BDC" if DOM_BDC is the name of a BDC for the domain. 3. Restart the database server. When the local machine is a BDC, setting AUTHENTICATION_SERVER is not necessary.