Forum Replies Created
-
Posts
-
So it would seem a separate issue (when you are connected to the remote host and not when opening the UI), but logs will help us to understand what’s happening. Can you send the logs from the Enterprise Client host, this time following the instructions here: https://knowledgebase.nomachine.com/DT11R00181#2?
Hi, can you send us the logs of the M- directories from the affected hosts (typically you can find them in /var/NX/nx/.nx/M-* ) ?
Attach them here or send direct to forum[at]nomachine[dot]com.
Hi LorenDB, we would like to send you a link for a new package to install, and you tell us if the fix helps. Please check your inbox for direct emails from us.
We’re still not able to reproduce the problem described in this topic. We will open an internal TR so that we can track the problems that were reported. It would be interesting to know if you encounter the same behaviour with the latest 7.8.2, just for the record.
You must insert an administrator user and password to allow the update to proceed. Just like when you installed the NoMachine software, which asks for admin user and password in order to proceed with the installation, it’s the same with updating. For information about updating the software, you can check the installation guide for the product you are using (Go to nomachine.com/all-documents).
This article might also be of help to you.
How do I update NoMachine software?
https://knowledgebase.nomachine.com/AR10K00698If this doesn’t help, please tell us what you would like to know and we can check how to improve our documentation accordingly 🙂
Hi, as far as we are aware, Devolutions Remote Desktop Manager supports NoMachine sessions, including the latest version. We checked just to make sure.
Confirm what you are using with regards to NoMachine software (both client and server) and the RDM product version as well.
Additionally, please tell us the steps you are following in order to the produce the error you receive.If you are using an old version of NoMachine software, I advise you to update to the latest version. We can only provide help here for currently supported versions.
Hi, thanks for the detailed information you submitted. We have a Trouble Report currently open which you can find here:
High CPU usage of NoMachine Client on Ubuntu when listing the available machines and connections
https://knowledgebase.nomachine.com/TR09S10371We’ve still to start work on a solution, and it’s likely that the fix will be something trivial. For the moment, could you try the workaround in the TR? That is, disable the mDNS search (network browsing): open the client UI -> Settings -> Player -> Security and select ‘Don’t show other computers on the network’.
We’ve checked Rocky 8 and that the command is correct. Everything works fine for us and connect successfully. Did something change on the system such as an update or a new setting?
Please submit the image that was missing. You can attach to another reply in this thread. Also a full set of logs from the server side would be useful. Please check here how to gather them: https://knowledgebase.nomachine.com/DT11R00182
Thanks for your contribution. I will link an article here for other users from our knowledge base which explains what usernames are accepted depending on the operating system you are connecting to.
Username formats supported to log-in to NoMachine by password authentication
https://knowledgebase.nomachine.com/AR03S01118As yet the next MR of v7 hasn’t been scheduled. In any cases the fix in question has also been added to the next major, version 8, which is in its final testing phase, so it’s probable that you’ll get the fix in that rather than wait for the next maintenance of version 7 🙂
Please check this topic here: https://forums.nomachine.com/topic/message-cannot-find-the-default-environment-please-contact-your-system-administrator-on-latest-slackware#post-36529
The workaround that Kroy wrote was for Slackware 14.2 but we checked it for version 15 and it works fine.
You’re right lo_pan. Although a fix was indeed done and queued up for insertion, it didn’t make the last maintenance. It will definitely be in the next v7 maintenance.