Windows Server TechCenter > Windows Server Forums > Hyper-V > Guest OS gets Access Denied on just 1 out of 2 Physical Drives, but can Share both fine with other Domain Clients
Ask a questionAsk a question
 

AnswerGuest OS gets Access Denied on just 1 out of 2 Physical Drives, but can Share both fine with other Domain Clients

  • Friday, September 18, 2009 10:44 PMWorstAdminKnownToMan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Now that you've read the basic outline in the title, let me go into detail.

    Setup:

    Host OS
    Windows Server 2008 R2 Build 7100
    1x250GB SATA (Online, C:\)
    2x1TB SATA (Offline)

    Hyper-V Manager
    Microsoft Corporation
    Version: 6.1.7100.0

    Guest OS
    Windows Server 2008 R2 Build 7100
    Dynamic VHD (Online, C:\)
    ->1TB DRIVE1 (Online, D:\)
    ->1TB DRIVE2 (Online, E:\)

    Symptom:
    The Guest OS can't access one of the attached physical drives (D:)

    "Location is not available"
    D:\ is not accessible.

    Access is denied.

    I can browse E: just fine. When comparing the Property tabs of both attached drives some look different:

    GENERAL drive capacity 0 bytes
    SECURITY Object name: D:\ [continue button]
    SHARING doesn't realise it's being shared
    QUOTA missing
    PREVIOUS VERSIONS aren't allowed for "offline files". This last symptom is also why I'm trying to resolve the matter. I like previous versions.

    I mentioned D:\ is shared and it is, just like E:\ and their NTFS permissions are identical. Using the same user, I can still browse the share from any client, VM or physical in the network.

    Steps Taken:
    I've tried switching between SCSI Controller and IDE Controller. Same difference.
    I've taken it completely offline. No change.
    I've attached it to another VM, running Windows XP SP3 in the same domain and was immediately able to browse it.

    Resolution:
    I hope someone could assist me with this. A solution is conditional: the data must not be touched. There is no possibility of migration.
    If more information is required to facilitate a resolution, please do not hesitate to ask. I will provide.

Answers

  • Tuesday, September 22, 2009 9:57 AMVincent HuMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    According to the description, the issue seems not related to Hyper-V. You problematic D:\ drive is a physical disk, if I misunderstand your concern, please feel free to let me know. If so, please connect this disk to a normal physical computer to check whether you get the same issue.

     

     

    Best Regards,

    Vincent Hu

     

All Replies

  • Tuesday, September 22, 2009 9:57 AMVincent HuMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    According to the description, the issue seems not related to Hyper-V. You problematic D:\ drive is a physical disk, if I misunderstand your concern, please feel free to let me know. If so, please connect this disk to a normal physical computer to check whether you get the same issue.

     

     

    Best Regards,

    Vincent Hu