API:<name> is writeable.   In that case the error indicates that either RPC functionality on
the machine is improperly installed or the krbcc32s.exe application could not be started
in the current session.

A "can't contact the KDC" error is produced by a failure to contact the KDC.  It means
the Kerberos libraries were able to obtain a list of servers for the realm and there was
no response.  Check that you have the correct information in the krb5.ini file and that
you are in fact using the krb5.ini file that you think you should be using.

Jeffrey Altman


Ty Sarna wrote:
Jeffrey Altman wrote:
  
What is your default ccname?   OpenAFS requires a ccache that can be
written to.   The MSLSA: ccache on Windows cannot be written to for
service tickets that the Windows LSA is not configured to obtain on
its own.
    

I *think* it's "API:", which should be writeable, no?

Also, it seems unlikely that this would cause the "can't contact KDC"
error when trying to get tokens manually, but perhaps I'm wrong?
Watching the KDC's log, it's definately not even trying to talk to it.
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
  

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to