The client window is however responsive: open the NoMachine menu by ctrl+alt+0, enter the Display -> Change settings panel and check at the bottom left: it should show ' codec Unknown'. When connecting to the Wayland-based desktop, the user gets a blank screen. A possible solution for both cases is to disable Wayland, or when this is not possible, to try any of the options explained below. Note that even in this case, some issues can still occur when the proprietary drivers of the video card are installed. In case of a Wayland-based desktop, NoMachine adopts a variety of methods to interact with it, but at the moment these methods are effective only when the Operating System is running on a physical host.
The same applies to the NoMachine software, that can be installed on a physical or virtual host to provide access to its desktop. These Wayland-based desktops operate also when the Operating System runs on a bare-metal virtual machine or in virtual machine on a hosted hypervisor like VMware Workstation Player, VirtualBox, KVM, VMware ESX. Fedora 31, OpenSUSE 15, Ubuntu 19.10 or later) provide support for desktop environments relying on Wayland compositor. Many recent Linux operating systems (e.g. Use the NX Connection Wizard to set up new connection profiles for your servers, and select Advanced to go into the menu that will allow you to point to the key for a particular server.This article applies to NoMachine v. Use /usr/NX/bin/nxserver –help to see options.Ĭonfig file: /usr/NX/etc/server.cfg (though I didn’t have to edit anything here by default)įinally: sudo /usr/NX/bin/nxserver -restart On Mac, you can create an NX folder under your home folder and scp the key with an appropriate naming convention to remember which server it is for. Later you can point to the appropriate key in your NX Client config. The key on the server is located in: /usr/NX/share/keys/default.id_dsa.key.įor Windows client machines, you will need to copy the key to “C:\Program Files\NX client\Windows\share\keys\” with a distinct name. Now we’ll need to copy the secure key that was generated onto the client machines so that your NX client can use it. Update permissions: chmod 640 /usr/NX/home/nx/.ssh/authorized_keys2 Start the service: sudo nxserver –restartĭownload and install the nxclient, nxnode, and nxserver rpm packages for your architecture:ĭownload the Windows/Mac NoMachine NX client for your desktop.Ĭreate a new ssh key pair in /usr/NX/share/keys/: sudo /usr/NX/bin/nxserver -keygen.NX NoMachine (Free Edition) is a great tool to take remote control of a Linux server desktop.
0 kommentar(er)
