Ted: Please read my previous response and provide the answers to the questions I asked. Since I can't reproduce this problem I need a stack trace to know what is broken.
ted creedon wrote: > Jeffrey, > > 1. The auth screen just doesn't pop up although it tries. So give me a stack trace. > 2. The AFS Client Configuration screen is accessable only thru Leash AFS > properties There is an AFS Control Panel in the Windows Control Panel for this. > 3. Leash does get AFS tokens for a cell that uses krb5 Because it is in the list of Kerberos realms > 4. Leash does not get AFS tokens for a cell that uses kaserver (I assume > that's because I don't understand how to set the system up - but I don't > care - its going away) Add it to the list of Kerberos realms in the Kerberos 4 config files. > 5. Under Linux aklog and klog produce tokens for the krb5 cell and kaserver > cell Only if the kaserver is listed as a Kerberos realm will aklog know how to access it. > I'm not sure how Leash is supposed to interact with AFS client. On previous > releases to 1.3.87 one could access the AFS tokens window from either Leash > or directly (it would stop doing this occasionally and resume after a > reboot). Now its thru Leash only. Leash is an independent tool from the AFS Client. If it sees the AFS Client Service and can access it via pioctl calls it will try to obtain an AFS token. > I would like a catalog of all the registry values used by AFS as they are > not all deleted with uninstall. Perhaps I'll look at the sources. The > behaviour of the client changes if one manually deletes all the afs and > transarc settings prior to reinstall. All of the registry keys are documented in registry.txt which is distributed from the same page as the installers. > tedc > > ---Original Message----- > From: Jeffrey Altman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 10, 2005 8:26 AM > To: ted creedon > Cc: [email protected] > Subject: Re: [OpenAFS] 1.3.87 for Windows Authentication screen doesn't pop > up > > Someone else reported this problem this week as well. > His problem appears to be the use of Kerberos 5 based tokens > for a Transarc AFS cell. They won't work. You can't access > the mapped path and then afscreds.exe appears to get confused somehow. > > I'm on vacation and don't have time to research this problem. > What I can ask you to do is install the debugging symbols and Microsoft > Debugging Tools for Windows and then obtain a stack trace showing what > function afscreds.exe is hanging in. > > That will go a long way to identifying the real cause of the problem. > > Jeffrey Altman > > > ted creedon wrote: > > >>I'm running Leash and it has to be enabled manually from there. >> >>Problem solved. >> >>tedc >> >>---------------------------------------------------------------------- >>-- >>*From:* [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] *On Behalf Of *ted creedon >>*Sent:* Tuesday, August 09, 2005 4:06 PM >>*To:* [email protected] >>*Subject:* [OpenAFS] 1.3.87 for Windows Authentication screen doesn't >>pop up >> >>The Authentication screen for v 1.3.87 doesn't pop up. >> >>There is no lock icon in the systray >> >>Any suggestions? >> >>Thanks >> >>edc >> > > > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info
smime.p7s
Description: S/MIME Cryptographic Signature
