I suspect this problem is going to be unrelated to Kerberos 5. You haven't shown any output from 'klog' or 'tokens' but I suspect they fail with the same error output.
The initial error is 0x66543218 or CM_ERROR_WOULDBLOCK. This error is being returned from afsd_service.exe in a previous call to pioctl Transceive that succeeded. The next step would be to capture debugging output from the afsd_service.exe or trace the operations in a debugger. Tracing the operations is a debugger will probably be necessary in this case because there simply aren't any obvious reasons why a CM_ERROR_WOULDBLOCK would be returned to the caller. Of course, I don't understand why would be be receiving an invalid exe error from a WriteFile call either. You are seeing this problem on more than one machine? Jeffrey Altman Gjefle, Paul D wrote: > c:\>aklog -d > Authenticating to cell our.afs.cell. > Getting v5 tickets: afs/[EMAIL PROTECTED] > pioctl temp != 0: 0x66543218 > About to resolve name [EMAIL PROTECTED] to id > Id 12345 > Set username to [EMAIL PROTECTED] > Getting tokens. > pioctl Transceive WriteFile failed: 0xC1 > aklog: unable to obtain tokens for cell our.afs.cell (status: 11862788).
smime.p7s
Description: S/MIME Cryptographic Signature
