Forum Replies Created
-
Posts
-
Hi,
can you try disabling HW decoding on client 01? Check the article here to know how to do this:
i) How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202ii) Then, if that doesn’t help, the logs from client01 would be useful. See the section of this document:
2. Fourth Step: Collect Client Side Logs
https://kb.nomachine.com/DT07S00243iii) Gather logs from server01 after reproducing the “Connecting to …” problem. For logs of the server, see the same document.
Submit everything to forum[at]nomachine[dot]com.
Take a look at the article which contains a number of things to check why this could be happening:
How to solve ‘session negotiation failed, application terminated prematurely’
https://kb.nomachine.com/AR08N00898Please enable the logs:
sudo /etc/NX/nxserver --debug --enablereproduce
sudo /etc/NX/nxserver --debug --collectAlso attach the node.cfg, system logs and .xsession-errors file.
Send everything to forum[at]nomachine[dot]com making sure to reference the topic. Thanks!
Hi, regarding the menu bar issue, we are working on improving the user experience when using NoMachine in fullscreen on macOS, and these improvements are planned for version 9.
WalkerJ, about the cursor issue, can you do the following when the problem occurs? Enable “Show remote cursor pointer” in the Input menu, and check whether the remote cursor moves or not.
Hi,
Take a look at the article which contains a number of things to check why this could be happening:
How to solve ‘session negotiation failed, application terminated prematurely’
https://kb.nomachine.com/AR08N00898I noticed that you have a Workstation Subscription. You have a direct channel to our support team if you login with your CustID and password in the support section of the website. Logs will be required in order to understand what’s happening.
On the affected machine, enable debug:
sudo /etc/NX/nxserver --debug --enablereproduce the problem
sudo /etc/NX/nxserver --debug --collectPlease also attach the node.cfg and system logs. All of this can be sent by email to forum[at]nomachine[dot]com. If you prefer to open a ticket, you will get instructions on where to send it.
Logs show you didn’t reboot as recommended. Please reboot the operating system. If the problem continues, resubmit fresh logs.
I don’t know why but I’m not able to start a virtual desktop.
After about 2 seconds I always get (message/image missing)Can you show us or paste the error? This is a different issue.
This allows us to terminate sessions that have been disconnected for a period of time.
You can do this with the key DisplayServerExtraOptions “-timeout s” in the node.cfg. (s = seconds)
I don’t know what product you are using but check the following resources:
Section 12 of the Workstation Install and Configuration Guide https://kb.nomachine.com/DT07T00262 (you will find the timeout key explained in all of the Terminal Server guides).
Check also here:
How to terminate NoMachine virtual desktops sessions automatically
https://kb.nomachine.com/AR08M00854Hi, Did you do a reboot after removing the leftover file as in the TR (https://kb.nomachine.com/TR04V11131). I’m assuming you did but I have to make sure.
If you did, can you try this instead as user root?
Make a copy of the following files
/usr/NX/scripts/vgl/vglserver_config /usr/NX/scripts/vgl/vglgenkeymaking sure to place them in the same folder
Uninstall
Execute
<path_to_folder_with_copied_files>/vglserver_config -unconfigReboot
The history command shows the following statuses – connected, disconnected, finished, failed. The time that appears next to the status is when that session was started. Please define “idle time”. You can easily write a script to get the time running for disconnected sessions.
We’re still trying to reproduce it.
Can you give us the output of
export LIBVA_DRIVER_NAME=iHD ; for DEVICE in /dev/dri/* ; do echo -e "Device: $DEVICE" && vainfo --display drm --device $DEVICE ; donein the meantime?We would need to see logs to understand the reason for this. Please run the following command from CMD (open as administrator)
%ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --enable allReproduce the problem, then run:
%ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --collectThe log archive is created in
%PROGRAMDATA%/NoMachine/var/log/archivesSend it via email to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject. Thanks!
Hi!
Remember that screen-blanking is a privacy feature, and an important one that does its job well. It’s there to stop users in the vicinity of the computer seeing sensitive information that the remote user (presumably the session owner) doesn’t want to show. We’ve had similar requests in the past for what to do (same explanation as yours more or less) and apart from pulling the plug… it would mean changing its current design. Changing how it currently works would need careful thought since we wouldn’t want to undermine its security function.
For Linux servers, an option could be to use NoMachine Workstation from the Terminal Server range; you don’t have to use the screen blanking option at all because you could run a virtual Linux desktop and nothing about your remote session would be visible. I’m not sure whether this fits your use case but you could consider it maybe?