Configuring /usr/NX/etc/server.cfg for SSH access on centos6

Forum / NoMachine for Linux / Configuring /usr/NX/etc/server.cfg for SSH access on centos6

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #16467
    jaimepinto
    Participant

    Simple request: If you have your NX server version 6+ working on Linux such that it will authenticate NX clients accessing the server via SSH, please paste here the uncommented lines

    # cat /usr/NX/etc/server.cfg  | grep -v \# | sort -u

    Assume I have ‘NoMachine Enterprise Desktop v6+’ or  ‘Workstation v6+’ Subscription for Linux. I don’t care for NX protocol or port 4000. I only care about standard ssh authentication over port 22 using trivial Linux shadow/pam/ssh/sss services under Linux.

    Thanks

    Jaime

    #16500
    jaimepinto
    Participant

    Very interesting! I didn’t have to do anything on the server (after a 2nd fresh install). I just set the v6+ client to use SSH on port 22, and somehow the server picked up the connection.  Inbound port 4000 to the server is blocked. I guess the developers at NX know what they are doing.

    Thanks

    Jaime

    [root@libra etc]# cat server.cfg | grep -v \# | awk ‘{if ($0 != “”) print $0}’
    ConfigFileVersion 4.0
    EnableUPnP NX
    EnablePasswordDB 0
    ClientConnectionMethods NX,SSH,HTTP
    SSHAuthorizedKeys authorized_keys
    AvailableSessionTypes unix-remote,unix-console,unix-default,unix-application,physical-desktop,shadow,unix-xsession-default,unix-gnome,unix-kde,unix-xdm,windows,vnc
    Section “Server”
    Name “Connection to localhost”
    Host 127.0.0.1
    Protocol NX
    Port 4000
    EndSection

     

     

     

    #16506
    Britgirl
    Keymaster

    Something obviously went wrong when you first installed – possibly old lic files interfering from an earlier version.

    SSH is meant to work out of the box, so when the user selects in SSH in the connection set-up, the rest is done for them.

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

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