Forum Replies Created
-
Posts
-
We’ve just installed Unity desktop using your same Ubuntu version without problems. What desktop environment are you using? And what version?
You mention tutorial, did you follow our tutorial on this page: https://www.nomachine.com/accessing-your-remote-linux-desktop-on-amazon-elastic-compute-cloud-via-NoMachine ?
Did you install NoMachine earlier and then uninstall before trying to reinstall again? Perhaps with a different NoMachine product? This could have caused problems with the license file for example. The best thing to do is uninstall again, remove the directory /usr/NX completely.
sudo rpm -e nomachine && sudo rm -rf /usr/NX /etc/NX
Then reinstall.
This depends on your system configuration. In 99,99% of cases you need root credentials (or be a part of sudo group) to install anything on the your Linux server.
Hi, checking the logs you sent it, they are from the client-side. We need them from the server side (the machine you are connecting to during the session).
Hi, can you give us more information, such as i) Linux distribution and version on the machine you are connecting to; 2) desktop environment; 3) version and specific product of NoMachine on the remote host; 4) version of NoMachine on connecting client and 5) OS of the client?
We can reproduce the problem, so we’ve opened a Trouble Report https://www.nomachine.com/TR01O07489. Please use the notify me facility to know when a fix has been released.
We aren’t able to reproduce it, so need to ask you for logs from both sides, client and server. Follow the instructions here, making sure you reproduce the error once you’ve enabled debug on the server side. Send them as attachments to forum [at] nomachine [dot] com.
Yes, the proper path is not being received (but this is just the tip of the iceberg) We’ll update the topic once we’ve got some more info.
Can you update the player version and see whether you have the same issue? I ask because whereas we are aware of issues with files sometimes being corrupt during transfer, we aren’t able to reproduce your exact same problem..
Hi, no quite the opposite 🙂
The patch that we prepared didn’t make the release we have scheduled end of this month or February. We’re happy to send you a patched 5.1.62 for you to try like we suggested last month. Let us know.
NM 5 Enterprise Server allows only 1 concurrent connection to Windows server, since NM provides access to *physical* desktop ?
It supports unlimited connections to the same physical desktop. Enterprise Desktop for Windows also has the same functionality. Enterprise Server offers node support, HA and other functionality which you can compare here: https://www.nomachine.com/feature_comparison
AFAIK, Windows Server allows several concurrent connections (RDP) , natively, on the server. Is this not available in NM 5 Enterprise Server
Enterprise Server supports RDP as you will see in the features table I just linked. It would make sense to have Enterprise Server for Linux or even Terminal Server, which via RDP, will connect you to your Windows nodes. If you want to set up RDP, please see here:
Using NoMachine Server for Linux to access Windows Terminal Server from the client machine
https://www.nomachine.com/AR02D00349 and https://www.nomachine.com/AR07J00645.Does it make any sense to create a NM5 cluster, with only Windows server ? If yes, then this will only allows as many concurrent connections as declared servers in the cluster ( e.g. a cluster with 4 Windows NM5 “nodes” will allows only 4 concurrent connections on cluster ).
If it’s acceptable to you that one Windows node is one desktop, the ES for Windows can be used as the entry point to broker connections to the nodes (each node being one Windows desktop). If you need assistance with pricing and setting up the server, please contact our sales team using the Contact Us link in the footer of the website.
After many attempts, we’ve finally been able to reproduce it. It would appear to be more of a problem with KDE 5, not NoMachine. Whilst we investigate further, it might be better to use an alternative desktop environment until we’ve identified a workaround. When we have some more info we’ll post it here.