Error 91 - Cannot Connect To The Ldap Server
Contents |
productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > > CA Support Online > Support by Product > Support by Product Error 91 in smps logs during the fail-over from one data center to another data center for policy/session/key store. Document unable to connect to ldap server my ldap server error invalid credentials (49) for user ID:TEC1282046 Last Modified Date:01/28/2016 {{active ? 'Hide' : 'Show'}} Technical Document Details Products unable to connect to ldap server simple bind failed CA Single Sign-On Releases CA Single Sign-On:Release:12.52 SP1 Components SITEMINDER -POLICY SERVER:SMPLC Issue: Getting "Error 91 - Can't unable to connect to ldap server joomla connect to the LDAP server" in smps.log for LDAP binds with failover servers in place. For Example: In Data Center A we are getting the below error while trying to fail-over
Failed To Initialize Tcp Client Connection. Socket Error 107
to Data Center B and Vice Versa. [01/28/2015][11:30:09][3844287344][][][][][][][][][][][][][][LogMessage:ERROR:[sm-Ldap-00350] SmObjLdapConnMgr Bind. Server Data_Center_B:20492. Error 91 - Can't connect to the LDAP server][][] Environment: Policy Server: R12.52 SP1 CA Directory: R12 SP12 Cause: The default connection setup timeout to session/policy store (CA directory) should be 10 seconds, however based on analysis it using 10ms. This results in failures connecting to the session/policy/key store across the siteminder socket error 107 data center. There is known issue for policy/key/session store LDAP binds with fail-over servers in place on 12.52 SP1 and it is fixed in 12.52SP1CR1. As a work around try connecting only one LDAP store if it's non prod environment and if it is production use LDAPPingTimeout in smregistry. Resolution: Please find the temporary workaround by adding the following to the sm.registry (LDAPPingTimeout) in case of production. HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\Debug=1032831252 Console= 0; REG_DWORD LDAPPingTimeout= 0x64; REG_DWORD And for Permanent fix, kindly upgrade your policy server to R12.52 SP1 CR01 Please help us improve! Will this information enable you to resolve your issue? Yes No Please tell us what we can do better. {{feedbackText.length ? feedbackText.length : '0'}}/255 {{status}} Not what you were looking for? Search Again> Product Information Support by Product> Product Documentation> Communities Join a Community> Education Find training by product> SHARE THIS {{link.title}} Copyright © 2016 CA. All rights reserved. {{link.title}} North America (English) Chat with CA Just give us some brief information and we'll connect you to the right CA Expert. Our hours of availability are 8AM - 5PM CST. All Fields Req
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same. Proudly Powered by phpBB © phpBB Group © 1998-2015 mozillaZine All Rights Reserved
HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Server [SOLVED] openldap client fails to connect http://www.linuxquestions.org/questions/linux-server-73/openldap-client-fails-to-connect-ldap-server-'ldap_bind-can't-contact-ldap-server'-834930/ ldap server 'ldap_bind: Can't contact LDAP server' User Name Remember Me? Password Linux - Server This forum is for the discussion of Linux Software used in a server related http://docs.oracle.com/cd/E19253-01/820-3508/txldap-8/index.html context. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability connect to to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | unable to connect Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. S
Solaris Trusted Extensions Configuration GuidePrevious: Initialize the Solaris Management Console Server in Trusted ExtensionsNext: Creating Labeled Zones Make the Global Zone an LDAP Client in Trusted Extensions For LDAP, this procedure establishes the naming service configuration for the global zone. If you are not using LDAP, you can skip this procedure. Starting in theSolaris 105/08 release, if you are in a Solaris Trusted Extensions (CDE) workspace, you can use the txzonemgr script or a Trusted CDE action to create an LDAP client. If you are in a Solaris Trusted Extensions (JDS) or a Solaris Trusted Extensions (GNOME) workspace, you must use the txzonemgr script. Note – If you plan to set up a name server in each labeled zone, you are responsible for establishing the LDAP client connection to each labeled zone. Before You BeginThe Sun JavaTM System Directory Server, that is, the LDAP server, must exist. The server must be populated with Trusted Extensions databases, and this system must be able to contact the server. So, the system that you are configuring must have an entry in the tnrhdb database on the LDAP server, or this system must be included in a wildcard entry before you perform this procedure. If an LDAP server that is configured with Trusted Extensions does not exist, you must complete the procedures in Chapter5, Configuring LDAP for Trusted Extensions (Tasks) before you perform this procedure. If you are using DNS, modify the nsswitch.ldap file. Save a copy of the original nsswitch.ldap file. The standard naming service switch file for LDAP is too restrictive for Trusted Extensions. # cd /etc # cp nsswitch.ldap nsswitch.ldap.orig Change the nsswitch.ldap file entries for the following services. The correct entries are similar to the following: hosts: files dns ldap ipnodes: files dns ldap networks: ldap files protocols: ldap files rpc: ldap files ethers: ldap files netmasks: ldap files bootparams: ldap files publickey: ldap files services: files Note that Trusted Exte