jaimepinto

[jaimepinto]

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

 

 

 

[jaimepinto]

Am I understanding correctly that to re-accomplish that previous functionality from 3.5  now (under 4) I’d need to purchase the following, at least:

* NoMachine Workstation Subscription (linux): $  124.50

* NoMachine Small Business Server Subscription (linux):$  744.50

This is strictly for personal use. I have a linux desktop at work from which I assume 3 persona at the localhost level, with the GUI logins permanently on, and regularly access that desktop remotely from 3 Windows clients at different locations behind firewalls. With the above subscriptions would I regain the straight SSH client connection as well, mute on the free versions (ie, no need for tunnels)?

Thanks

Jaime

[Author]

Posts