Forum Replies Created
Using NX protocol, and there is no $HOME/.nx/config/client.crt. Only player.cfg is there. All directories are owned by my user.
I don’t have any $HOME/.nx/R-*, only F-M* and M-* directories. The latest session says:
3233 3233 18:45:06 625.628 Socket: WARNING! Can’t create the IPv6 socket.
3233 3233 18:45:06 625.837 Socket: WARNING! Error is 97 ‘Address family not supported by protocol’.
Info: Slave server running with pid 3264.
Info: Listening to slave connections on port 25001.
3233 3233 18:45:06 730.617 ClientSettings: WARNING! Creating the list of favorites.
3233 3233 18:45:06 730.807 Main: Starting NoMachine Client version ‘4.4.12’.
3233 3233 18:45:06 776.269 OsDetect: Setting os type to ‘CentOs’.
3233 3233 18:45:06 776.289 Main: Creating a new connection monitor.
3233 3233 18:45:07 573.413 ClientThread: Creating new thread.
3233 3233 18:45:07 850.704 MonitorService: Enabled drag and drop feature.
I agree it shouldn’t change. I’ve only installed NX once on all my machines, yet every day it complains that the key has changed. Same details, in fact I’ve created icons with the IP, port and other settings, which has never changed.
Here’s how I use it, in case it makes a difference. I run nxserver on the remote CentOS 7 machine. (installed with rpm) The server starts with systemd. In the config file I’ve changed each port it listens to, to reflect the IP of that host, for example 192.168.1.14 listens to port 4014. On the client machine, I set up a reverse SSH tunnel, which reaches out to the remote machine, takes 127.0.0.1:4014, and brings it back to the client through the tunnel, so 4014 then shows up on the client at 127.0.0.1. On the client when I hit the icon, it goes to 127.0.0.1:4014 and the machine reaches into its bellybutton and gets 4014 from the remote machine as if the remote server is local.
I’ve used reverse SSH tunnels for many years, to extend all kinds of services, and I can’t see why it would have an effect on the NX keys, but I thought I’d explain my method. Also my method is the reason I wish there were a way to make nxserver listen only on 127.0.0.1, as I don’t want anything listening on outside interfaces for security reasons (in case the firewall is ever compromised).
Thank you, that works.
Another question: Every morning when I start sessions on the various remote machines, it always says the remote host key has changed, and I have to approve the new key. This should not happen, and could mask cases where the key has actually changed maliciously. Why is this happening?
I don’t have a Documents directory. I do have ~/.nx/config/Hex.xns which I drag from file manager to the desktop itself (KDE), but it never appears on the desktop. I try clicking on Hex.nxs in the file manager, but nothing happens.
Normally what I do is Edit the Start menu and create a new object there. I have to give the command which is run to start that object, but no commands work that I’ve tried so far.
What is the actual mechanism of how this is supposed to start? Isn’t an executable supposed to be associated with .nxs files?
Thanks, but nothing works.
bash: /home/bill/.nx/config/Hex.nxs: Permission denied
$ /usr/NX/bin/nxclient /home/bill/.nx/config/Hex.nxs
20161 20161 07:38:06 327.178 Socket: WARNING! Can’t create the IPv6 socket.
20161 20161 07:38:06 327.360 Socket: WARNING! Error is 97 ‘Address family not supported by protocol’.
$ /usr/NX/bin/nxclient.bin /home/bill/.nx/config/Hex.nxs
/usr/NX/bin/nxclient.bin: error while loading shared libraries: libqt.so: cannot open shared object file: No such file or directory
$ /usr/NX/bin/nxnode.bin /home/bill/.nx/config/Hex.nxs
/usr/NX/bin/nxnode.bin: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory