Does OMV within VM prohibit File Explorer Access

  • When OMV is operating in a Virtual Machine environment does that scenario prohibit computers on the network from accessing the Windows 10 Pro file structure of the computer housing the Virtual Machine? I am a beginner with OMV but a fairly good computer person. All of my network computers can see the main computer but ACCESS IS DENIED when attempted. I have checked permissions and security settings. All seems to be okay. I can access file structures from the machine to other computers on the network but I cannot access the machine itself from other computers. All three other computers have no problem interacting with each other on the network in File Explorer.


    If there is a problem could someone help me understand what I need to do to rectify.


    Thanks

    Thanks, Kai :thumbup:

    Current OMV5.3.4-1 OPERATING ENVIRONMENT: ASRock AB350Pro4 Mobo, AMD A8-9600 Bristol Ridge Quad-Core 3.1 GHz, 16GB Ram, Kingston A400 120GB SSD, WD Blue 4TB HDD

    Backup OMV5 OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 5.0-amd64 Linux Debian running virtual via VirtualBox v5.2.22
    DATA Backup - Two sets of identical backups using GoodSync 1-way backup onto 2 external drives.

    • Offizieller Beitrag

    Running OMV in a VM does not change how it works. How you have the virtual networking may make things work different but doubtful.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Running OMV in a VM does not change how it works. How you have the virtual networking may make things work different but doubtful.

    I understand OMV is compatible in a virtual environment. No problem there. Here's what I'm trying to convey . . .

    • I open File Explorer on a network computer that is other than the BSMT-P5ND (PC Name) computer where OMV is running virtually
    • I then click on the > to expand the file tree for the BSMT-P5ND because I want to access a folder and file located in one of the non virtual HDD drives
    • At that point I receive and error message stating Windows Cannot Access \\ BSMT-P5ND
    • The other 3 PC's on the network have the same issue
    • All Network and Sharing settings are identical on all PC's
    • I never had the problem before setting up the virtual machine to run OMV
    • Thus, I am wondering if the virtual OMV environment is preventing access

    Thanks, Kai :thumbup:

    Current OMV5.3.4-1 OPERATING ENVIRONMENT: ASRock AB350Pro4 Mobo, AMD A8-9600 Bristol Ridge Quad-Core 3.1 GHz, 16GB Ram, Kingston A400 120GB SSD, WD Blue 4TB HDD

    Backup OMV5 OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 5.0-amd64 Linux Debian running virtual via VirtualBox v5.2.22
    DATA Backup - Two sets of identical backups using GoodSync 1-way backup onto 2 external drives.

    • Offizieller Beitrag

    I do think that the OMV virtual environment is preventing access. Not because it is virtual but because that is one of the main features of OMV. OMV is designed to only provide access if you are allowed access. I suspect that you have not correctly configured OMV to provide access. It might be a minor spelling error or a skipped step setting up the share. But this is just a guess based on very limited information.

  • Adoby - I can appreciate your comments and I have a strong tendency to agree.


    Now, I just have to find out from someone on the forum exactly where I need to go within OMV - IF that is indeed the culprit. As a beginner, that is a little bit over my head to solve.

    Thanks, Kai :thumbup:

    Current OMV5.3.4-1 OPERATING ENVIRONMENT: ASRock AB350Pro4 Mobo, AMD A8-9600 Bristol Ridge Quad-Core 3.1 GHz, 16GB Ram, Kingston A400 120GB SSD, WD Blue 4TB HDD

    Backup OMV5 OPERATING ENVIRONMENT: Windows 10 Pro 64bit (always latest build) Intel Core 2 Quad Q9550 2.83GHz 8GB ram; OMV 5.0-amd64 Linux Debian running virtual via VirtualBox v5.2.22
    DATA Backup - Two sets of identical backups using GoodSync 1-way backup onto 2 external drives.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!