0

New server (RHEL 7) in a very restrictive network environment that permits only a handful of ports for everything connected in the LAN.

22 is accessible and I'm wondering if it's possible to have NX Server use 22 for NX protocol (and not SSH). By definition, NX requires a high number port, so I was wondering if there was a way to listen also to 22.

NX protocol seems to work better for us and it would be great if we could keep it.

Is there a way to tunnel NX, which is setup for port e.g. 4000 to listen to 22, which is open for ssh?

Thank you

Ivy
  • 1
  • 1
  • Why using NX when there is X2go based on same protocol, but it is free and without restrictions? And yes, it uses port 22 exactly with the help of SSH, by using a port forwarding, and that is very good thing because you'll gain a key-based auth and all that security at no cost. – Nikita Kipriyanov Oct 24 '19 at 20:13
  • I'm a huge X2Go fan and I've been using it for years (>5). We moved to NX since in this deployment (all RHEL in my experience) is more responsive, works better with RStudio, and the probability of losing a session is smaller. – Ivy Oct 24 '19 at 22:39
  • It boils down to: can we tunnel MachineNX, which is listening to a high port (e.g. 4000) to 22, which is open for ssh? – Ivy Nov 07 '19 at 23:45

0 Answers0