Forum Replies Created
December 2, 2020 at 12:53 in reply to: Lag in refresh with NoMachine 6.12.3 Kubuntu 16.04 #30615
What version did you update from? Has anything changed on your Linux host?December 1, 2020 at 17:03 in reply to: Remove Screenshot option from NX Player or not to allow in NX Server #30599
You can compare the free version and its enterprise-oriented sister product here: https://www.nomachine.com/remote-access-for-everyone. You should be looking to install Enterprise Desktop on the computers you want to access if you or your client are using the software in a commercial environment. Contact Sales for more info about this and the differences between the two products for your specific needs.
Disabling the screenshot feature is possible by preventing access to the “Connection information” dialog. Take a look at the ClientMenuConfiguration key in the server.cfg and remove “connection”.
Regarding your comments about our online knowledge base, we are already working on improving this by removing/moving documentation which can now be considered irrelevant (such as articles etc about our legacy products 3.5 and version 4). In an ideal world there wouldn’t be any need for support 🙂 but that proves to be a an impossible feat even for providers of operating systems, let alone for the ISV’s that make the programmes to run on them. All the more reason to make sure help resources are easy to find. In any case, we appreciate the feedback you’ve provided because it gives us some extremely useful insight into what users of our software are experiencing, so thank you!
Look out for version 7, coming soon, which will provide a streamlined UI, making navigation of the player and server components as well as connection creation/configuration much simpler.December 1, 2020 at 10:40 in reply to: First blank screen, next ‘Connection reset by peer’ #30592
There was a link pointing to bitbucket.org which from what you wrote was a mistake, nevermind 😉December 1, 2020 at 10:03 in reply to: First blank screen, next ‘Connection reset by peer’ #30585
can you send the logs to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email. I’m not sure what link you wanted to include, if the linked webpage doesn’t contain the stored logs nor be related to the problem in discussion the keymaster will remove it. Thanks.
Hi, I would do a complete reinstall of the software on the remote computer you are connecting to. Did you install the latest version from our website. Could it be that you previously had a different edition installed? Also, you should not have to perform any action related to posix.dll in bin unless you are following specific operations related to installing on Latte Panda (in that case you should contact their forums). AFAIK NoMachine installs out-of-the-box on that device.November 27, 2020 at 09:16 in reply to: Support for arm64e architecture on macOS 11 (Big Sur) #30544
Once version 7 is released, which is in its final testing phase, the team we’ll be able to concentrate on a universal binary for macOS.
Just to clarify, the free version allows one connection to the remote desktop. Enterprise Desktop allows unlimited connections to the same physical desktop. If user A is logged in locally to the Windows host, you will be able to connect as user B with NoMachine but the person already logged in will need to authorize you.
I’m not sure what you mean by “some files in use by running processes”. An easier way to get the logs from the remote computer (the one you are trying to connect to) is by following the guidelines here: https://www.nomachine.com/DT10O00162.
What version of Windows are you connecting to?
This document might be useful to you which has some useful tips on how to debug: https://www.nomachine.com/DT10O00163
We aren’t aware of issues with taking an excessive amount of time to log out. We had one occurrence of a session taking 10 secs to log out but there were many applications open at the time. How many applications do you have open at the time of log out and what are they?
Drag and drop is not supported with Wayland desktops
It’s not clear to me what the problem was that you were encountering in the first place, but if you considered the “issue” resolved, that’s fine. I requested logs because I was under the impression that you were seeing a “waiting for desktop to authorise” message despite 1) logging in with the same username and 2) you had followed the advice of Mth in the topic you mentioned.
I mentioned “security risk” which is taken from Mth’s original answer to the topic that you were quoted at the start of this thread: having an unwanted user attach to your desktop without your permission is not what most people want. So the desktop owner has a choice to accept or refuse. Of course, if you trust the user with your username and password (you are the owner), then that’s entirely your choice and not under discussion here.
Maybe you should have a look at the Security section of the Server Guide document in our Knowledge Base.
If you continue to see behaviour which doesn’t match what you’ve set on each server, please open a new topic: https://www.nomachine.com/DT10O00155#2.2.
At NoMachine we want our users to be able to connect to and use any desktop environment they want, we don’t like to discourage 😉
Gnome and KDE are the most commonly used Linux desktop environments amongst our users. Then there are “lighter” choices which we also support, browsing the knowledge base is testament to that, and are becoming increasingly popular. See these for example:
Desktops environments supported by NoMachine
Setting a lightweight desktop environment on Ubuntu 11.04 or later (there is also an article for Fedora)
We prefer to let our users choose their own DE based on their own tests and general preferences. We publish benchmarks in or knowledge base (not for all DE, but the most common ones). For example,
Guidelines for sizing a NoMachine infrastructure and benchmark tests for v. 6
Performance all comes down to what you are using on the physical machine. For example, 3D graphical effects (e.g. shadows, animations, fading menu etc..) perform better on hosts with a capable GPU (Graphics Processing Unit) but are made available also on those machines without a GPU. In this case software rendering is done on CPU instead on GPU. This process is CPU-intensive and does require sufficient CPU power for a good experience. A lightweight desktop like Xfce or Mate is less resource intensive and will help to reduce the CPU load. You can find some examples for installing and running an alternative desktop here: https://www.nomachine.com/AR04K00667
It seems strange that all those NoMachine servers are presenting the same problem. As Mth wrote in the topic that you mentioned, the default behaviour (and provided the configuration files have been messed with):
1. When there is Login Window, you can connect with any user without prompt.
2. When there is a user desktop logged (User A), you can attach as the same user without prompt. (To UserA’s desktop)
If you enter different credentials in NoMachine player (UserB), you are not desktop owner, there could be a potential security risk involved, so UserA will see the prompt and consequently decide whether to authorise or not.
Since we are not able to reproduce the problem, I suggest you increase the debug level in the logs of one of the affected host machines (let’s say from one of the x.org hosts) and send them to us and we will take a look. For now you can continue to run the earlier version of NoMachine. Instructions are here:
Enable debug on the server machine and then do:
sudo /etc/NX/nxserver --restart
Then please gather logs either manually or by executing:
sudo /etc/NX/nxserver --debug --collect
Please send the logs to forum[at]nomachine[dot]com using the title of this forum’s thread as the mail’s subject.