If there is no other way for the change to be sent to FS3, the network will need to be changed so the servers can communicate. For help with error codes that provide possible causes along with actions you can take, see SecureLogin Error Code List. In cases where strange communication errors appear, you should check the network address information that the server experiencing the error is using against the actual network address information that the other Consult your product manuals for complete trademark information. weblink
Often a number code is truncated to two digits, so it is not the actual decimal equivalent or the hexadecimal code. However, if FS3 attempts to send the change to FS1, it will receive a communication error because FS1 only communicates via IPX. A server might experience what appears to be a communication problem, when the actual problem is network address misinformation that one server is using to communicate with the target server. Make sure that you provide rights for the service by adding the appropriate containers to the containers list in the import policy" fix This means the import policy did not have
However, in this case, the error is informational because FS1 can still receive the change from FS2. Novell makes all reasonable efforts to verify this information. For more information on transitive vectors and transitive synchronization, see http://support.novell.com/techcenter/articles/anp20020301.html and http://support.novell.com/techcenter/articles/anp20020201.html . Novell is now a part of Micro Focus Home Micro Focus Home Skip to Content Products Collaboration + Open Workgroup Suite GroupWise Micro Focus Vibe Endpoint Management
For information on error codes for LDAP, see LDAP and NDS Integration in the Novell Developer Kit (NDK). LAN/WAN Failures. Errors of this type can occur due to problems with any of the following situations: Outdated, faulty, or incompatible LAN drivers used by a server Faulty LAN hardware or cabling used An outstanding operation is preventing a request from being processed.
Some of the NDS error codes commonly returned due to communication issues are: ERR_INVALID_TRANSPORT (-622) ERR_TRANSPORT_FAILURE (-625) ERR_ALL_REFERRALS_FAILED (-626) ERR_UNREACHABLE_SERVER (-636) ERR_SECURE_NCP_VIOLATION (-684) ERR_CHECKSUM_FAILURE (-715) Informational Communication Errors. The Schema Manager in ConsoleOne. However, the information provided in this document is for your information only. It is also possible that a communication error code may be informational only.
symptom "Login count = (x), Logins required = (y) fix Ensurelogins count found in HKLM\SOFTWARE\NOVELL\WORKSTATION MANAGER\IDENTIFICATION\USER LOGINS\