Britgirl

[Britgirl]

The next step is to understand if it’s a drivers problem or not. Can you try the package libmfx-tools and encode with its sample encoder? The procedure is here:

https://github.com/Intel-Media-SDK/MediaSDK/wiki/Intel-media-stack-on-Ubuntu

sudo apt-get install libmfx-tools

export LIBVA_DRIVER_NAME=iHD
wget https://github.com/lu-zero/fate-samples/raw/master/h264-conformance/AUD_MW_E.264

# Encode H.264 stream w/ Low Power encoder on gen9+ (skl+)
/usr/share/mfx/samples/sample_encode h264 \
-w 176 -h 144 -f 30 -cqp -qpi 30 -qpp 30 -qpb 30 -qsv-ff \
-i AUD_MW_E.yuv -o encoded_AUD_MW_E.264

[Britgirl]

Are you still able to send us the logs from player and server sides?

Seems that switching off the hardware decoding using NoMachine’s GUI does not work. For disabling hardware decoding one should edit player.cfg file

Do you mean that you tried disabling HW decoding in the connection menu and you still got the green screen? The menu enables/disables for the session, but does not stop the libraries from being loaded. You need to edit the file $HOME/.nx/config/player.cfg on the client side and set the configuration key “Enable hardware accelerated decoding” to “disabled” to stop the libraries from being loaded entirely.

The options are:
1) true: hw decoding enabled
2) false: hw decoding disabled (but libraries for hw decoding are loaded)
3) disabled: hw decoding disabled (libraries for hw decoding are never loaded and the checkbox is greyed out inside menu panel)

From the menu, you are able to toggle between options 1 and 2. So does setting the key to “disabled” in the player.cfg solve the issue?

[Britgirl]

Hi, is this computer you changed from nvidia to AMD the client or the server? Can you send us the complete set logs of the server-side computer you’re connecting to and logs of the client computer you’re connecting from? 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!

[Britgirl]

Hi,

there seems to be an issue with capture in the agent. A simple reboot could solve the issue. Did you already try that? If that didn’t help, you can also try changing the screen capture method in the ‘C:\Program Files\NoMachine\etc\node.cfg’ file.

DisplayServerExtraOptions "-nodxgigrab"

[Britgirl]

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

[Britgirl]

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.

[Britgirl]

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.

[Britgirl]

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/AR02N00875

Submit everything to forum[at]nomachine[dot]com.

[Britgirl]

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.so

Restart NoMachine and try again to see if NoMachine is using Intel’s mfx hardware encoding.

[Britgirl]

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.

[Britgirl]

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?

[Britgirl]

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 better IP="Paste_here_IP_address"; echo >/dev/tcp/$IP/4000 && echo "NoMachine is runned" || echo "NoMachine is stopped"

For scheduling how about crontab?

[Britgirl]

Wayland is supported, with some limitations, and you can read more about this here
https://kb.nomachine.com/AR02P00969

Can 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.

[Britgirl]

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?

[Britgirl]

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.

 

[Author]

Posts