HAH! Got the bugger The latest error was because I still had an
afs/cellname principal running around... So the fix is either tweak
krb5.conf to default to afs/cellname (or just afs) (windows clients
wont go to afs/cellname, at least not that I've found, so my choice was
straight [EMAIL
"James D. Nurmi" <[EMAIL PROTECTED]> writes:
> the krb5.conf is correctly stating that the kdc & adminserver are the
> newly CNamed kerberos1 machine... Kinit works, aklog works. klist
> lists out the new ticket, tokens claims to have tokens... However if I
> try to enter a section on /afs that r
Derek Atkins <[EMAIL PROTECTED]> writes:
> Set your krb.conf/krb5.conf to point to the new KDC.
>
> Or do you mean you're actually using "klog"???
Windows client uses the db server as kerberos servers (and so does klog)
I use a udp forwarder to that I wrote to "solve" the problem.
ftp://ftp.sta
