Please enter a title. Then I modified the ldapclient configuration to use tls:simple: # ldapclient mod -a authenticationMethod=tls:simple the configuration after: # ldapclient list NS_LDAP_FILE_VERSION= 2.0 NS_LDAP_BINDDN= cn=proxyagent,ou=Profile,ou=unix,dc=ch,dc=abb,dc=com NS_LDAP_BINDPASSWD= xx The crypted password :) xx Please help me I really need to sort out this. wrobbins2 Jun 23, 2010 4:49 PM (in response to 807567) 1) better to start a new thread than reply to one from years ago 2) check ownership & permissions on '/var/ldap/ldap_client_file' this contact form
Like Show 0 Likes(0) Actions 2. That is why it is so confusing. Note: ldap Indixing has been done and the patches have been applied as per the support article.Env: Solaris 8TS 6.1iPlante LDAPThanksPrem Pratick Kumar Report Inappropriate Content Message 1 of 3 (132 No other server has this problem. https://community.oracle.com/thread/1940775
All of the LDAP errors are from Uptime Inetd except one which says psinfo. Client Support Engineer uptime software ...because downtime is not an option Back to top #5 Garytm Garytm Member Members 3 posts Posted 04 July 2011 - 05:14 AM SOLVED - Finally. Thanks, Shalom Message was edited by: shalomG 6963Views Tags: none (add) This content has been marked as final.
Re: Problem on Solaris 10 Native ldap client. Libsldap: Status: 81 Mesg: Openconnection: Simple Bind Failed - Can't Contact Ldap Server They work fine with the authetification method simple. After doing this steps the Client can't connect to the Server again. Back to top Back to Technical Support 1 user(s) are reading this topic 0 members, 1 guests, 0 anonymous users Reply to quoted postsClear uptime User Community Forums → up.time
Index(es): Chronological Thread [Date Prev][Date Next] [Chronological] [Thread] [Top] Problems to authenticate Solaris 9 in OpenLDAP To: [email protected] Subject: Problems to authenticate Solaris 9 in OpenLDAP From: [email protected] Date: Tue, 13 Have someone faced this problem? Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily. Tue Nov 16 14:38:40.7371 Error: Unable to refresh profile:__default_config:Session error no available conn.
JudgeX Faq Reply With Quote Share This Thread Tweet This + 1 this Post To Linkedin Subscribe to this Thread Subscribe to This Thread « Previous Thread | Next All have local accounts for Uptime. There are a few Linux clients which connect over Port 636 to the Server. All LDAP tests pass. Libsldap: Makeconnection: Failed To Open Connection To
Sun Apr 29 22:40:55.5164 Error: Unable to update from profile =cut= I could resolve this executing: bash-3.00# svcadm restart network/ldap/client -and- bash-3.00# pkill -HUP ldap_cachemgr seams that ldap client was not Join Now For immediate help use Live now! It is setup fine and works fine on the server. Please add it.
But they should work with tls:simple, so: 1. One other possibility is that the client cannot resolve the IP to the FQDN (try "# getent 10.41.80.58" and verify it is a FQDN... I´m really despaired. :-( Can anyone help me? I'd recommend you open a support ticket by emailing [email protected] to have the up.time support department assist with investigating this issue more closely for you.Cheers,JW_ Jeff W Sr.
inetd: [ID 293258 daemon.warning] libsldap: Status: 81 Mesg: openConnection: simple bind failed - Can't contact LDAP server psinfo: [ID 293258 user.warning] libsldap: Status: 7 Mesg: Session error no available conn.