Installation guide
21-13
Messages 400 – 499
Action: Check both the Internet counters for errors and the operation of the security server
host. For more information on security server host connectivity, refer to the Network
Access Software Management Guide.
Local -480-Security server host rejected new password as insecure
Explanation: The new password chosen was deemed unacceptable to the security policy
enforcement mechanism of the Kerberos security server host.
Action: Choose a more secure password; one that is longer and does not contain part of
the principal name.
Local -481-Security server host database in use or locked
Explanation: Password updates to the security server host’s database are not presently
possible.
Action: Retry later or contact the system administrator.
Local -482-Security client failed to send a packet; no network buffers
Explanation: The buffers used to send and receive network data were all in use. A
memory leak may exist in the software. It is also possible that the access server is
momentarily overloaded.
Action: If the error persists, reboot the access server. If the error returns, contact your
authorized service representative.
Local -483-Security client failed to send a packet; transmission error
Explanation: The security client incurred a socket transmission error.
Action: This problem can have many causes. Check the network parameters on the access
server. For example, check that the other protocols are not affected and that the access
server can successfully issue a PING command.
Local -484-Security client failed to receive a packet; receive error
Explanation: The access server socket layer returned a receive error.
Action: This problem can have many causes. Check the network parameters on the access
server. For example, check that the other protocols are not affected and that the access
server can successfully issue a PING command.
Local -486-Security server (host) not specified
Explanation: Either the security server host name entered is invalid or not defined on the
access server as a security server host.
Action: Reenter the correct host name as a security server for the realm in question. If the
problem persists, refer to the Network Access Software Management Guide.