[OpenAFS] dynroot on Windows]

[Leroy Tennison]

This is a multi-part message in MIME format.
--------------020705050804020006000003
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jeffrey Altman wrote:

> 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
>  
>
Thank you for your reply and information, that was the issue.

--------------020705050804020006000003
Content-Type: message/rfc822;
 name="Re: [OpenAFS] dynroot on Windows"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Re: [OpenAFS] dynroot on Windows"

Message-ID: <43D465C6.3010500@prodigy.net>
Date: Sun, 22 Jan 2006 23:12:38 -0600
From: Leroy Tennison <leroy_tennison@prodigy.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jeffrey Altman <jaltman@secure-endpoints.com>
Subject: Re: [OpenAFS] dynroot on Windows
References: <43C9775F.5040002@prodigy.net> <43C93AC0.7090809@secure-endpoints.com>
In-Reply-To: <43C93AC0.7090809@secure-endpoints.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Jeffrey Altman wrote:

>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
>  
>
Thank you for your reply and information, that was the issue.


--------------020705050804020006000003--