-669 FFFFFD63 FAILED AUTHENTICATION

Source

eDirectory™

Explanation

An attempt to authenticate an eDirectory client or to authenticate to an eDirectory server failed.

Warning:

Applying all solutions mentioned in this topic could make the problem worse if the actual cause of the problem is not known. Before following a course of action, make sure that you understand the cause of the error and the consequences for the actions suggested.

Possible Cause

An invalid password was received during the attempt to authenticate.

Action

Attempt to authenticate again. Make sure the password is entered correctly.

Possible Cause

If this error occurs during an attempt to establish communication to a server, the remote IDs on the source and/or target servers are invalid.

Action

To resolve a suspected remote ID issue, use the DSREPAIR Advanced Menu option View Remote Server ID List. Select any eDirectory server listed and then select the option to repair all remote IDs. Perform this operation on both the target and source servers. Repeat this operation until neither the source or target server reports any error.

Possible Cause

The source or target servers could be using an invalid Rivest-Shamir-Adleman (RSA) public key.

When the source server is using or looking at the wrong public key, the key is the right format, but is for the wrong object. If the problem is the public key, do one of the following:

- If the source server has a master replica, read/write replica, or read-only replica of the target server object, ensure that all other servers in the replica list are able to authenticate to the target server.

Warning

: Using the Send All Objects option generates a high level of network traffic.

If another server can authenticate, then do a Send All Objects from the correct server, or Receive All Objects on the target server (but only if the server with the correct copy has the master replica).

Make sure that you do not send copies containing incorrect public keys.

If no servers can authenticate to the target server, remove eDirectory from the target server and reinstall it into the tree, or contact a Novell* support provider.

- If the source server has a subordinate reference replica, or if no replica of the partition containing the target server object exists, then the external reference to that object needs to be backlinked again. Contact a Novell support provider.

A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For information on trademarks, see Legal Notices.