Questions regarding nxserver –nodeadd

Forums / NoMachine Terminal Server Products / Questions regarding nxserver –nodeadd

This topic contains 1 reply, has 2 voices, and was last updated by Avatar Haven 1 month ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #22979
    Avatar
    itguy92075
    Participant

    Hello,

    I have a couple of questions regarding the adding of nodes to a terminal server, version 6.7.6.  In a test use case I have:

    + /etc/NX/nxserver --nodeadd 192.168.1.243 --label 192.168.1.243 --limit 1 --strict-host-key-checking no

    which errors out when the node’s originally-assigned terminal server is down or dead:

    NX> 190 Connected to NX Node.
    NX> 500 ERROR: Cannot add node 192.168.1.238:4000. This node is running on a
    NoMachine server with a multi-node setup enabled.

    Is there a way I can configure this to override the previous registration?

    In another case, I get prompted to answer a question where the documention says the question should be suppressed:

    + /etc/NX/nxserver --nodeadd 192.168.1.243 --label 192.168.1.243 --limit 1 --strict-host-key-checking no
    NX> 190 Connected to NX Node.
    NX> 763 Could not authenticate on the remote node using server's public key.
    NX> 763 Would you like to login on the remote node as a privileged user to add
    NX> 763 this key and try again? [yes|no]:

    Am I misunderstanding the docs?

    #22999
    Avatar
    Haven
    Contributor

    hello itguy92075,
    The error “This node is running on a NoMachine server with a multi-node setup enabled” is printed when we are still detecting an active connection with the other multi-server. If ‘originally-assigned terminal server’ is down, it sometimes requires a few moments to close the connection.

    Is there a way I can configure this to override the previous registration?

    To be sure that remote node is no longer aligned with multi-server keys you have to remote access public keys. On Linux: ‘/var/NX/nx/.nx/config/authorized.’ for NX protocol and restart NoMachine Server on that node.

    ‘–strict-host-key-checking’ option is for automatically save the host key. A host key is a cryptographic key used for authenticating computers. This is the first step when connecting to a new host. In next step server detects that cannot access the terminal server Node with the public key, we have to log in to the remote node to add this key to get access to that host. We need privileged user credentials to do that.

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

You must be logged in to reply to this topic.