Forum Replies Created
-
Posts
-
Take a look at the answer from Mth in an earlier topic
Unable to make the local display available or access to the local display is disabled
Hi, it’s not currently possible but we will be adding support for USB auto-sharing, so all you will need to do is plugin the device, before or during the NoMachine session, it won’t matter. Watch out for this in one of the successive v9 updates.
We investigated with the specific logitech keyboard and opened the Trouble Report here https://kb.nomachine.com/TR02V11091. It will be in the next maintenance release.
It’s hard to say why that is happening, it’s possible network related? Our tests show that over the Internet there are no pops in audio or microfreezes. When it happens again, please submit:
logs from the server side (the machine you are connecting to) – see this document https://kb.nomachine.com/DT07S00243
logs from the player side (the machine you are connecting from) – see the same document as above
Session statistics – check the instructions in this article on how to get session statistics https://kb.nomachine.com/AR02N00875Submit everything to forum[at]nomachine[dot]com.
Please check in /usr/lib/x86_64-linux-gnu if you have the library libmfxhw64.so – if not please create symbolic link to libmfxhw64.so.1 from a shell with:
cd /usr/lib/x86_64-linux-gnu/ sudo ln -s cd libmfxhw64.so.1 libmfxhw64.soRestart NoMachine and try again to see if NoMachine is using Intel’s mfx hardware encoding.
I will find out the reason why it is forced to restart (or it will hang and cannot be accessed).
This would be of interest to us since nxserver should not be hanging or suddenly becoming inaccessible. To investigate we will to know what you’ve installed it on and the server-side logs (see this document for instructions, https://kb.nomachine.com/DT07S00243.
Glad to know you authenticated in the end. Btw, you can always use the word ‘localhost’ in the Host field of the connection details instead of the IP if you prefer. When you say “invitation method”, what do you mean exactly?
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 (provided you’ve not changed the onelive login after setting up Windows). Or you can use the local username assigned to your account. 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.com/TR02V11091.
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.