Source:  eDirectory or NDS

Explanation:  A server sent a packet using eDirectory or NDS checksumming. However, the packet was identified as corrupt because the checksumming verification 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:  eDirectory or NDS for NetWare does not, by default, use checksumming because checksumming is not supported by all frame types. However, the source and target server are using checksumming.

Action:  Generally, it is not recommended that checksumming be used because most versions of eDirectory or NDS automatically provide transport-independent CRC checking on all eDirectory or NDS traffic between servers.

Possible Cause:  Packet corruption is occurring. This might be caused by faulty LAN drivers, LAN cards, or other LAN/WAN equipment existing between the source and target servers.

Action:  Make sure that any LAN/WAN equipment, cards, and drivers that exist between the source and target server are functioning properly.