On 6/25/2010 1:16 AM, Atro Tossavainen wrote: > Hi, > > Is the AFS Control Center in the Windows OpenAFS client even supposed > to work any more? (This is on XP.)
They are known not to work. There is no one maintaining them.
> When I installed it, it started complaining about comerr32.dll missing,
> and when I removed OpenAFS, installed MIT KfW 3.2.2 and installed
> OpenAFS again, it no longer complained about the missing DLL but the
> program is still not working ("The AFS Account Manager was unable to
> find the TaAfsAdmSvr.exe program, or was unable to prepare your computer
> to perform AFS administration. Error: f 191 (1727) (0x000006BF)").
>
> The TaAfsAdmSvr.exe program is in the same directory as the Account
> Manager, in C:\Program Files\OpenAFS\Control Center. Trying to start
> it manually on the command line, without any parameters, results in
>
> AdmSvr: Initializing...
> AdmSvr: RpcNsBindingExport failed; error 0x00000000
> AdmSvr: Could not bind to port 1025 or export bindings; terminating
> AdmSvr: Shutting down...
Is your intention to install and operate a kaserver on Windows?
> And of course, with MIT KfW 3.2.2 installed, OpenAFS token acquisition
> from a kaserver stops working altogether so OpenAFS can't be used.
From the release notes:
Value: EnableKFW
Regkey: [HKLM\SOFTWARE\OpenAFS\Client]
Regkey: [HKCU\SOFTWARE\OpenAFS\Client]
Type: DWORD {0, 1}
Default: 1
Function: KFW_is_available()
When MIT Kerberos for Windows can be loaded, Kerberos v5 will be used to
obtain AFS credentials. By setting this value to 0, the internal
Kerberos v4 implementation will be used instead. The current user value
is checked first; if it does not exist the local machine value is checked.
smime.p7s
Description: S/MIME Cryptographic Signature
