LDAP is not listening to port 389 unless "Disable SSL Port" is selected on the LDAP server object.

(Last modified: 11Nov2003)

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

fact

Novell NetWare 5.1 Support Pack 6

Novell Directory Services 8

Novell Portal Services 1.0

symptom

LDAP is not listening to port 389 unless "Disable SSL Port" is selected on the LDAP server object.

If SSL is enabled LDAP is not listening to either 389 or 636 when viewed from TCPCON - PROTOCOL INFORMATION - TCP - TCP CONNECTIONS.

When LDAP loads the message: "Waiting from SSL services to initialize" is seen.

PKIDIAG has been run and the server KMO assigned to the LDAP server validates correctly.

cause

This issue is caused by a race condition between SAS and NILE.  This, among other things,  can be caused by their load order in autoexec.ncf.  NILE must be loaded and logged into eDirectory for SAS to initialize.

fix

Change the load order in the autoexec.ncf.  To see the correct order please refer to TID 10082078.

If SAS is manually unloaded and re-loaded you will see the server begin to listen on secure ports.

There is a new SAS.NLM released that will wait up to 20 seconds for NILE to initialize before giving up.  Please refer to TID 10082078 for the patch name and details.

document

Document Title:	LDAP is not listening to port 389 unless "Disable SSL Port" is selected on the LDAP server object.
Document ID:	10088716
Solution ID:	NOVL93931
Creation Date:	11Nov2003
Modified Date:	11Nov2003
Novell Product Class:	NetWare

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.