Forum Replies Created
-
Posts
-
The current version is now 8.10. Please update your NoMachine client and server side software if you haven’t done so already 🙂
Can you reproduce this problem regardless of the client OS you are connecting from? You wrote you have 4 Linux Mint systems, so I assume you are connecting between them. Is it possible for you to test from a different OS? E.g a connection from Windows to the affected system. I think you also contacted us via Report Issues, if you did, please follow the instructions you received by email 🙂
Update: problem disappeared after applying system updates.
Did you add the private key in the player as well? The last section of this article
https://kb.nomachine.com/AR02L007851. Launch the NoMachine User Interface from Programs menu or Applications and right click on a connection. Choose ‘Edit connection’Â to access connection settings.
2. Be sure that NX is the selected protocol in the drop-down menu.
3. Go to Configuration panel and choose ‘Use key-based authentication with a key you provide’ and click on Modify.
4. Select the private key and check ‘Import the private key to connection file’ if you want to save it for that session.
5. Back to the previous panel and click on Connect
The client will prompt you for username and passphrase.
Check the IP addresses for that connection by going to ‘Edit connection’. Then select an alternative one if there are multiple ones available. A screenshot showing what I mean is and my explanation https://forum.nomachine.com/topic/how-to-make-nomachine-update-target-computer-ips#post-39467
Wake On Lan works by sending so called “Magic Packets”, which are packets of the second layer (MAC). VPN emulates and works on the third layer IP. WOL on its own does not use the IP address of the destination host, it uses its MAC address. NoMachine translates the IP address to the MAC address based on the routing table. In the Magic Packet only the MAC address is used.
Magic Packet is a broadcast packet, therefore it is not possible to route it through VPN without special configuration of the VPN itself provided that the VPN supports it, so you should check this in the VPN you are using.sk.bsd, take a look at this Trouble Report which we opened for a similar issue to the one you are describing
https://kb.nomachine.com/TR07U10921
As a temporary workaround, disable Wayland.
embee999, your issue is also known https://kb.nomachine.com/TR10U11031. There is a workaround in the TR.
Take a look at the third option in this https://kb.nomachine.com/AR03P00973. Use the proper command to stop the X server according to your display manager and then restart the server.
https://kb.nomachine.com/AR03P00973
If the tips don’t help, tell us the desktop environment and send us the logs.
https://kb.nomachine.com/DT07S00243.Can we assume you are the latest version which is 8.10? We are not aware of white screen issues as you describe when connecting to Windows or other OSes (you wrote Linux client under XFCE to Windows 10 server). Any white screen issues similar to yours that we encountered in earlier versions have been fixed (you can take a look in the Trouble Reports section of the knowledge base to search them). We are aware of ONE issue connecting to Linux which temporarily shows a white screen and then disconnects with an error, but this does not appear to be your case (it appears when connecting to KDE/Plasma desktop, as well as disconnects with an error). You can find it here:
White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
https://kb.nomachine.com/TR07U10921We’re happy to investigate your issue, but to do that we need to know:
– the Linux distribution/version you’re connecting from
– the graphics card installed on the both sides
– logs from the affected machine (https://kb.nomachine.com/DT07S00243) You can submit them to forum[at]nomachine[dot]com.Improvements to support for HiDPI displays is still of course planned. We’ve not dedicated the necessary resources simply because of other development priorities related to version 9 and NoMachine Network. Once v9 is out, can start on adding an option to make the session “DPI Aware”
I updated NoMachine on my Mac this morning, and after the update, when I connect to the remote, I can see the screen, but when I move the mouse inside the NoMachine remote window, I don’t see a mouse cursor.
What version of NoMachine was running before you updated?
Can you update to the latest (8.10) and check if the same issue occurs?Logs would be useful in that case.
We are aware of a white screen issue with Wayland. It’s related to KDE running on Ubuntu 22-based versions (also Kubuntu). You can indeed try KDE 5.27. The workaround is to disable Wayland and use X.Org.
Please use the following link to track its status:
White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
https://kb.nomachine.com/TR07U10921Hi, what you need is the Workstation product. It’s available in evaluation from the download section of the website here:
https://downloads.nomachine.com/download-enterprise/It lets you run up to 4 “virtual desktops” on the same machine which are also persistent.
Hi ziggy,
we weren’t able to reproduce with or without a KVM switch. So, we need logs from the server 🙂
Follow the instructions here and send them to forum[at]nomachine[dot]com.
How often we make a maintenance release generally depends on what tweaks and fixes have been added. It can be once a month or it can be every 2 or 3 months. If you take a look at the Software Updates section, you can see how often we release updates. We are still waiting for the RPi5 devices we ordered, so that’s why we have not officially “added support” yet (i.e we did not add it to the devices in the download section of the website, nor mention it in our latest release announcement). Adding “support for a distro or OS version, or a device” means that we have tried and tested it in our labs 🙂 In the case of RPi boards in general, there is the issue with Wayland, so please use X.org instead.