Tobias Michaels wrote: >> Tobi: >> >> When sending reports it is helpful to specify which version >> of a product you are using. I am going to take a stab in the >> dark and guess that you performed a first time install using >> either 1.4.2-beta3 or 1.4.2-rc1. >> >> CM Error 11862791 = Cache Manager is not initialized / >> afsd not running / afsd not reachable >> >> >> Windows Error 0x52E = Logon failure: unknown user name or bad >> password. >> >> If this was a first time install of one of those two versions >> of OpenAFS there is a registry value that was not properly constructed. >> >> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0] >> "BackConnectionHostNames"=multi-sz >> >> You should upgrade to 1.4.2-rc2 and then remove this value from the >> registry and allow it to be re-created correctly. >> >> If that is not your problem, then we will need to know a great deal >> more about your machine and the domain infrastructure to which it >> belongs. In particular, do you log in to the machine with a password >> or do you use a smartcard or a MIT Kerberos realm or something else. >> >> Jeffrey Altman >> >> >> >> > > Hi Jeffrey, > i was using version 1.4.1. I did what you told me, uninstalled the > v1.4.1 und installed v1.4.2-rc2 > I checked my registry, but there is only the Lsa-Folder, I don't have > the MSV1_0 subfolder. What shall I do now? > > About the domain infrastructure: I try to use the afs-server of my > university via internet with a vpn-client from cisco systems running in > the background, but as I mentioned before it works fine with my laptop > and openafs1.4.1 > > Regards > > Tobi
I have never seen a Windows configuration that does not have the MSV1_0 key. Try creating that key and see if the behavior improves. The MSV1_0 key contains the options necessary for negotiating NTLM authentication. If the key doesn't exist then the afs client service will detect an error and will not create it. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
