Forum Replies Created
-
Posts
-
Hi, yes it is possible and it’s done using the concept of “profiles”. The Cloud Server already supports a system of rules which can then be inherited by its nodes. We implemented this for a number of important server workings and features so that specific rules related to, for example, clipboard, file transfer, audio, recording and others are propagated from the Cloud Server (or Enterprise Terminal Server) to any of its nodes to allow or disable a service, feature or session type. You can see more about this in the Cloud Server guide https://kb.nomachine.com/DT09S00252#4.5.
We are working to extend the configuration and security options that are made available by the system and that are enforced and eventually negated, and reverted, by the master (Cloud in your case) server in future versions.
So,
Windows local host OK
Windows to Linux (both) Not OK
Linux (both) to Windows OKThis is probably something to do with the package you have installed. Did you install the free edition everywhere? Make sure you didn’t install an Enterprise Client package which does not include the server component. Also, check that you downloaded and installed the correct software package for your system’s architecture. So if you have a 64-bit system, and installed a 32-bit package, remove it and download and install the 64-bit package.
If everything is correct, send us the server side logs (one of the Linux systems) after you have reproduced the problem. So enable debug according to the instructions here, https://kb.nomachine.com/DT07S00243, connect from Windows or the other Linux host, reproduce the error and then gather logs. You can send them to us via email (forum[at]nomachine[dot]com) or attach here.
Hi, yes this is possible on immutable systems, including with the free edition. Take a look at our article in the knowledge base and let us know if you have further questions:
How to install NoMachine on Fedora Silverblue and other Immutable Systems
https://kb.nomachine.com/AR03V01225Thanks Cytan299 for the update. That’s good to know.
IndianaM1ke, can you update your macOS like Cytan299 did and tell us if the issue is resolved for you?
Sorry for not updating you. We have been trying to reproduce the error using your exact set-up and steps but without much luck. However, there is a TR already open on a similar issue related to Windows client connecting to Gnome, upon using the Right-Ctrl + Shift + V in the session, it toggles the control key press. It might be related to this. Can you check if the workaround can help in your case?
We need to clarify better what is the client OS you are using to connect from and what is the server OS host you are connecting to when you encounter this issue. You mentioned that you turned hardware encoding off on the Ubuntu client. HW encoding is turned off on the server. On which Ubuntu machine did you disable HW encoding?
We understand that you are connecting from the macOS or Ubuntu 24.04 (clients) to the Ubuntu 22.04 server? Is this right?
Is it only when you connect from Ubuntu 24.04 to the Ubuntu 22.04 server that you have this problem? If so, you could try disabling hardware decoding on the Ubuntu 24.04 client. To do this follow the instructions here https://kb.nomachine.com/AR07U01202 making sure to set the option key=”Enable hardware accelerated decoding” to value=”disabled”.
Hi, thanks for your feedback. NoMachine is a commercial software but we do release some components to the public, and you can find them here: https://downloads.nomachine.com/opensource/. Indeed, hardware encoding on ARM is not currently supported in NoMachine. It is planned though! Other features coming in version 9 were prioritized, but it is definitely something we are going to add.
Hi, unfortunately there is no other alternative workaround other than using X11, but if you send us the server side logs, we can check to see what the problem is with the other capture methods? Send them to forum[at]nomachine[dot]com. The instructions are the same as before 🙂 https://kb.nomachine.com/DT07S00243, steps 1, 2 and 3 for the server machine you are connecting to.
Also useful to know:
i) Is the server running in a VM?
ii) Are you using proprietary drivers? If you are, can you possibly try the open source ones?
There is another topic with a workaround, can you try it?
This looks like the following known issue with Plasma 6, https://kb.nomachine.com/TR05V11141.
Hi, can you try disabling hardware decoding on the client machine that you are connecting from? See the article for further instructions making sure to set the appropriate key to “disabled”.
How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202Can you send us the client side logs (the device that you are connecting from)? Please take a look at step 4 in the instructions here, https://kb.nomachine.com/DT07S00243. We don’t need server side logs for the moment.