Re: Communicator 4 and LDAP
We are forced to use Exchange at work and I use its LDAP server to look up addressing information. I do occasionally get the error 0x5B that others report but I just try again and it usually works. This is with Netscape 4.61 on 4.0-CURRENT On Wed, 8 Sep 1999, Lars Fredriksen wrote: Hi, Has anyone had any luck using communicator with a LDAP server? Both communicator 4.5 and 4.61 fails to connect to any LDAP server that I have tried. It appears that the connect() gets interrupted and not restarted. This happens both under current and 3.0. Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- /===\ | Work: [EMAIL PROTECTED] | Home: [EMAIL PROTECTED] | \===/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Communicator 4 and LDAP
click on "Communicator" - AddressBook , then on your ldap server: Fill in : Description: User Friendly name for your ldap server LDAP Server: ldap's hostname Server Root: your server root Port Number : the port number where your ldap server is listening to From the address book window you should be able to query the ldap server. Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Communicator 4 and LDAP
Hi, I can't connect to the default ldap servers;however, on my win98 box I can connect to the InfoSpace ldap server. I have a local ldap server here and I can connect to it using netscape with no problem. Try it : rah.star-gate.com port 389 -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Communicator 4 and LDAP
Matthew Reimer wrote: Maybe the code is trying to bind the local side of the socket to port 0x5B? If so, then it could be proved by running Netscape as root. No, 0x5B is the LDAP_CONNECT_ERROR hex value. As I pointed out in the truss earlier a SIGALRM happens that causes connect() to return with a EINTR (which as far as I know it shouldn't and the connect(2) man page does not say that EINTR is a valid error return from connect()). The LDAP library assumes that connect() is restarted by libc if I read this right :-) Lars Matt Amancio Hasty wrote: Don't know what the problem is with netscape. I can search the ldap server with openldap's ldapsearch tool: /usr/local/openldap/bin/ldapsearch -h ldap.infospace.com -b "c=US" "cn=Amancio*" And what do you know I am listed there 8) cn=Amancio Hasty+ [EMAIL PROTECTED]; c=US; o=Amancio Hasty Jr; l=San Franci sco; st=CA; ou= objectclass=Person commonname=Amancio Hasty [EMAIL PROTECTED] cn=Amancio Hasty [EMAIL PROTECTED] surname=Hasty sn=Hasty c=US l=San Francisco st=CA o=Amancio Hasty Jr ou= title= description= postalAddress= telephonenumber= userPassword= userCertificate= givenname=Amancio facsimileTelephoneNumber= -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
