Possibly slightly O.T.: Why FQDN required to do simple bind with "ldapsearch"?
- From: ohaya <ohaya@xxxxxxx>
- Date: Mon, 17 Apr 2006 22:28:40 -0400
Hi,
I was doing some testing, using ldapsearch from a Solaris machine, to access Active Directory. I was trying to use a simple bind, and initially could not get a successful access, until I started using a fully-qualified domain name (FQDN) for the hostname parameter.
I'm not sure if this is more of an AD question, or an ldapsearch question, but I was wondering if anyone might know why I had to use the FQDN for the ldapsearch hostname parameter in order for the simple bind to succeed?
Thanks,
Jim
.
- Follow-Ups:
- Re: Possibly slightly O.T.: Why FQDN required to do simple bind with "ldapsearch"?
- From: Joe Richards [MVP]
- Re: Possibly slightly O.T.: Why FQDN required to do simple bind with "ldapsearch"?
- From: Ace Fekay [MVP]
- Re: Possibly slightly O.T.: Why FQDN required to do simple bind with "ldapsearch"?
- Prev by Date: setting up mail server
- Next by Date: Re: Possibly slightly O.T.: Why FQDN required to do simple bind with "ldapsearch"?
- Previous by thread: setting up mail server
- Next by thread: Re: Possibly slightly O.T.: Why FQDN required to do simple bind with "ldapsearch"?
- Index(es):
Relevant Pages
|