nomachine_nx_remote_access_for_unix_linux_v4
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
nomachine_nx_remote_access_for_unix_linux_v4 [2013/12/17 19:56] – juckins | nomachine_nx_remote_access_for_unix_linux_v4 [2013/12/17 20:00] (current) – juckins | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | NX client v3 cannot connect to NX server v4 via SSH; only via NX. SSH connections are only supported with a paid server v4 version. | + | __Installation instructions__ \\ |
+ | [[https:// | ||
- | __Linux | + | __Compatibility between v3 and v4__ \\ |
+ | [[https:// | ||
+ | |||
+ | Note: NX client v3 cannot connect to NX server v4 via SSH; only via NX. SSH connections are only supported with a paid server v4 version. | ||
+ | |||
+ | __Setting up a Linux to Linux connection__ \\ | ||
Installing nomachine_4.0.369_1_i686.rpm on both the server and the client works, except that on the server iptables needs to be turned off. The appropriate rule is to allow TCP port 4000 and UDP port 4722. Use system-config-firewall to add 2 custom rules. | Installing nomachine_4.0.369_1_i686.rpm on both the server and the client works, except that on the server iptables needs to be turned off. The appropriate rule is to allow TCP port 4000 and UDP port 4722. Use system-config-firewall to add 2 custom rules. | ||
Also note that once the NX connection is established to the target machine, a new virtual desktop session is not established as in NoMachine v3. Rather the behavior is like Windows " | Also note that once the NX connection is established to the target machine, a new virtual desktop session is not established as in NoMachine v3. Rather the behavior is like Windows " | ||
nomachine_nx_remote_access_for_unix_linux_v4.1387328171.txt.gz · Last modified: 2013/12/17 19:56 by juckins