Source: eDirectory or NDS
Explanation: An unexpected error occurred on the target server.
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: Continuous occurrences of this error indicate the requester is using an invalid or unsupported request format. Packet corruption has occurred.
Action: Make sure that any LAN/WAN equipment, cards, and drivers that exist between the source and target server are functioning properly.
On every server in the replica list, run DSREPAIR with the option to Verify Remote Server IDs set.
Possible Cause: Continuous occurrences of this error can also indicate that a program fault occurred in the application used to issue the eDirectory or NDS request.
Action: Contact the developer of the application.
Possible Cause: The target server sent an invalid reply.
Action: Make sure there is a master replica of each partition.
Possible Cause: This error can also be a result of one or more of the following errors occurring.
Action: For information to resolve each error, see the information provided for each error.
Possible Cause: The target server does not have the correct information about the source server. Not having the correct information is often caused by a problem with local to remote ID numbers or the Server object.
Action: If you suspect that the target server does not have the correct information, do the following:
Possible Cause: The source server is unable to contact another server needed to complete the operation. This could occur because a link or server is down.
For example, if you do a Receive Updates in DSREPAIR and the server with the master replica is down, this error will be returned.
Action: If you suspect that the source server is unable to contact another server needed to complete the operation, do the following: