Cannot connect, screen sharing is disabled

Forum / NoMachine for Mac / Cannot connect, screen sharing is disabled

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #24218
    MadMartian
    Participant

    I cannot connect to my Mac with NoMachine.  It produces the following message on the client machine:

    “Error: Cannot connect to the desktop, screen sharing is disabled”

    I don’t even understand what that means, how can screen sharing be disabled? I didn’t even think that was possible.  I am using version 6.8.1 on both the Linux client and the Mac server.

    #24237
    Gega
    Participant

    Hello,

    This means that for some reason you’re not allowed to access physical display of current user. This can happen any of this
    three reasons:

    1)LoginScreenAccess is set to 0 in server.cfg and system is in login window state.
    2)You’ve changed settings by clicking on nxclient monitor menu and disabling “Accepting connections”, in this case nxclient monitor
    icon will be grayed out.
    3)PhysicalDesktopSharing from server.cfg is set to either 0 or 2 and connecting user has no permission to access physical display.

    #24247
    MadMartian
    Participant

    It was none of those three points, but I turned on debug logging for the server and found this:

    2019-10-25 01:29:14 259.343 71811 NXSERVER Get nodes sessions.
    2019-10-25 01:29:14 259.624 71811 NXSERVER Server config type: unix-remote,physical-desktop.
    2019-10-25 01:29:14 259.776 71811 NXSERVER Server config internal types: foreignDesktop,physicalDesktop,
    2019-10-25 01:29:14 259.876 71811 NXSERVER Sessions available on node localhost:4000: foreignDesktop,physicalDesktop,.
    2019-10-25 01:29:14 260.035 71811 NXSERVER Searching nodes in database.
    2019-10-25 01:29:14 260.138 71811 NXSERVER Amount of nodes in array: 1.
    2019-10-25 01:29:14 260.243 71811 NXSERVER Check session resources for nodes: localhost:4000.
    2019-10-25 01:29:14 260.569 71811 NXSERVER Session type: virtualApplicationDefault is not available.
    2019-10-25 01:29:14 260.650 71811 NXSERVER Session type: virtualRDP is not available.
    2019-10-25 01:29:14 260.749 71811 NXSERVER Session type: virtualUnixApplication is not available.
    2019-10-25 01:29:14 260.862 71811 NXSERVER Session type: virtualConsole is not available.
    2019-10-25 01:29:14 260.950 71811 NXSERVER Session type: foreignDesktop is available.
    2019-10-25 01:29:14 261.030 71811 NXSERVER Session type: virtualXdm is not available.
    2019-10-25 01:29:14 261.121 71811 NXSERVER Session type: virtualDefault is not available.
    2019-10-25 01:29:14 261.236 71811 NXSERVER Session type: virtualGnome is not available.
    2019-10-25 01:29:14 261.337 71811 NXSERVER Session type: physicalDesktop is available.
    2019-10-25 01:29:14 261.415 71811 NXSERVER Session type: customForeignMaster is not available.
    2019-10-25 01:29:14 261.512 71811 NXSERVER Session type: virtualAttach is not available.
    2019-10-25 01:29:14 261.619 71811 NXSERVER Session type: virtualDesktop is not available.
    2019-10-25 01:29:14 261.720 71811 NXSERVER Session type: virtualVms is not available.
    2019-10-25 01:29:14 261.847 71811 NXSERVER Session type: virtualVnc is not available.
    2019-10-25 01:29:14 262.018 71811 NXSERVER Session type: nxFrameBuffer is not available.
    2019-10-25 01:29:14 262.142 71811 NXSERVER Session type: physicalDesktop is available.
    2019-10-25 01:29:14 262.270 71811 NXSERVER Session type: virtualKde is not available.
    2019-10-25 01:29:14 262.404 71811 NXSERVER Session type: nxConsoleShadow is not available.
    2019-10-25 01:29:14 262.519 71811 NXSERVER Session type: nxConsole is not available.
    2019-10-25 01:29:14 262.609 71811 NXSERVER Session type: virtualCde is not available.
    2019-10-25 01:29:14 262.717 71811 NXSERVER Session type: physicalDesktop is available.
    2019-10-25 01:29:14 263.016 71811 NXSERVER Get value result for class: session is type unix-script,connections-limit,virtual-desktops-limit with value .

    I managed to resolve this by completely purging NoMachine from my system including deleting ~/.nx/ recursively, then reinstalling and it connects now.

    #24262
    Britgirl
    Participant

    That output doesn’t tell us what was wrong, and purging means that the logs we could have looked at are now lost, so we can’t investigate further. If it happens again, let us know.

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

This topic was marked as solved, you can't post.