Forum Replies Created
-
Posts
-
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?
Hi,
scripts in server.cfg need to be executed as ‘user nx’ by nxserver. Scripts in node.cfg are executed as the user who starts the session of the nxnode process.
It could be that you don’t have permissions to execute, use this for example:
sudo chmod 555 /usr/NX/scripts/custom/runApplicationEnd.shCan you tell us what you want to achieve with the script? Maybe send us the script as well, along with your server.cfg and node.cfg files. Send them to forum[at]nomachine[dot]com.
Hi anip,
yes, we’ve already opened a Trouble Report for the issue, https://kb.nomachine.com/TR04V11131, so you can use that to track the fix, which is planned for the next update, NoMachine 8.12.
We can confirm that manually removing /etc/udev/rules.d/99-virtualgl-dri.rules file and rebooting fixes the problem you’ve reported 🙂
Earlier you wrote that you are also not able to login using Windows own remote desktop program. It’s either something misconfigured (possibly to do with the MFA app), the username and/or password is incorrect, or the fact that it’s a corporate PC, is it possible that remote desktop was even disabled?
NoMachine accepts multiple username formats, explained in the article just below.
Username formats supported to log-in to NoMachine by password authentication
https://kb.nomachine.com/AR03S01118Is it possible for you to make a test which for the test’s purposes requires a person on the other end? I realise that your intention is to get unattended access, but at least this way we can see that a NoMachine connection is actually possible. On your mother’s PC (the server side), check that GuestDesktopSharing is enabled. In the free version it’s enabled by default, but you can check it by going into the NoMachine server settings, in the Security panel: !M icon in the system tray > Server status > Security > Allow guest desktop sharing on this server. Then start your connection (see also the illustrated tutorial https://www.nomachine.com/getting-started-with-guest-desktop-sharing, there are steps for the desktop owner and steps for the guest).
Another thing we can do is look at the player logs and the server-side logs to check the error in more detail. Again, on your mother’s computer, open the Security panel, scroll all the way down and select debug level in ‘Server logs’. Restart the NoMachine server in Status. Then on your computer, the local side, open the Settings and go to Player > Security, tick the box ‘Don’t delete log files on exit ‘. Reproduce the problem. For the Player logs on Windows the .nx folder is hidden. To find it, write the following in the address bar or the file browser:
%USERPROFILE%\.nx or navigate through the computer folder till the user’s home and digit .nx in the navigation toolbar to reach it. Path can be similar to: C:/Users/nomachine/.nx. Zip it.</p>
For the server logs, find the VAR folder. It’s stored in %PROGRAMDATA%/NoMachine/var/log/. Zip that as well. Send everything to forum[at]nomachine[dot]com.To access any desktop via NoMachine you need a system account on that computer. On Windows 11 you need to input the same credentials you would normally use when accessing your onelive account on the MS website. Or you can use the local username assigned to your account. The password is the same for both. To check the local username, just go into the C: drive of the computer you want to access, select Users and check what your local username is. Are you sure you are using the right password? Don’t use the PIN that Windows 11 asks you when unlocking the screen.
Can you show us the error that you are receiving with NoMachine? What Windows version is it on the side you are connect to?