Re: Possibly slightly O.T.: Why FQDN required to do simple bind with "ldapsearch"?

The issue is probably name resolution. Your solaris box wasn't resolving the short host name.

An alternative is if you are using SSL, you don't specify it, then you need to use the FQDN because that is what the cert is linked to.

joe


--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm



ohaya wrote:
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
.

Relevant Pages