Just -h 10.2.250.15 -x -b 'dc=ldn,dc=sw,dc=com'
((objectClass=nisDomainObject)(nisDomain=ldn.sw.com)) should match
the scripted search.
OK - I ran
ldapsearch2.4 -h 10.2.250.15 -D
cn=proxyagent,ou=profile,dc=ldn,dc=sw,dc=com -w x -x -b
'dc=ldn,dc=sw,dc=com'
Stuart Cherrington wrote:
OK - so I tried
ldapsearch2.4 -h 10.2.250.15 -x -b 'dc=ldn,dc=sw,dc=com'
# extended LDIF
#
# LDAPv3
# base dc=ldn,dc=sw,dc=com with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#
# search result
search: 2
result: 32 No such object
# numResponses: 1
What are the searches being run (from your slapd.log)?
The ldap.log contains
Aug 27 12:36:24 msldap01 slapd2.4[22363]: connection_get(21)
Aug 27 12:36:24 msldap01 slapd2.4[22363]: SRCH 0 3
Aug 27 12:36:24 msldap01 slapd2.4[22363]: 0 30 0
Aug 27 12:36:24 msldap01
Hi,
I Have an OpenLDAP 2.4.18 server on RHEL 5.3. I can get Linux clients to use
the master by use of the /etc/ldap.conf file. I'm now trying to get a SOlaris
10 client to use the master by initialising with the default profileName. If I
run:
ldapclient -v init -a proxypassword=x -a
Date: Fri, 27 Aug 2010 21:33:42 +1200
From: i...@ianshome.com
To: stuart_cherring...@hotmail.co.uk
Subject: Re: Getting Solaris to use Openldap
On 08/27/10 08:48 PM, Stuart Cherrington wrote:
Hi,
I Have an OpenLDAP 2.4.18 server on RHEL 5.3. I can get Linux clients
to use
On 08/27/10 09:56 PM, Stuart Cherrington wrote:
Date: Fri, 27 Aug 2010 21:33:42 +1200
# default, profile, ldn.sw.com
dn: cn=default,ou=profile,dc=ldn,dc=sw,dc=com
*defaultSearchBase: dc=ldn,dc=sw,dc=com*
authenticationMethod: simple
followReferrals: TRUE
profileTTL: 43200
Date: Fri, 27 Aug 2010 22:33:15 +1200
From: i...@ianshome.com
To: stuart_cherring...@hotmail.co.uk
Subject: Re: Getting Solaris to use Openldap
CC: openldap-technical@openldap.org
On 08/27/10 09:56 PM, Stuart Cherrington wrote:
Date: Fri, 27 Aug 2010 21:33:42 +1200
# default
On 08/28/10 12:41 AM, Stuart Cherrington wrote:
Date: Fri, 27 Aug 2010 22:33:15 +1200
From: i...@ianshome.com
What are the searches being run (from your slapd.log)?
The ldap.log contains
Aug 27 12:36:24 msldap01 slapd2.4[22363]: connection_get(21)
Aug 27 12:36:24 msldap01 slapd2.4[22363]:
