On Monday, April 12, 2004 16:52:23 -0700 Donn Cave [EMAIL PROTECTED]
wrote:
I believe we're more or less always asking for this trouble.
If you don't get a canonical, reverse looked-up name back
out of MIT Kerberos krb5_sname_to_principal(), then you're
doing something different than me.
Well,
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Jeffrey Hutzelman) wrote:
On Monday, April 12, 2004 16:52:23 -0700 Donn Cave [EMAIL PROTECTED]
wrote:
I believe we're more or less always asking for this trouble.
If you don't get a canonical, reverse looked-up name back
out of MIT
On Saturday, April 10, 2004 16:47:21 + Donn Cave [EMAIL PROTECTED]
wrote:
It depends on your client software. All you need to do is resolve the
addresses to canonical host name first, and use the resolved name for
both the client connect and the service ticket.
Careful here... Using
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Jeffrey Hutzelman) wrote:
On Saturday, April 10, 2004 16:47:21 + Donn Cave [EMAIL PROTECTED]
wrote:
It depends on your client software. All you need to do is resolve the
addresses to canonical host name first, and use the resolved
Quoth vadim [EMAIL PROTECTED]:
| I am evaluating now a possibility of load balancing between several ldap
| servers. I imagine each ldap server will bind to its own ip address.
| LDAP client will try to connect to ip address of the loadbalancer and
| the loadbalancer will distribute requests
Hallo everybody,
I am evaluating now a possibility of load balancing between several ldap
servers. I imagine each ldap server will bind to its own ip address.
LDAP client will try to connect to ip address of the loadbalancer and
the loadbalancer will distribute requests between ip address of
