Forum Replies Created
-
Posts
-
Can you send those logs to forum[at]nomachine[dot]com? They were likely too big for the forums to attach.
We will be releasing patches in the next update (coming soon) to get round these nvidia problems that were recently introduced in their drivers.
We’ve reproduced this and opened a Trouble Report which you can see here: https://www.nomachine.com/TR06N06920
Please sign up to receive a notification when a fix has been released.
Hi, can you confirm what version is on the server side? You mention 4.6.16 – is that both sides?
Also, is it copy from Win to paste in Linux that’s not working, or the other way round? Both ways? What application are you using and in which desktop environment on the Linux server?
Hi, thanks for your feedback 🙂
I can answer straight away on a few of your points/questions. One of our devs will be looking in to the issues you’ve reported in 1) and as a consequence will also cover 2) and 3) in your conditions list.
3) What makes my machine accessible remotely: a) leaving the computer on and the application running? or b) leaving the computer on and the service is running?
To be able to access your machine you need to leave your computer on, and the NoMachine service running (check the status in the icon tray that !M is visible).
4) In one sentence what is the basic difference between NoMachine free (peer-to-peer) and NoMachine cloud?
Cloud Server provides access via the browser, so you don’t need to install NoMachine on the connecting client.
5) Will NoMachine cloud run on FreeBSD (for UNRAID)
The supported platforms on which you can install NoMachine (server side) do not include FreeBSD. We are currently evaluating whether to add it.
With regards to your suggestions, we really appreciate you submitting them. We’ll analyze them one by one and see what improvements can be made. I’ll point out at this stage that point 4 in your suggestions list will be solved when we release NoMachine Network (was Anywhere). You can read more about this here: https://www.nomachine.com/FR07J02731
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.