Re: Communicator 4 and LDAP

1999-09-11 Thread Matthew Thyer
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, >

Re: Communicator 4 and LDAP

1999-09-08 Thread Fredriksen
Just a quick note, inside the netscape ldap library, there is a header file called potable.h, in it there is the following snippet: /* * for connect() -- must we block signals when calling connect()? This * is necessary on some buggy UNIXes. */ #if !defined(LDAP_CONNECT_MUST_NOT_BE_INTERRUPTED

Re: Communicator 4 and LDAP

1999-09-08 Thread Fredriksen
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

Re: Communicator 4 and LDAP

1999-09-08 Thread Matthew Reimer
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. 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/

Re: Communicator 4 and LDAP

1999-09-08 Thread Amancio Hasty
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

Re: Communicator 4 and LDAP

1999-09-08 Thread Fredriksen
Amancio Hasty wrote: > 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

Re: Communicator 4 and LDAP

1999-09-08 Thread Amancio Hasty
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 Unsu

Re: Communicator 4 and LDAP

1999-09-08 Thread Fredriksen
Amancio Hasty wrote: > 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

Re: Communicator 4 and LDAP

1999-09-08 Thread Amancio Hasty
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