Stephen Joyce wrote:
C:>dir u: The system canot find message text for message number 0x13d in the message file for System.
Interestingly, the dir of \\winho-afs\users SUCCEEDED the very first time I executed the command, but failed thereafter. This is not a tokens issue; the same user can issue the same commands on 1.2.10 clients without problems.
Why do you believe this is not a token issue?
You are running a cell with mixed servers. 152.2.5.2 and 152.2.7.67 are OpenAFS either 1.2.10 or 1.2.11 depending on the service. But 152.2.5.3 is Transarc AFS: AFS version: Base configuration afs3.6 2.26
The moment your client connects to the Transarc server its going to fail if you have Kerberos 5 based tokens.
The very first item in the afs-install-notes.txt file that is posted along with the installers for 1.3.71 states:
"As of 1.3.65, the OpenAFS client will directly use Kerberos 5 tickets as tokens if KFW is installed. The client requires that all of the AFS Servers with which it communicates support the use of Kerberos 5 tickets as tokens (aka 2b tokens). This means that all of the AFS servers must be running OpenAFS release 1.2.8 or higher. Transarc servers do not support Kerberos 5 tickets as tokens."
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
