Hi all,
I downloaded krb5-1.3.5-sparc-sun-solaris2.9.tar and unpacked the tar to
get it installed on my UNIX box. Then I tried to run kinit (the one in
the unpacked directory), I got an error:
ld.so.1: kinit: fatal: libkrb4.so.2: open failed: No such file or
directory
Then I checked
Kerberos experts,
I am using SEAM 1.01 on Solaris 9 and am authenticating to AD. When others try they
fail the login with the KRB5 error code 52 error. I read that this has something to
do with UDP packet size and to try TCP. Is there a way in SEAM to have it use TCP
rather then UDP, or to
Sticking your KDC behind a load balancer seems like a singularly bad
idea. It's going to introduce a lot of complexity for no real
benefit.
Kerberos mailing list [EMAIL PROTECTED]
https://mailman.mit.edu/mailman/listinfo/kerberos
Sam,
Actually, a load balancer simplifies client deployment in our case (we
can't utilize DNS load balancing on our campus). We can, with a load
balancer, have all of the KDC's share one hostname. Our kadmin server
can also share that hostname.
kerberos:88 - points to our KDC's
kerberos:749 -
On Oct 5, 2004, at 23:15, Jason T Hardy wrote:
Sam,
Actually, a load balancer simplifies client deployment in our case (we
can't utilize DNS load balancing on our campus). We can, with a load
balancer, have all of the KDC's share one hostname. Our kadmin server
can also share that hostname.
On Wed, 6 Oct 2004 03:59:35 + (UTC) [EMAIL PROTECTED] (Jason T Hardy) wrote:
Sam,
Actually, a load balancer simplifies client deployment in our case (we
can't utilize DNS load balancing on our campus). We can, with a load
Don't need DNS load balancing (and it's broken anyway).
balancer,
