Forum Replies Created
-
Posts
-
Hi, thanks very much for sending us the logs that you did (2 sets). Unfortunately, the second set didn’t contain new logs (from the moment the problem occurs). This means that we still need a new set of logs without the problem (again), then a second attempt of the second set of logs as soon as you encounter the problem.
We appreciate this is tiresome, but we have no other way of investigating this issue that only you are encountering. Something is happening in between and we have no idea what this can be. No one else has reported it and we have attempted several times to reproduce without success 🙁
I think what you need is NoMachine Network (originally named Anywhere). This functionality is coming soon. Please take a look at the Feature Request we have in our KB and use the notify me tool to know when it has been released.
If you are still encountering issues, what I suggest is you enable debug, reproduce the problem and then send us the logs (to forum[at]nomachine[dot]com. Both server and client side. Please follow the instructions here: https://www.nomachine.com/DT07M00098
This last question is dealt with here: https://www.nomachine.com/forums/topic/connection-drops-due-to-random-port-changes
You say specific software, can you tell us which software applications you are using?
Is 5.3.9 on the server? If so, what’s on the client-side? If 5.3.9 is the client side, what NoMachine software did you install on the machines you are connecting to?
Ideally this problem needs to be in the Mac section because it’s a different issue for a different OS 😉
USB sharing on macOS 10.12.5 is not possible because in v5 this OS version is not supported. It’s supported on versions from 10.6 through 10.10.5.
With the release of version 6 usb sharing will be supported on the last macOS versions as well.
We are currently investigating this. So far we’ve not been able to reproduce it.
It is most like due to an incorrect installation/uninstallation of a previous version of nxusbf.sys driver.
Have you tried removing NoMachine, restarting PC and installing it again?
Hi, can you submit those logs to forum[at]nomachine[com]. Make sure you reference the topic link in your email. Thanks!
Do you happen to know what version of NoMachine is on the University server? Can you tell us in your email with logs which Uni it is so we can check if they are a customer? If so, we can reach out to them.
This is related to Fedora’s use of Wayland.
Please see the following Feature Request which documents adding support for Wayland: https://www.nomachine.com/FR10N03221.
Until we add support for Wayland protocol you should disable Wayland in the gdm configuration by adding the following key in /etc/gdm/custom.conf:
WaylandEnable=false
I don’t know what version you have installed. You say 2016 – does this mean it’s v5?
From version 4 onwards the free version of the NoMachine software allows access to the physical desktop of the remote host (1 connection).
If you want to run 2 instances of the Linux environment on the same host you need the Workstation installed. You can download this from the website as an evaluation here: https://www.nomachine.com/download-enterprise#NoMachine-Workstation.
We use Microsoft’s DXVA and DirectX 9 APIs for hardware decoding acceleration on Windows platforms. The problem you’re having is that this function from DX9 returns to us invalid values of frame stride. Without the correct value we can’t process frame and therefore this crash happens. You can switch to software decoding by setting key “Enable hardware accelerated decoding” in player.cfg to “disabled” – in this case by default you’ll be using VP8 decoding, unless you follow steps in article https://www.nomachine.com/AR10K00696 or buy AVC Pack to enable H264 software decoding. Other possibility would be to update graphics drivers and DirectX. Also make sure you don’t have any custom DirectX libraries in your system in default paths that could be loaded instead of original ones.