Forum Replies Created
2FA via PAM, it gives you more flexibility, for example password plus one time codes (TOTP).
We don’t yet support ssh-key login with 2FA, however other methods can be used and configured via PAM, in similar way to demonstrated in following article:
I suspect one from the processes is eating up nearly all your CPU’s resources. Next time when it will happen please run ‘top’ command and show us results.
If you want to take control over FW settings please disable automatic FW configuration by changing that key in server.cfg:
# Enable the server to automatically configure the firewall for all
# the configured services. On platforms that don’t support adding
# the specific executables to a white list, the needed ports are
# added at server startup and removed at server shutdown, or when,
# at run-time, a new port is needed. The default value is 1.
# 1: Enabled. NoMachine opens the required ports in the firewall.
# 0: Disabled. Firewall must be configured manually. By default
# the required ports are TCP ports 4000 for NX, 4080 and 4443
# for HTTP and UDP ports in the range 4011-4999 range.
Hi, please check if firewall or anti-virus software doesn’t block external connections on your Mac client machine.
Your physical display may be not resizable becouse it’s headless.
If you turn off lightdm / X server a NoMachine will start one on it’s own, fully resizable.
Run the following command to update NoMachine audio support:
/usr/NX/bin/nxnode –audiosetup [<path>]
where <path> is an optional argument to specify the absolute path to PulseAudio configuration files (e.g. client.conf, daemon.conf, …) in a non standard location. For more information about this command please run /usr/NX/bin/nxnode –help.
Please check if you have Artsd daemon installed and running.
We found some unusual behaviour in logs you sent.
Can you tell us more about your Windows 10 edition and language variant?
We will try to reproduce a problem in our lab.July 17, 2017 at 08:48 in reply to: Could not connect to the server. Error is 111: Connection refused #15276
We found that you are trying to connect to local port 7025 with help of SSH protocol and that connection fail.
Port 7025 is not a default SSH port so please assure that you have a SSH daemon listening there on your local host (directly or via port forwarding or tunnelling).
Reconnection should take around 2 seconds but multiple factors can affect it.
Please send to us a logs from client and server and we will try to find a bottleneck.
Connection time depends on multiple factors, quality of WiFi, server and client hardware etc.
4/5 seconds is fine on weaker WiFI networks.
Ten seconds delay can be provoked by SSH server reverse DNS lookup procedure.
It can be disabled by setting ‚UseDNS’ key to ‚no’ in sshd_config on your server.