Tobias Michaels wrote: > Thanks for the tip, > but I already use the timeserver of my cell for synchronizing. I found > something about debugging this error in the list archive and added a > registry key, after that i ran tokens.exe and it said: > C:\DOKUME~1\TOBIAS>tokens.exe > > Tokens held by the Cache Manager: > > pioctl Explorer logon user: [Tobias] > pioctl WNetAddConnection2(\\afs,Tobias) failed: 0x52E > pioctl WNetAddConnection2(\\afs\all,Tobias) failed: 0x52E > pioctl SamCompatible logon user: [ANUBIS\Tobias] > pioctl WNetAddConnection2(\\afs,ANUBIS\Tobias) failed: 0x52E > pioctl WNetAddConnection2(\\afs\all,ANUBIS\Tobias) failed: 0x52E > AFS device may not have started > > Maybe someone of you can recognize, what my windows is doing wrong? > > Regards, > > Tobi
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
smime.p7s
Description: S/MIME Cryptographic Signature
