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 >
smime.p7s
Description: S/MIME Cryptographic Signature
