Forum Replies Created
-
Posts
-
Hi, NoMachine is compatible with Windows 11. Out of interest, did you also try connecting from a different client-side computer to this Windows 11 host?
We aren’t aware of similar problems with this version, so the best thing is for us to check the logs of the affected Windows 11 host. Can you follow the instructions here and then send the logs you extract via email to forum[at]nomachine[dot]com? Just put the topic title in the subject of your email. Thanks!
Can you provide some more details about your environment? For example, do the 10 RPIs have different IP addresses?
Hi, the attachments didn’t attach correctly. Could you send them direct so I can attach them separately? 🙂 Just send them to forum[at]nomachine[dot]com and use the topic title as the subject. Thanks!
Thanks for bringing this to our attention. We’ve now updated the article with the additional information and feedback you provided, so thanks again for pointing this out. As soon as we’ve added support for VA-API, we’ll update the article again to make this clear.
Can you send us the $HOME/.nx directory from the server side? They are missing from the logs that you sent.
In order to understand the complete context can you tell us exactly how you are using NoMachine? You mention context-switching, can you give some more details?
Btw, with a subscription you are entitled to open a support ticket from your customer area, and as a Premium you have a response time of four business hours. You can submit tickets by logging on here: https://www.nomachine.com/support and scrolling down to Customer Center 🙂
Eugene, the logs were incomplete. We need them from the computer which you are connecting to, the server side and the debug logs from the client-side computer you are connecting from. Please follow the instructions from this document on the computer you are connecting to (the server side):
First Step: Enable Debug Level on the Problematic Host
https://knowledgebase.nomachine.com/DT11R00182#1I will paste it here:
To enable debug on Windows, open a CMD console as administrator and move to the ‘bin’ folder under the NoMachine installation, e.g:
cd %ProgramFiles(x86)%\NoMachine\bin
nxserver --debug --enable allSecond Step: Connect and Reproduce the Problem
Be sure that the Don’t delete log files on exit checkbox is selected in the client user’s interface in the Settings -> Security panel of your client-side computer.
Third Step: Create the Log Archive
cd %ProgramFiles(x86)%\NoMachine\bin nxserver --debug --collectThe log archive is named as: NoMachine-log-.zip (e.g. NoMachine-log-2018.09.27-11.44.01.zip) and stored in: %PROGRAMDATA%/NoMachine/var/log/archives on Windows 10, 8.x, 7 and Vista or in Documents and Settings/All Users/NoMachine/var/log/archives Windows XP.
Send both sets of logs as attachments to forum[at]nomachine[dot]com. Thanks!
Hi, can you send us any images that you tried pasting into the body of your topic? I will upload them separately as attachments. Thanks!
We aren’t able to reproduce this on our systems with your same set-up. Can you send us the full backtrace of the crash?
Instructions are here:
Using GDB to debug a core file on Linux
https://knowledgebase.nomachine.com/AR09L00810Send it to forum[at]nomachine[dot]com. In the subject of your email please use the topic’s title. Thanks!
@mikecico, try Workstation from the Terminal Server for Linux range. It’s available in evaluation.
https://www.nomachine.com/product&p=NoMachine%20Workstationhttps://forums.nomachine.com/topic/anyone-gotten-quicksync-encoding-working-on-a-recent-ubuntu#post-32641 . I can only conclude that information is out-of-date.
Can I ask which information you think is out-of-date?
Hi cro, we promise it’s coming. Version 8 for desktop is in its final stages, although we admit it’s taking longer than we expected. As soon as we have released that, we will focus on getting the mobile version out.
Please see my answer to a similar question here: https://forums.nomachine.com/topic/still-not-working-well-on-dex#post-36083.
It is possible to force the termination of a virtual desktop session, it’s also possible to show an extra dialog to the user when they click X to close the window.
# Set for how long the server has to keep alive virtual desktops in
# status disconnected. When the time is expired, the server will
# terminate virtual desktops if no user are connected there.
#
# 0: Virtual desktops in status disconnected are never terminated.
# This is the default.
#
# >0: Keep alive virtual desktops in status disconnected for this
# amount of seconds.
#
#DisconnectedSessionExpiry = “0”To activate the dialog I mentioned please see, for example, the chapter on Activating the Disconnect/Terminate Dialog in the configuration guide for the product you are using. E.g, in Workstation it is in Chapter 11, section 4.