Forum Replies Created
-
Posts
-
We’ve not been able to reproduce this behaviour. Are you sure there are no other factors influencing the missing screen lock? Is it affecting just your computer or other Win11 computers?
You can use the same keypair, one public key is placed on the ECS host. If you do that, you will need to run
--serveraddon each node, and then accept the fingerprint of the ECS when prompted. If you need further assistance setting up your ECS and node infrastructure, please contact us directly and one of our technicians will assist you.Hi Brian, just a quick update, the logs you submitted were useful but we need to debug deeper. We are preparing a new debug package and will send it soon.
Can you first tell us what NoMachine product and version you are using on the server and client sides?
Are those shortcuts, which are not working to how you expect, being intercepted on the Windows client?
Something you could check is whether the misbehaving keys are being received by the server when they’re pressed on the client. You can do with an onscreen keyboard or with xev. Can you show us the output?Hi, can you enable grab the keyboard in the connection menu (connect first, open the menu with ctrl-alt-0), proceed to Input)?
More details here: https://kb.nomachine.com/DT06S00218#3
Keyboard
Grab the keyboard input – Ticking the box disables the capturing of some system key combinations allows you to use those shortcuts in the remote desktop.Please show us the list of processes showing such high CPU usage. Also, logs from the ECS server host, also knowing what OS version it is would be useful as well.
Hi, I removed your public IP from the log excerpt for privacy reasons. Is there a specific reason for using version 8.9 to connect? Have you considered updating it? This would narrow down the issue so that we aren’t investigating older versions to find out that the problem was being caused by something already fixed.
That said, we would need the server-side logs so we can check them. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. It’s important to enable debug, reproduce the error, then zip up the logs.
Also the player logs would be useful as well. (instructions are in the same document)
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi,would you able to send us the server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. It’s important to enable debug, reproduce the error, then zip up the logs.
Also the player logs would be useful as well. (instructions are in the same document)
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Apologies, I didn’t point out that this is a global setting, and requires you to exit the Player first (Quit the player from the system tray !M icon), make the requested change and save, then re-open the Player. Can you try again?
We’re investigating it our side as well in the meantime.
Hi, no there isn’t. This is to keep the number of shortcuts to the minimum to avoid clashing with system shortcuts.
The shortcut options available (and which you can edit if you prefer) can be found in the Player settings > Input > Shortcuts.Hi, this is a valid request for connections to the physical desktop and should be relatively easy to do, so we’ll open a feature request. Are you also handling users connecting with guest desktop sharing? Because if that’s the case, the name of the desktop owner cannot be shown for privacy reasons and so this FR will not apply to that type of user.
Is the session in fullscreen when you encounter this? When the session runs in fullscreen mode, NoMachine disables the display sleep timer in order to offer users a more comfortable experience (such as when streaming media). There’s a key that should regulate this. In .nx/config/player.cfg, can you edit the key “Turn off energy saving while in fullscreen mode” to false? Does this help?