ggham

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Unable to connect remote disk #20025
    ggham
    Participant

    Dear s.meliss,

    For instance you can test installing FUSE(https://osxfuse.github.io/) package that should contain
    .kext files, and check if you encounter same problem with it.

    I’m not sure if new login with admin rights solves the issue, since I haven’t identified the problem,
    but as a workaround you could try to disable SIP(System Integrity Protection) temporarily and then
    re-enable again after installing NoMachine and checking if disk is forwarded. I found this guide
    that describes steps required to disable and then re-enable SIP:
    https://support.intego.com/hc/en-us/articles/115003523252-How-to-Disable-System-Integrity-Protection-SIP-

    in reply to: Unable to connect remote disk #20008
    ggham
    Participant

    Dear s.meliss,

    The way to enable the extension is triggered by trying to load it for the first time, it can be done by either installing NoMachine, or doing it manually and you’ve tried both.

    Since you weren’t prompted with a dialog by system in either case, it makes me think the issue is something different, but I haven’t yet been able to identify the problem. Have you tried installing/loading other third party kernel extensions? I’m wondering if they’ll output the same error as nxfs.kext file.

    in reply to: Unable to connect remote disk #19996
    ggham
    Participant

    Dear s.meliss,

    This looks like a different problem to system policy preventing to load kext file.
    From the error displayed, it could be that NoMachine installation didn’t set up proper
    permissions to nxfs.kext file.

    Could you please check the output of ls -ld /Library/Application\ Support/NoMachine/Extensions/nxfs.kext/
    it should be similar to drwxr-xr-x 3 root wheel. If the output is different, please try these two commands:
    sudo chmod -R 755 /Library/Application\ Support/NoMachine/Extensions/nxfs.kext/
    sudo chown -R root:wheel /Library/Application\ Support/NoMachine/Extensions/nxfs.kext/

    If this is not the case, and nxfs.kext still fails to load, please check if anything needs to be
    allowed in “System Preferences -> Security & Privacy -> General”(check AR01P00962) tab,
    just to be sure it’s not the issue described in the article, also, please try to load nxfs.kext using
    kextutil, since it will give more information in case of failure:
    sudo kextutil -t /Library/Application\ Support/NoMachine/Extensions/nxfs.kext/

    Thanks

    in reply to: Unable to connect remote disk #19979
    ggham
    Participant

    Hello s.meliss,

    To make sure that this is the same issue as described in AR01P00962, please check the output of command  kextstat | grep nxfs after trying to mount a disk. If no output is shown, then you could try to load  the nxfs.kext file manually, with command sudo kextload /Library/Application\ Support/NoMachine/Extensions/nxfs.kext/,  if it fails to load for the same reason as described
    in the article, you can proceed with following described steps(from AR01P00962).

     

    If nxfs.kext file fails to load even after following the steps, please share nx-related system logs with us(output of cat /var/log/system.log | grep nx).

    in reply to: Windows device mount issues #18250
    ggham
    Participant

    Hi dmongan,

    We are aware of the link creation problem on Windows, and will soon have a patch that fixes the issue. We’ll make sure to notify you as soon as the patch is availabe.

    As for the permissions issue, we will investigate the problem and give you further feedback about that too.

    in reply to: NoMachine Player stops working #15033
    ggham
    Participant

    Hi totalizator,

    We received your email, that provided more information about the problem, however, we were unable to recreate the crash with the set up you described(Antergos / Arch Linux with Client 5.2.21-1, Server 5.2.11-1 – Ubuntu).

    The information you provided included the stack trace of the crash, but without being able to reproduce, the stack trace is insufficient for us to find the cause of the problem. Could you please provide the full set of logs as described here: https://www.nomachine.com/DT07M00098, so that we can continue with investigation?

    Send them to forum[at]nomachine[dot]com making sure you reference the topic title.

    Thanks

     

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