Has anyone successfully used the Windows AFS client in an AFS cell with Ken
Hornstein's NRL AFS-Kerberos5 migration kit (which allow you to run a
normal Krb5 server, storing afs3, krb5, and krb4 keys)? We've successfully
used it with unix clients (using aklog to obtain AFS tokens from krb5
tickets) and have preserved the ability for users from foreign cells to
authenticate to our servers by running "fakeka", which decodes just enough
of the RX packet to forward the authentication request to the krb5 server.
So far so good... but the Windows AFS client has looked more attractive to
us lately and we cannot get it to work with our modified setup...
I can browse AFS filespace unauthenticated just fine. I can
successfully obtain tokens for an unmodified AFS cell, and also for a
second cell which implements MIT's Kerberos v4. When I try to obtain
tokens in our cell, however, the error message I actually get is:
The AFS Client was unable to obtain tokens as stephen in cell
physics.unc.edu.
Error: 37 (unknown authentication error 37).
Does anyone have any hints or tips for getting the Windows AFS client to
work in this modified environment; we'd _really_ hate to have to go back to
the Transarc KA server.
Cheers,
Stephen
--
Stephen Joyce
UNIX System Administrator / Network Administrator
Physics and Astronomy Department
University of North Carolina at Chapel Hill
[EMAIL PROTECTED]
voice: 919/962-6494
fax: 919/962-0480
