My Oracle Support Banner

After Configuring A New OID 11g Instance to Run on Privileged Ports, ldapbind to Port 636 Fails with "Cannot connect to the LDAP server" (Doc ID 1551929.1)

Last updated on JUNE 25, 2018

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.


Oracle Internet Directory (OID) 11g, i.e.,, on Linux.

After configuring another OID instance to listen on privileged ports 389 and 636, and applying solution steps from:

   OID LDAP Processes Fail to Start with Log Error "Bind failed" <Document 1432825.1>

OID starts and ldapbinds to port 389 work, however an ldapbind to the SSL port 636 fail with:

ldapbind -h -p 636 -U 1 -D "cn=orcladmin" -q
Cannot connect to the LDAP server


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.