Step 4: Add VNC to the list of available session types in the server configuration file

Add value: vnc if it is not present yet.ĪvailableSessionTypes physical-desktop,shadow,unix-xsession-default,unix-gnome, vnc Uncomment and edit the AvailableSessionTypes key. Step 3: Add VNC to the list of available session types in the node configuration file

Specify path and name of the command to launch the VNC client: ensure that the CommandStartRFB key is not commented and set a proper value.įor example for TigerVNC, RealVNC and TightVNC: On host A edit the node configuration file: /usr/NX/etc/node.cfg. Step 2: Instruct NoMachine to launch the VNC client The VNC server is necessary only to provide the vncpasswd utility when it's not installed by the VNC client. If not, you need to install also the VNC server on host A. You can use for example TightVNC, RealVNC or TigerVNC.Ĭheck if the VNC password utility is available (try to execute the vncpasswd command) on host A. In case of multi-node environments (Enterprise Terminal Server + NoMachine Terminal Server Nodes), you need to perform the following operations on each of the NoMachine node machines you want to use for starting VNC sessions.Įnsure that VNC viewer is installed on host A. Host B, the VNC Server host to be connected via RFB. To enable VNC virtual desktop sessions, perform steps 1-4 below on the NoMachine host. In its current implementation, the VNC server doesn't have an empty password set. VNC sessions are supported by NoMachine NoMachine Terminal Server and Enterprise Terminal Server (or Enteprise Server for v.

Nomachine 4