Forum Replies Created
-
Posts
-
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.
this button does not exist under “keyboard and mouse” for me.The Feature Request link that I sent is a feature that has not been implemented yet.
” I’ve evaluated the Enterprise Desktop version and it doesn’t allow multiple virtual monitors, which is a bit odd”
Enterprise Desktop indeed does not permit multiple virtual Linux desktops on the same machine. This is a feature of the Terminal Server family, so Workstation is the product for you, as you rightly identified and as Francesco already suggested 😉
It seems there is a problem with nxlsa.
Did you reboot the computer after installing NoMachine?
If you did, what is the NoMachine version? What is the Windows version?
Do you have an antivirus installed or is there LSA protected mode enabled?
Hi, I am going to send you a file in a separate email. It contains the workaround whilst you wait for the permanent fix. Download it on to your machine and then run:
sudo semodule -i nx-unconfined.ppThanks for letting us know. We have not been able to reproduce this problem – is it possible that you used the public key instead of private key when prompted?
Thanks for letting us know.
When you have time, you could collect the logs manually. See here for more info:
https://knowledgebase.nomachine.com/DT11R00181#1.3Any questions, we’re here 🙂