Upgraded NoMachine, lost server access

Forum / NoMachine for Mac / Upgraded NoMachine, lost server access

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #54748
    ziggy
    Participant

    I just upgraded NoMachine on my Mac, from 9.1.24_6 to 9.2.18_1 (free version), and since the upgrade, I’ve lost the ability to make remote access to that computer through NoMachine.

    This particular box is a 2020 Mac Mini with an M1 processor that is running Sequoia 15.7.1

    On the client machine I have a pre-defined connection point defined for the server, although there is also an auto-detected connection offered.  Prior to the upgrade, I could use either of these to connect to the server.

    Since the upgrade, if I use either of these contact points, NoMachine reports “no available desktops on this server”.  Right now, my suspicion is that I’m seeing a structural issue with NoMachine, rather than a MacOS permissions issue.   I’ve checked and all the system permissions I can find are OK.

    From a command line I ran nxserver –status, and it reports that nxserver and nxd are active, but that nxnode is disabled, and I think that’s the source of my problem.  I ran nxserver –shutdown and the nxserver –startup and the result still reports that nxnode is still disabled.

    On a whim, I did another shutdown and then disabled the permissions for screen recording, but when I re-ran a startup, I didn’t get a prompt for enabling screen recording permissions.

    There’s probably something small here that I’m missing, but I don’t see what it is.  Any clues of how to resolve?

    Other potentially relevant information:

    – I’m seeing the same behavior with access attempts from NoMachine 9.1.24_6 free version from connection attempts from both Win 11 and Linux Mint 21.3 (with Cinnamon desktop), although both of these connections were working reliably before the upgrade of the Mac.

    – For the Mac, the display is set up with a KVM connection, and where remote connection attempts are happening when the KVM is switched to a different display (namely, the computer attempting to connect).

    Any chance that downgrading the Mac back to 9.1.24_6 would resolve this problem?

    TIA

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic. Please login .