-625 & -622 Reported in DSREPAIR Report Sync Status

(Last modified: 12Jan2004)

This document (10089384) is provided subject to the disclaimer at the end of this document.

goal

-625 & -622 Reported in DSREPAIR Sync Status

fact

Novell NetWare 6

Novell NetWare 6 Support Pack 2

Novell eDirectory 8.6.2

Novell eDirectory 8.6.2 Support Pack 2

Only TCP/IP configured on the servers - NO IPX

symptom

There are no apparent communication issues between the servers and the -625's & -622 appeared to be sporadic. Repair NetWork Addresses in DSREPAIR reported no errors. Clients are still able to login and use copy files etc. to and from all servers.

change

Customer had upgraded the Certificate Authority from NetWare 5.1 to NetWare 6 a few months ago. Following this upgrade, NICI appeared to be functioning correctly

cause

NCP Packet Signature Option set to 2.
When this option is set to 2, NICI is used to sign the NCP packets.

SDIDIAG revealed problems with NICI [Checking Servers]
 *** Checking container .bt.PHOENIX-TEST. ...
   Server .OLD-EC-PHT3.pht3.resource.bt.PHOENIX-TEST.
    - Synchronization needed.
   Server .STF-CM-PHT2.pht2.resource.bt.PHOENIX-TEST.
    - Synchronization needed.
   Server .OLD-EC-PHT1.pht1.resource.bt.PHOENIX-TEST.
    - (Domain server) keys are good.

fix

Download the current version of SDIDIAG from support.novell.com

Run SDIDIAG --> RESYNC and ensure that it is successfull.

Setting the NCP Packet Signature Option to the default of 1 would also have "resolved" the error by not using NICI.
SDIDIAG is a better fix as this resolved the underlying NICI problems.

document

Document Title:	-625 & -622 Reported in DSREPAIR Report Sync Status
Document ID:	10089384
Solution ID:	NOVL94313
Creation Date:	05Dec2003
Modified Date:	12Jan2004
Novell Product Class:	Novell eDirectory

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.