Jaime Cifuentes wrote: > Hello all, > > My customer is requesting to deploy a 64-bit OpenAFS client running on > Windows XP64 SP2. We have an OpenAFS cell running on RedHat Linux. > A person on their team tried to install the available 64-bit client, but > ran into some issues. As I understand these were the problems he saw: > > 1. Once userid logged in to AFS, mapped drives status was as if it > was not mapped (no check mark ). Clicking on the drive could > connect the drive, but it not always happened.
Although the AFScreds tool is still included in the distribution its use is not recommended. Please read the release notes. The drive mapping APIs used by that tool are not reliable. Please encourage your users to map drive letters using the Explorer Shell Drive mapping and the \\AFS UNC paths. > 2. In a couple of occasions the drive connection just dropped. When the network interfaces on the machine are reconfigured the Netbios Name registration is temporarily lost. It will take a few seconds for the AFS Client Service to re-establish the name registration for \\AFS. > I have just gotten a loaner to play with for a short period, and I have > not tried this myself. But my question is if anyone has installed the > 64-bit client, and if they have seen any issues. And if they have, how > were they corrected? The only long term solution is the completion of the native file system client that permits the removal of the loopback adapter and the dependency on the SMB gateway server. This work is being funded and should be completed by the end of the year. Jeffrey Altman Secure Endpoints Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
