Connect a disk problem

Forum / NoMachine for Windows / Connect a disk problem

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #16527

    Running Windows 10 x64, latest patches. Latest client (6.0.62) connecting to Mac Mini running MacOS High Sierra (10.13.1) with NoMachine 6.0.62 as well. I’m trying to connect to a local disk (on the PC) to share with the remote (the Mac) and I’m not sure how to interpret what is apparently an error stating:

    “Failed to Connect to the disk C:/. the directory C doesn’t exist”

    I’ve tried naming the Export As: different things, to directories that exist on both the local and remote system but I’m confused about what it wants in the Export As: field. The error above was when I just used what it filled as the default, i.e. “C”




    Hello Kent
    Those error message could be given for various reasons and we have few steps that will help to solve this problem.

    1) First you can try to change name in “Export as” field.
    This is name of the folder which inside would be mounted disk.
    Change to something that doesn’t exist, because we don’t want to overwrite anything.

    2)Second its possible your account doesn’t have enough permissions to create directory on macOS, so make sure you have it. Try to create new folder there.

    3) Another reason could be that on installation something went wrong with drivers from disks.
    On Windows (even when its Client machine) its very important to restart computer when prompt come out on installation. Its important because otherwise drivers are not correctly installed.

    On macOS (Server machine) its important to allow NoMachine to install “third party drivers”.
    If those prompt was missed, you can check it under System Preferences -> Security & Privacy tab.
    *its possible to check it in less then 30 minutes after NoMachine installation.

    To list driver loaded on macOS use command:

    $ kextstat | grep nx
    You can get similar result as:
    $ kextstat | grep nx
    116 0 0xffffff7f80fcd000 0x5000 0x5000 com.nomachine.driver.nxau (4.1.b2) 78172556-B6A4-3112-BA41-E79D18108476

    Nxau is NoMachine audio driver, its loaded all the time. If its missing then installation went wrong, and system blocked our drivers. However, you can load it yourself.

    First shutdown nxserver:
    $ sudo /etc/NX/nxserver –shutdown
    Load kext file:
    $ sudo kextload /System/Library/Extensions//nxaudio.kext

    Now new window could appear on macOS with information about third party drivers.
    Then you can check it under System Preferences -> Security & Privacy tab, and allow to load/install those drivers.
    Last, start nxserver:
    $ sudo /etc/NX/nxserver –startup
    Now you should have nxau when you list kext files.

    About disks.
    Nxfs is driver from disks. If nxfs is missing you can connect from Windows to macOS and try to export disk from Windows to macOS, and then run kextstat command. Now it should appear.

    $ kextstat | grep nx
    168 0 0xffffff7f832c7000 0x5000 0x5000 com.nomachine.driver.nxau (4.1.b2) 78172556-B6A4-3112-BA41-E79D18108476
    170 0 0xffffff7f832cc000 0x12000 0x12000 com.nomachine.kext.nxfs (4.1.b1) BFEE045F-718B-31CD-AA31-0E114A139EB3

    Thats mean that driver is ok. If nxfs.kext is missing that you can load it manually like before, but
    its in other place:
    $ sudo kextload /Library/Application\ Support/NoMachine/Extensions/nxfs.kext

    And now you should see nxfs.kext driver.

    Also do you have problems with sharing other devices?
    Or maybe something is not working on specific machines?

    We also got helpful articles:
    NoMachine Installation Guide

    If above commands don’t help, please gather logs:
    How to collect logs.

    This instruction work on NoMachine 6 version as well. Any logs can be sent to forum[at]nomachine[dot]com


Viewing 2 posts - 1 through 2 (of 2 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.