Forum Replies Created
Please assure that ports used by NoMachine are not blocked by firewall.
By default these ports are:
4000 in case of NX protocol
22 in case of SSH protocol and NoMachine server installed on Linux or Mac
4022 in case of SSH protocol and NoMachine server installed on Windows
Looks like you have installed 32 bit NoMachine package on 64 bit system.
Please remove 32 bit version and install correct, 64 bit package or install 32 bit compatibility library.
We found that key you are trying to do contains obsolete options, no longer used in NX 4 and 5.
Please don’t add ‚no-port-forwarding,no-agent-forwarding,command=”/usr/NX/bin/nxnode”’ to key you are trying to use for SSH System authorisation.
Additionally SSHD fails to decode your key.
Please generate new one, add it to your .ssh/authorized_keys2 and use in player as explained in following article:
In System login case it looks like the key you are trying to use is not added into .ssh/authorized_keys2 file in your home directory on server.
NoMachine login case is more complicated and we need nxserver.log and nxerror.log files from your server to analyse the problem.
Logs you collected are not enough detailed to provide any hint. Please increase SSHD LogLevel from INFO to DEBUG3 and restart daemon. If you are worry about your privacy please remove all sensible info from collected logs.
Additionally please explain step by step how you try to login and when it works and when not. All of it will help us to understand problem.
Please enable debug in your SSH daemon on server and show us logs from failed attempt.June 6, 2017 at 09:23 in reply to: Restrict NoMachine to listen on a particular interface #14998
We have verified it and setting rtlocalhost to local interface as we perviously suggested doesn’t have any effect.
You can set it to IP of your real interface.
Binding to interface specified in option works only if server cannot establish UDP connection to client first .
Instructions how to connect to NoMachine when the server is behind a NAT router or a firewall you can find there: https://www.nomachine.com/AR11L00827.May 23, 2017 at 12:19 in reply to: Restrict NoMachine to listen on a particular interface #14877
Please set ProxyExtraOptions „rtlocalhost=127.0.0.1” in node.cfg.May 16, 2017 at 15:14 in reply to: Restrict NoMachine to listen on a particular interface #14814
Right now it’s not possible to restrict listening in nxnode.bin to particular interface. However it’s possible to disable TCP and use UNIX sockets which are local by definition. It can be done by setting DisplayServerExtraOptions “-nolisten tcp” in node.cfg. We will consider providing a config file key for better control and selecting particular interfaces.
Please take a look at ‚PhysicalDisplays’ key in node.cfg file.December 28, 2016 at 11:23 in reply to: Cannot use authentication with SSH/SSL key – free version #13308
Please follow article about setting up key based authentication.
You Linux machines have to be prepared in advance to have a correct key with correct IP of Windows server.
Depending on protocol you use you have to store server key in following files:
~/.ssh/authorized_keys for SSH protocol
~/.nx/config/client.crt for NX protocol
More about keys used in NoMachine can be found here:
Yes, you should use Player installed on your server to connect to custom session on localhost. Player is a part of Server installation so you should have it already installed.
It’s currently not possible to automatically enable/disable broadcast or permit/deny incoming connections when you move to different location.
This can be archived with help of system scripts where you can detect changes in network interfaces and reconfigure NoMachine configuration files.
To filter incoming connections you can use a system firewall or prepare a custom script that NoMachine will executed before login – ‘UserScriptBeforeLogin’. Please take a look at article about custom scripts: