Forum Replies Created
-
Posts
-
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.
Just to confirm that we got them, thank you, and we are now able to continue with the investigation.
Codec string: H.264 NVENC/DXVA, audio Vorbis 22kHZ stereoThis shows that NoMachine is actually using hardware decoding. Can you describe the problem you are encountering?
NoMachine Terminal Server is targeting organizations with a need for unlimited sessions and/or have a large number of users. Also consider the support that comes with a subscription as well.
For individuals/professionals or very small units, NoMachine Workstation might be a better option 😉
Thanks for letting us know anyway, I’m glad a clean reinstall fixed the problem. If it happens again, let us know.
If this is a headless Linux machine, please take a look at his article, point 3 in particular:
Connecting to Linux headless machines with NoMachine
https://knowledgebase.nomachine.com/AR03P00973A specific case which leads to black screen on Linux is when the X server is running but it is not rendering. In this case NoMachine doesn’t use its own virtual display because it detects that the X server running, so you need to turn back on NoMachine’s virtual display. I say “turn back on” because before the system crashed (we can’t be sure if it was the actual connection that crashed), NoMachine was running fine.
I’m glad you got the demo up and running. Which product did you choose in the end? 🙂
Out of interest, you wrote “product feature chart shows even the basic versions supporting Web access”. Can you tell me which chart you were looking at? I will make sure it’s corrected.
The comparison of NoMachine Free Edition and Enterprise Desktop is available here: https://www.nomachine.com/remote-access-for-everyone