Leroy Tennison wrote:
> Installed the Windows client, logged into afs, created the drive mapping
> in the client, went into Windows Explorer and tried to view the drive
> {which is labeled 'auto1 on afs (F:)'} but nothing was there. Tride
> Properties and got a long apuse but no result. Is this a dynroot issue
> or should I look for something else. Any troubleshooting tips would be
> appreciated.If you installed using the default settings, then Freelance mode is indeed on. Please read section 3.3 of the Release Notes which can be accessed by Start->Programs->OpenAFS->Documentation for information on how Freelance mode works. OpenAFS for Windows supports UNC paths to access the AFS name space of the form \\AFS\<cellname>\<path> As long as addresses for the vldb servers for <cellname> can be resolved via either the CellServDB file or AFSDB DNS records, then mount points for <cellname> (or .<cellname> RW) will be automatically created in the Freelance "root.afs" volume. There is a known bug in Windows that allows the same drive letter to be assigned to both a Network Drive Mapping and a removable device such as a USB hard disk, SD card, CF card, etc. When such a collision occurs it is impossible to use the drive letter to access any data. I recommend you test OpenAFS by using UNC paths and if you are going to assign drive mappings, do so via the Windows Explorer and start with the highest available drive letter in order to avoid collisions. In the future, when asking questions please indicate what version of the software you are referring to. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
