Forum Replies Created
-
Posts
-
I’m not sure why the nxserver would need to be restarted. This would need further investigation. Have you set it to not restart when the machine reboots?
nc won’t restart the nxserver. To check if nxserver’s listening on the port, try with
nc -zv <ip_address_here> 4000. Or betterIP="Paste_here_IP_address"; echo >/dev/tcp/$IP/4000 && echo "NoMachine is runned" || echo "NoMachine is stopped"For scheduling how about crontab?
Wayland is supported, with some limitations, and you can read more about this here
https://kb.nomachine.com/AR02P00969Can you tell us what distribution is on the server side? Current known issues can be found in the knowledge base: https://kb.nomachine.com/trouble-reports?s=wayland&search=wayland&last_update=%25&affecting=%25&products_trouble=%25&status_tr=Open. If you submit the logs of the problematic server, we can check to see if it’s one of those. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243.
Can you try enabling the keyboard grabbing. Go to Settings > Player > Input > Grab the keyboard input.
More illustrated details are available here: https://kb.nomachine.com/DT11R00177#2.1.
What OS version are you connecting to?
Hi Belez, although it’s unusual to connect to localhost, it is possible. Using NoMachine to connect to the local desktop of the very same machine where there is the nxserver running (localhost), rather than using it to connect to a desktop on some other computer, will cause an infinite nested windows effect and a dialog will inform you of that once you get through the authentication stage. So bear that in mind.
So, I understand that you want to record the desktop, but the “Recording bar” from the !M icon in your OS system tray doesn’t give you access to the same Recording settings (letting you set quality of audio and video for example) as the recording tool available to you during a remote desktop connection via the menu (Ctrl-Alt-tab). This is correct. When activating the recording bar directly from the !M icon, it doesn’t let you set quality using a GUI. BUT you’re request is an interesting one and so we’re going to open a Feature Request which will make it possible.
Now the authentication problem. To access any desktop via NoMachine you need a system account on that computer. It’s exactly the same as it was before, nothing has changed 🙂 It’s just Microsoft keeps changing what you use to login with. 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 your C: drive, 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.
Please submit logs from both sides (player side and server side) and also the nomachine configuration files (both sides, player.cfg and server.cfg). You can send everything to forum[at]nomachine[dot]com.
For the Player side logs, be sure that the client has been launched with the ‘Don’t delete log files on exit’ option enabled in Settings -> Player -> Security. On the server,
nxserver --debug --enable allfrom a terminal enables the debug logs. Start your session, reproduce the problem and then extract the logs. Instructions are available here: https://kb.nomachine.com/DT11R00182Hi, there is a bug which is preventing disabling of copy and paste.
https://www.nomachine.com/TR03U10799
It might be possible to try a patched package before it’s released in an upcoming maintenance. Please contact us via the website (Contact us link in the footer of the website) to make a request.
Please use the following Trouble Report to track this issue https://www.nomachine.comTR02V11091.
About the workaround that was already provided, it’s from the Trouble Report here: https://www.nomachine.com/TR09U11006 which we originally opened on Gentoo and it’s the same for Arch-based distributions such as Cachy OS. The problem is that to make sound work on arch/gentoo distros, it means that NoMachine should change the configuration files of the already built-in pulseaudio/pipewire server during installation (/usr/share/pipewire/pipewire-pulse.conf). This is not a solution. Changing the system’s configuration can only be made by the administrator/owner, so for this reason the creation of a symlink is the best workaround.
Thanks for submitting the logs. Player logs are showing HW decoding is not being used. Did you also disable also hardware decoding (on Linux) besides disabling hardware encoding on Windows?
Also useful for the investigation:
1) Run this command on the client machine and send us the file (‘xdpyinfo.out’).:
xdpyinfo -ext all > xdpyinfo.out
2) Does closing the player and reconnecting help?3) Does the problem appear after the screensaver starts up?
4) You say you reinstalled the server and it solved the crash which is good news. We would appreciate a new set of logs, including both server and client logs, just after having reproduced the issue. This will allow us to compare with the earlier ones you sent.
5) Is the monitor of the server attached and turned on all the time when the issue is reproduced? Or if it’s a laptop, is the lid open?
Hi, can you try disabling HW encoding on the Windows and see the freezing still occurs? On the Windows machine, open NoMachine settings > Server > Performance > Untick the box ‘Use hardware encoding’.
If it does, player logs from the Linux client this time would be useful. Please refer to the same document I pointed you to last time.
Hi, we aren’t aware of similar issues on Windows 11. Are you able to send us the server-side logs from the Windows machine, so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
OneVPL is now the replacement to MediaSDK.
Indeed. In fact support for OneVPL will be added in the next update (coming soon).