Forum Replies Created
-
Posts
-
It seems that Nvidia has broken something in their latest driver update. While we investigate some more, a temporary solution is to set the key EnableHardwareEncoding to 0 in node.cfg (and use VP8), or downgrade your driver if possible. You can also try with H.264 software encoding for the time being, more about this is here: https://www.nomachine.com/AR10K00706.
As soon as we have some more information we’ll post it here.
Just so everyone can track the official patch when it gets released, here is the Trouble Report: https://www.nomachine.com/TR06N06907.
Confirm the version you are using on the server side, and also on the client side. We recommend that you update to the latest in any case. We’ve tried with a number of OS combinations on the latest 5.1.26 and can’t reproduce. What OS and OS versions are you connecting from and to?
By design, permissions for transferred files in NoMachine sessions are inherited from the OS to which they are downloaded
We have reproduced this problem and have opened a Trouble Report which you can see here: https://www.nomachine.com/TR05N06898
Please sign up to receive notification of its fix.
Provided that the server is indeed set up correctly (so in this case it’s Windows with a supported Nvenc-enabled driver installed) NoMachine’s use of HW acceleration for encoding works out of the box.
So we should assume that the problem is client side, with decoding. Looking at the screenshots it appears the resolution of the remote display is higher than 1920×1080.
Are you connecting from a Windows client? I ask because when connecting from Windows, NoMachine can support remote display resolutions up to 1920×1080 and not beyond.
More about this is available here: https://www.nomachine.com/AR09L00811
If you’re not connecting from Windows, then we need to investigate further.
If you’ve installed Workstation, then you should be seeing the screen that is in Step 3 (fig. 5) here: https://www.nomachine.com/creating-new-virtual-desktop-sessions.
We were not able to reproduce this problem. Could you enable logs on the affected servers, reproduce the problem and then send to us the whole /usr/NX/var/log directory to forum[at]nomachine[dot]com or attach them here (size is restricted). We’ll also need the client logs.
Instructions about debug and collecting logs you can find here: https://www.nomachine.com/DT04M00076.See the tutorial here: https://www.nomachine.com/creating-new-virtual-desktop-sessions.
Choose ‘Create a new custom session’ (fig. 6). Also check that you have the right package installed (https://www.nomachine.com/AR10K00724).
It’s a bug. We’ve opened a Trouble Report which you can find here: https://www.nomachine.com/TR05N06873
There’s also a workaround.
Hi, I haven’t forgotten 🙂 It’s actually been fixed and we’ll be sending you all a link to download the package.
Do you mean that before updating the NoMachine software on your client you could see the other computers on your LAN, and now you can’t? In theory, updating the client side shouldn’t affect autodetect of NoMachine servers running in the same LAN.
Have you accidentally changed something in the Player privacy settings? See this: https://www.nomachine.com/DT11M00106#2.5. If the ‘Don’t show other computers on the network’ is checked, you won’t see any available machines. Similarly, if other machines where NoMachine is installed have not checked ‘Advertize on the network’ box (https://www.nomachine.com/DT11M00106#3.1.), you won’t see them when you are on the LAN.
If you are not on your company’s LAN, your Player won’t be able to find the machines that are available. Is it possible that you have moved off the company’s network?