COMMAND

    volumes

SYSTEMS AFFECTED

    Win

PROBLEM

    Lee Wilbur found  following.  He  encountered a problem  where, if
    you mount a  partition to a  path rather than  a drive letter  and
    then create  a Macintosh  volume for  it, the  permissions set for
    that volume will be ignored by Mac clients.

    This is what Lee did and you can too to reproduce the problem:

        1. Create a generic user account.
        2. Mount  a disk  partition to  a folder  off another  logical
           drive letter (ex. c:\TestJunction).
        3. Set permissions  on that junction  so that only  the domain
           admins are allowed access.
        4. Create  a Mac  Volume for  that mount  point (path would be
           c:\TestJunction in the example)
        5. Now,  from a  Mac client,  connect to  the server  with the
           generic user  account.   You should  see the  Mac volume as
           accessible - even though your generic user is not a  domain
           admin.  Mount  the volume.   Then open it  and copy a  file
           into the folder.  Even though you shouldn't have permission
           to, you'll be able to copy that file.
        6. To  further  test  this,  Lee  removed  the volume, made  a
           sub-folder  under   the   root   of   the   junction   (ex.
           c:\TestJunction\TestSubFolder) then created the Mac  volume
           again, this time linked to the TestSubFolder.  This time it
           worked, he  was unable  to gain  access to  the volume  (it
           appears grayed out).

SOLUTION

    Based on information provided me by Clark Lebarge it appears that
    the resolution suggested in Microsoft KB article Q237701 fixes the
    problems.

    Though it makes no mention  of this specific issue in  relation to
    macintosh  volumes,  it  appears  to  have  been  the cause of the
    problem.   Once  Lee  did  as  Clark  suggested  the "visible" mac
    volumes were grayed out as they should be.