Forum Replies Created
-
Posts
-
The most reasonable implementation would be to send a WOL packet just before the connection attempt, so that if the server is not running, it would restart its run, or send the WOL packet if the server is not immediately responding in a reasonable time, like a couple of seconds. The WOL packet, instead, is now sent after the connection timeout, if the remote host is not responding. The reason it was done like this was to overcome a few WOL problems and incompatibilities we encountered at the time of the first implementation. We actually retested all of this and it doesn’t seem that these problems and incompatibilities still hold. This means that a more reasonable implementation should come shortly, actually resolving the problem you detected. Thanks for reporting.
I’m assuming you’ve got the free edition installed on the Windows 11 PC. A NoMachine Free Edition installation will accept 1 connection. If you’ve started a connection to your Windows 11 PC and then start a second connection to the same PC, the first connection will close. Two NoMachine players connecting to the same Windows desktop requires Enterprise Desktop.
https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Desktop
Not quite sure what to make of what you wrote. With HW encoding/decoding enabled, then NoMachine uses the graphics card available on the host in order to encode or decode. If that’s not possible, NoMachine reverts to H.264 software encoding. This is explained in the material that I pointed to.
As for hypervisor technologies, NoMachine works out-of-the-box with most of them and we test with quite a few including Proxmox.
NoMachine can be used with VOIP applications in the following scenario https://forum.nomachine.com/topic/audio-from-user-to-user#post-41572
Hi, can you submit all attachments and images to forum[at]nomachine[dot]com? Also confirm distro and version on the server side and what OS you are connecting from. Desktop env will be useful as well.
I had in mind that NoMachine was able to adapt the remote resolution as the client window is resized.
It does 🙂 provided the following conditions are met:
When the connection is to the physical desktop (any OS) , the supported resolutions are those of the remote graphics card as listed in the System settings on the server. The session resolution on the client side cannot be higher than the maximum resolution supported by the remote graphics card (server side).
The supported resolution for virtual NoMachine desktop sessions (Terminal Server for Linux products) doesn’t depend on the remote hardware and thus the remote screen can be resized to whichever resolution is supported by the user’s local monitor.
I pasted this text from the article here:
Some tips about resize and scaling options for NoMachine remote desktop software
https://kb.nomachine.com/AR02M00835Hi, we can reproduce and will be opening a Trouble Report. Thanks for reporting 🙂
The workaround in the meantime is to connect over ssh or change TTY (ctrl+alt+F2) – and remove the mentioned line greeter-setup-script=/usr/NX/scripts/vgl/vglgenkey or restore the orginal key:
sudo cp /etc/lightdm/lightdm.conf.orig.vgl /etc/lightdm/lightdm.confWe’re still investigating. In the meantime, can you take a look at the following link and try the steps there? This will at least check that everything is functional (without NoMachine in the mix).
export LIBVA_DRIVER_NAME=iHD wget https://github.com/lu-zero/fate-samples/raw/master/h264-conformance/AUD_MW_E.264 # Decode H.264 video stream w/ maximum speed /usr/share/mfx/samples/sample_decode h264 -i AUD_MW_E.264 # Decode H.264 video stream and dump output YUV /usr/share/mfx/samples/sample_decode h264 -i AUD_MW_E.264 -o AUD_MW_E.yuv -i420 # You can verify the result comparing with the following checksum: # sha1sum AUD_MW_E.yuv e17a3f8cfeeeb1cc46218c3c797d24dd84e82b59 AUD_MW_E.yuv # 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.264and tell us the outcome.
Thanks for letting us know. SSH tunnels aside, if you have any other questions about player and the server, or other components of NoMachine software, let us know here 🙂
With regards to the sound issue, check what is indicated in your Windows sound settings. Are you able to change to another audio output? With regards to the no access on Jetson issue, are you not even able to SSH into it? Have you tried rebooting? Rebooting with a monitor attached or HDMI dongle (if you don’t have a monitor)?
Hi,
please tell us:
1) if pointer/cursor grabbing is enabled in the Player.
2) if you’re sending Ctrl+Alt+Del through the shortcuts menu and you’re reaching the Windows security screen (lock, change user, task manager etc)
3) are those two players connected to the same desktop, each one showing a different monitor?To restore the GUI you just removed, you can run
sudo systemctl set-default graphical.target.You should still be able to connect with NoMachine 🙂 When you say “not able to get a screen”, what do you mean exactly? Did you install NoMachine on Windows, NoMachine on your Jetson and then tried connecting with NoMachine using the Jetson’s IP address? Can you tell us what happens exactly?
What desktop environment is running in Ubuntu? We have an article here with some tips about how to set up your Jetson. Take a look: https://kb.nomachine.com/AR02R01074 and follow the tips there and let us know how you get on.
Try installing using our official tar.gz packages from our website. Manjaro is a distribution we don’t support, but we tested on the fly and can’t reproduce your issue even with Yay What package did you use? There seems to be quite a lot of NX derivatives (which we can’t handle in these forums). We used “1 aur/nomachine 8.11.3-1 (+90 0.40)”
Please also tell us the Desktop Environment. Is it GNOME? XFCE?
https://forum.manjaro.org/t/howto-resolve-an-unbootable-manjaro-black-screen-login-failed-cant-boot-etc/3957
Some tips are available at the above link.It seems the local system is crashing (not nxplayer). Can you send us the system logs (journalctl) and player logs? Please refer to the following document for instructions 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!
You could also try disabling hardware decoding in the meanwhile (setting it to “disabled”, as explained in https://kb.nomachine.com/AR07U01202), just to exclude a possible problem with drivers.