Forum Replies Created
-
Posts
-
@bigtractor, I am not quite sure why you are concerned that we updated our KB article concerning the OS version that you are using. We try to keep our KB up-to-date as much as possible, and that sometimes means that when users report issues on the forums, we take time out to check whether specific OS versions are working as they’re supposed to. We also make regular checks on syntax and so forth, so an update will result even for the removal of a comma.
The team actually added this part to the article specifically for your case which you took the time to report to us on the forums:
“2) We verified that on Ubuntu 16.04, besides following the above instructions, it’s also necessary to run the container in privileged mode as explained here: https://docs.docker.com/engine/reference/run/”
The developer who replied to you may likely have been preparing his next reply to also inform you that some changes have been made to the article, but I beat him to it 🙂 I will leave it up to Cato to answer your question about privileged mode.
Carbuff, the current server software is 5.1.54, which also includes the recent OpenSSL Project’s vulnerability fix as well as a number of fixes to do with copy&paste, so what you should do is update your server software (ask your Admin). Then if you continue to have problems, we can investigate on the latest version.
See our reply here https://www.nomachine.com/forums/topic/nomachine-network-anywhere-status
You’ve already been added to our list of those interested in testing 😉
Take a look at the article here https://www.nomachine.com/AR07K00681, paragraph iv) Listing all the desktop types available on the server.
Also this:
How to run a virtual desktop environment on Linux different from the default one with NoMachine
https://www.nomachine.com/AR04K00667A similar question was posted in this topic which answers your question:
https://www.nomachine.com/forums/topic/selecting-different-desktop-environment-nomachine-5
Logs didn’t attach, probably because they were too big. Send them to forum[at]nomachine[dot]com.
Just to clarify, are you connecting from this Red Hat client? When you say it doesn’t respond, do you mean the GUI opens when you start the connection, but doesn’t continue? Can you submit a screenshot of what you see when it ‘hangs’.
Or do you mean that when you try to connect, the connection just hangs? What is using 100 CPU? The connecting client or the remote host to which you are connecting?
SSH is geared towards the Enterprise users. The free version doesn’t support SSH and there are good reasons why SSH is not in the free version.
People expect software to install and work out of the box, while SSH requires that you install and configure SSH beforehand. This is not what the average user expects. Second, SSH can be tricky to configure, so why give users of the free version these problems before they’ve even started? Third, the NX protocol can use both TCP and UDP for multimedia traffic and this can make a huge performance difference.
Clearly NoMachine wants people to get the best from the software. If you are in a setting where SSH is a requirement (but you don’t want to install one of the Enterprise pay-for products), or you’re tech-savvy, then you can still tunnel the NX connection over SSH, as you would do for any other protocol.
If you are interested in knowing more about the differences, I suggest you check this article: https://www.nomachine.com/AR11K00739
We’ve not been able to reproduce this issue at all. If it’s possible, can you send us the logs from the server? You’ll need to enable logs first, then reproduce. See the instructions here and send them to forum[at]nomachine[dot]com. Thanks.
We don’t need to send you a debug package. It will be enough for you to enable debug and then submit the logs: https://www.nomachine.com/DT07M00098.
Please follow the instructions and then send the logs to forum[at]nomachine[dot]com.
We’ve not been able to reproduce this problem so we are sending you a debug package to investigate further. Check your inbox for emails from our keymaster.
Hello everyone, the patch for this bug has been released today. Update now. More details about 5.1.54 are here: https://www.nomachine.com/SU09N00176.
We’ve reproduced the issue and opened a Trouble Report. You can sign up to receive notification of a fix when it’s available. Thanks for reporting.