Kerberos works best with a random number generator package installed on the operating system. If one is not installed, it will use a potential slow fallback entropy generating system.
HP provides a /dev/random driver for hp-UX 11i (11.11), named 'KRNG11I'. It is available, for free, from the KRNG11I depot. You can check if this is already installed by running:
$ swlist KRNG11I
For older versions (hp-UX 11.00), an open-source implementation of /dev/random is available from "random" DLKM (dynamically loadable kernel module) for HP-UX .
Entropy is generally obtained from /dev/random which is an interface to a kernel random source. On Solaris 8, the /dev/random driver is provided in the following patches from ORACLE:
Kerberos is a time-sensitive protocol. Your Unix hosts must be synchronized within five minutes of your Active Directory domain controllers. Run the following command as root to have Authentication Services synchronize the local time with Active Directory:
The most common installation or upgrade failure is that the Unix host cannot read the Authentication Services application configuration in Active Directory. Ensure that you have followed the instructions in Configure Active Directory for Authentication Services and that the configuration has been created successfully.
During an upgrade you may see an error that Authentication Services cannot upgrade because the application configuration cannot be located. If you previously joined to a specific domain controller Authentication Services disabled DNS SRV record lookups. This means that Authentication Services cannot resolve other domains in the forest and may be unable to locate the application configuration. In this case you must ensure that the domain controller you specified is a global catalog. Otherwise, you must create the Authentication Services application configuration in the domain that you join or you must properly configure DNS to return SRV records and join normally, rather than specifying a domain controller when you join.
For more information, see About Active Directory configuration.
If you are unable to join the domain, run the preflight utility to validate your environment.
Then, verify the following:
If you are joining to a specific domain controller you must ensure that Authentication Services can locate and read the configuration information in Active Directory. You should do one of the following: