on 7/26/05 1:34 PM, Sanford Whiteman wrote:
. . . so hopefully Sandy can tell me how to allow ldap2aliases to
reference another port.
When using the -s option to specify the LDAP server, append the port:
-s 1.2.3.4:1389
Sandy,
That seems to work however I'm getting the size limit
on 7/27/05 7:23 AM, System Administrator wrote:
This current problem occurs when trying to use ldap2aliases on mx1 for
information on hosting2 (hosting2 is using port 1389).
Never mind. I rebooted hosting2 and now I don't get the size error on either
mx computer.
Thanks,
Greg
---
This E-mail
Never mind. I rebooted hosting2 and now I don't get the size error
on either mx computer.
Yep, requires a slapd restart when you change the .conf.
--Sandy
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems,
I'm trying to start the ldap service on another imail server (win2000) and
it won't start (I'd like to run ldap2aliases on it). Changing the ldap port
in imail to 1389 allows the ldap service to start. Port scanning, I see ldap
(port 389) is running, so something else must be using it. Anyone have
on 7/26/05 11:49 AM, System Administrator wrote:
I'm trying to start the ldap service on another imail server (win2000) and
it won't start (I'd like to run ldap2aliases on it).
For those following along -
I've discovered that Active Directory uses port 389 in Win2000. I haven't
located any
I've discovered that Active Directory uses port 389 in Win2000.
Indeed it does!
I haven't located any way to change that port yet. . .
Don't try.
. . . so hopefully Sandy can tell me how to allow ldap2aliases to
reference another port.
When using the -s option to specify the LDAP
