Derrick Brashear <[email protected]> writes: >> Moreover, there seems to be some sort of change in the behavior of the >> 1.5.68 aklog relative to 1.4.11; the new aklog only appears to attempt >> the latter one. > > There seems not to be.
Well, when I hold tickets for [email protected] and attempt to aklog to research.cs.berkeley.edu (which uses principal afs/[email protected]), I see this on RESEARCH.CS.BERKELEY.EDU's KDC: 2009-12-28_19:16:48.25167 Dec 28 11:16:48 research.cs.berkeley.edu krb5kdc[2979](info): TGS_REQ (1 etypes {1}) 65.23.129.159: UNKNOWN_SERVER: authtime 1262027795, [email protected] for [email protected], Server not found in Kerberos database 2009-12-28_19:16:48.39314 Dec 28 11:16:48 research.cs.berkeley.edu krb5kdc[2979](info): TGS_REQ (1 etypes {1}) 65.23.129.159: UNKNOWN_SERVER: authtime 1262027795, [email protected] for [email protected], Server not found in Kerberos database 2009-12-28_19:16:48.53461 Dec 28 11:16:48 research.cs.berkeley.edu krb5kdc[2979](info): TGS_REQ (1 etypes {1}) 65.23.129.159: UNKNOWN_SERVER: authtime 1262027795, [email protected] for [email protected], Server not found in Kerberos database When I downgrade the client (65.23.129.159) to 1.4.11, everything works fine. I'm sure this is a configuration error on my part, and I've just lucked out in some way that the 1.4.11 client is more forgiving about. - a _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
