Giorgi-G.

[Giorgi-G.]

Hello,

We make tests on our machines with printer\scanner sharing and it works very well.

For now we can suggest to try few things:

1. Completely uninstall NM from both machines.

2. Install latest NM version on both machines NoMachine 6.0.66

3. Try to share any another USB device i.e. USB flash drive.

Also please provide us some info about kernel version on Raspberry Pi.

[Giorgi-G.]

Dear Sebastian,

If your Canon LiDE 60 Scanner is visible on your RPI 3 as a common USB device, it can be forwarded with help of USB forwarding that will be available in RPI packages in version 6.0 – coming soon.

Best Regards,
Giorgi

[Giorgi-G.]

Hello,

In that case you can disable NoMachine USB driver on Windows.
It will allow you to keep using NoMachine as long as the USB driver is disabled.

To do that, just follow next steps:

1) First step is to remove all devices:
a) Run the device manager: Control panel -> Device Manager
b) Uninstall all “NoMachine USB Stub” devices if they exist.
c) Uninstall all “NoMachine USB Host Adapter” devices if they exist.

2) Second step is to remove all drivers:
a) Run console with administrator rights:
Menu start -> Run -> cmd -> Right click -> Run as administrator
b) Run the Windows sc.exe tool from console:
> sc stop nxusbf
> sc stop nxusbh
> sc stop nxusbs
> sc stop nxusbd

> sc delete nxusbf
> sc delete nxusbh
> sc delete nxusbs
> sc delete nxusbd

Note: when given service doesn’t exist yet, sc tool returns error 1060, which is not an error in this case.

3) Third step is to unregister “NoMachine USB Hub Filter”
a) Open Windows registry:  Menu start -> Run -> regedit
b) Find the following registry key in the tree on the left:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\36fc9e60-c465-11cf-8056-444553540000
c) Find UPPERFILTERS variable on the right side.
Note: it should contain list of registered filters, but maybe it’s empty if no filter is registered.
Edit UPPERFILTERS variable and remove entries containing nx prefix (e.g. “nxusbf”) if they exist.
d) Reboot the machine.

Best Regards.

[Giorgi-G.]

Hello,

Unfortunately this workaround cannot help on Sierra.

On most recent versions, MacOSX implements a new way to manage USB devices
and the current version of NoMachine USB drivers is not suitable for that.

The new USB drivers, ready for Mac 10.11 and later, will be available with the
incoming major version, NoMachine v.6.

This TR (https://www.nomachine.com/TR09M06042) is about your issue and you can subscribe to it. You will be notified when it will be fixed.

Best regards.

• This reply was modified 7 years, 1 month ago by Britgirl.
• This reply was modified 7 years, 1 month ago by Giorgi-G..
• This reply was modified 7 years, 1 month ago by Giorgi-G..

[Giorgi-G.]

Hello,

As I see you have two problematic issues – one is with NoMachine USB sharing driver (nxusbf.sys) and another one is with VIA Labs VL810 USB 3 Hub driver (vl810filter.sys). Maybe they are correlated somehow.

For resolve this I can offer few things to do

1. Update driver for V810 controller driver
2. Try to disconnect this hub (if possible) from your machine and check again
3. Try to disable USB sharing of NoMachine – https://www.nomachine.com/TR01N06385

Additionally want to say that the current version 5.3 still has an old version of drivers for USB sharing. We are aware that these drivers may cause issues with some operating systems and hardware. We will provide an up-to-date version of USB drivers with the incoming v. 6 (which should be released soon). Once available, we expect that upgrading to v. 6 will help to solve also your issue.

Regards.

[Giorgi-G.]

Hello,

The current version 5.3 still has an old version of drivers for USB sharing. We are aware that these drivers may cause issues with some operating systems and hardware. We will provide an up-to-date version of USB drivers with the incoming v. 6 (which should be released soon). Once available, we expect that upgrading to v. 6 will help to solve also your issue.

Regards.

[Giorgi-G.]

ARCH Linux is not among the Linux distributions that we officially support, even if we are interested to make NoMachine able to work also on such platform, we cannot say when a fix can be made available. We have opened a new trouble report to track this problem: https://www.nomachine.com/TR06O07837, you may register to ‘Notify me when the TR is closed.’ to be informed when the fix is made available.

[Author]

Posts