The NoMachine service is not available or the access was disabled on host

Forum / NoMachine for Linux / The NoMachine service is not available or the access was disabled on host

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #249
    techiedjf
    Participant

    I installed the latest version of nomachine on a LINUX x64 RHEL 6 server. I have tried many attempts to get my Windows client to connect to the LINUX server. I keep receiving the error, “The NoMachine service is not available or the access was disabled on host….”

    I cannot find any documentation for a simple for the “Use the NoMachine login” option.

    Any help much appreciated!

    #252
    titan
    Participant

    Double click on the connection (that you maybe created with a 3 client and that was then imported to the 4 by using the same protocol settings). When the client is showing the connection details click on Edit and change the Protocol to NX.

    There is clearly a communication problem on our side, albeit these situations are generally difficult to handle “automatically”. Future versions will offer the choice of switching to the NX protocol if SSH connections fail with this error.

    #268
    techiedjf
    Participant

    I am using a brand new OS and fresh install (rpm and tried tar), but I get the same connection problems.

    I did try both SSH and NX, but no success in connecting.

    #271
    Anonymous
    Inactive

    I had the same message and found these two articles useful in the KB:

    “The NoMachine service is not available or NX access was disabled on host” is shown
    http://www.nomachine.com/AR11K00751

    and also this:
    http://www.nomachine.com/AR04J00627

    The second is only valid though if you are trying to connect to 3.5.0. You mention you installed version 4 on your Linux machine, so it must be something else. What do the logs say?

Viewing 4 posts - 1 through 4 (of 4 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.