Forum Replies Created
-
Posts
-
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.</div>
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?
We’re analyzing the information you provided to us, so thank you, and now it’s a question of replicating the environment and reproducing the exact same errors. We’ll update the topic as soon as we can.
Yes it did, but my fault for not noticing that the document I indicated was not up-to-date. All v8 documents are aligned now.
Those commands are for running virtual desktop sessions which are available in all Terminal Server products. What you need to do is
By default, on Linux:
/usr/NX/bin/nxplayer --session <path to .nxs file>For more details check out this article https://kb.nomachine.com/AR04O00923. You may also be interested in this document which highlights what you can configure in your connection file: https://kb.nomachine.com/DT07S00240
The output didn’t proffer any useful hints unfortunately.
Completely disable hardware decoding on the client if you already didn’t do so by following the instructions here:
https://kb.nomachine.com/AR07U01202Attach gdb so we can get the dump of threads of the client not updating the screen:
$ sudo gdb -p <pid of the client process>
$ set height 0
$ set logging file /tmp/backtrace.txt
$ set logging on
$ threads apply all bt full
$ quitAlso, when the connection freezes, is the client still responsive? ie. Can you open the menu and interact with it? While the window appears to be frozen, is the CPU usage of the client process normal?
Decoding is disabled in the Player.cfg on the client side, the device that you are connecting from. There is an article you can check for the steps to follow:
How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202Apologies, the correct key is
EnableClientCredentialsStoring none. I realised my mistake when checking the server.cfg file. The key is present in your version. Just set it to none.