Giorgi-G.

[Giorgi-G.]

Hi,

Logs show up that USB forwarding was working till 17.03.2020. Last time USB forwarding service was stopped at 17.03.2020 14:57:31 and after it didn’t start. Any ideas about what may happen?

It’s definitely some issue related to the NoMachine USB module and not to your USB devices. One of the ways that might fix this issue is to reinstall NoMachine software.

Can you please make a few more tests:

1. Do you see NoMachine USB drivers correctly in Devices Manager? Refer to Screenshot 1.

2. Check does NoMachine Devices Service is running in Services? Refer to Screenshot 2.

3. Following this instruction https://www.nomachine.com/DT10O00163#2 disable deleting session logs after session closing. Further, connect via NoMachine to a remote machine and open the USB Forwarding tab. Wait for a 1 minute, close session and send session logs as described in the link.

Attachments:

1. 

   Screenshot-1.png
   

2. 

   Screenshot-2.png
   

[Giorgi-G.]

Hi,

Few steps that might help us to detect the issue.

1. Try to connect some flash drive to your local Windows machine. Is it visible in the devices list?

2. Do you use ASMedia USB Controller on your Win machines?

3. Send us logs from your Win machine, how to collect them is described here: AR10K00697

4. Can you please attach a screen of your NoMachine Window on the devices tab?

5. Check, do you have any conflicting software installed on the machine?

[Giorgi-G.]

Hi,

The actual continuing of this post was in this thread https://forums.nomachine.com/topic/forwarding-ipad-connected-to-local-windows-to-macos-server

In your case, you can try a few things.

1. If possible connect from your Win client to any other remote machine to be sure that it’s not Windows related issue.

2. Check, do you see on NM Menu -> Devices -> Connect a USB device, USB devices from both machines?

3. To be sure that USB forwarding module works well on the remote (Mac) side please connect to Mac via NM, open NM Menu -> Devices -> Connect a USB device, after USB devices from both machines will appear, close NM menu (but not session) and open Terminal on Mac, run this command kextstat | grep com.nomachine and send output here.

 

[Giorgi-G.]

This issue is not device-related, it’s USB forwarding module related issue.

It’s on the server (Mac) side, not on the Windows side. So there is no need to do anything on Win part.

You need to uninstall NoMachine on Mac server, after installing it again and allow MacOS to install NoMachine Extensions. That should be done on Mac -> System Preferences -> Security & Privacy. The procedure is described step by step in the article I have sent you before.

To not miss the Extension approving prompt by Mac, it’s better to open Mac -> System Preferences -> Security & Privacy -> General panel before you start installing NoMachine.

[Giorgi-G.]

Hi,

First of all, it looks like you have old NoMachine installed on your machine. Please uninstall it and install the latest one.

During the installation please take a look to allow all NoMachine System Extension installation. There is an article on how to do that.

https://www.nomachine.com/AR01P00962

 

[Giorgi-G.]

Hi,

The fact that Pendrive forwarding works means that the USB forwarding module of the NoMachine is installed well, with all dependency components.

And as well as that, you can see forwarded devices in the Windows Device Manager, so this shows that it’s well connected to the remote machine.

One of the reasons why it’s not being detected by the software is maybe the device drivers are not installed properly on the machine where you forward your device.

Few more questions.

1. Can you check whether connecting your device physically to the server (not client) and forwarding the device from the server host to the VM running on the same host actually works?

2. Are your two machines located in one local network? What’s the ping time between them? In some hi-traffic devices timing of the network becomes very critical.

3. There are two optical mouses in your window, have you tried to forward the other one? Did it work?

4. Is there any chance to forward device to another Windows 10 PC (NOT VM), with installed software?

Another recommendation it’s better to forward one device at a time (especially hi-traffic device) and if it fails (with a red sign near the device) restart both machines.

[Giorgi-G.]

Hi,

1. Can you please tell me what kind of devices you have forwarded?

2. Is it possible to try to forward pendrive on mouse? The devices that work without additional software.

3. Do you have installed virtio? https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers

4. Can you please send me screenshots from NM GUI with forwarded device and Devices Manager of server-side.

Best.

[Giorgi-G.]

Hello!

Did you follow the instruction about running make under su, not just “sudo make” ?

Additionally, looks like binutils is missing on your system and needs to be installed.

[Giorgi-G.]

Hi Jarf23,

Based on the screenshot you have attached, I can conclude that the USB forwarding module is disabled on at least one of your machines.

It can be done manually by user, or another reason can be some conflicting software detected on your machine\machines.

To be more precise, can you please send the logs from both machines (Client and Server) to forum[at]nomachine[dot]com and I will try to find out the exact reason.

How to collect the NoMachine log files: AR10K00697

[Giorgi-G.]

Thanks for reply,

No there is no way to compile and install nxusb.ko without admin rights. You may ask your admin and pass him the article to do that.

[Giorgi-G.]

Hi,

Please check whether the nxusb.ko kernel object is compiled on your machine. If not, you will need to compile it. Instructions for checking and ultimately compiling are available here: https://www.nomachine.com/AR12J00658

There’s nothing else in the attachments that can help us unfortunately. Could you also please send us logs from server and client sides? https://www.nomachine.com/AR10K00697

[Giorgi-G.]

For now we can say that you have passed point #1. And the reason why USB device forwarding doesn’t work is that nxusb.ko driver is compiled but not loaded. So you will not be able to forward devices from it or connect devices to that machine.

 

It’s necessary to check and find one of two possible reasons why it’s not loaded. To that you need to have a root access. And also to fix it you will need to have root access.

Here are instructions to find out why driver is not loaded:

Run in terminal following commands:

sudo insmod /usr/NX/bin/drivers/nxusb.ko

after:

tail /var/log/syslog 

and send us output from terminal.

[Giorgi-G.]

The command lsmod | grep nxusb returns nothing.

Are you sure that before running that command you opened Devices -> Connect USB devices and waited before USB devices list will be loaded?

About logs – we didn’t receive anything to forum@.

[Giorgi-G.]

Hi,

In that case, I can explain the steps to follow for point #1. Here are instructions for how you can do that without admin rights:

Connect to remote machine, open terminal on it and type command:

cat /usr/NX/var/log/nxinstall.log | grep -i usb && ls -l /usr/NX/bin/drivers/

After go to NM Menu -> Devices -> Connect a USB device and wait 10 seconds till devices appear and type this command in the terminal :

lsmod | grep nxusb

And send us file with all output from the terminal.

Again, the above commands don’t need root access. And they will completely cover point #1.

It also may be helpful if you send us the logs from remote Linux machine. Because of you don’t have root rights, you will not be able to send us a complete package. But partial logs will be possible.

To collect them run following command in terminal:

cd ~/ && tar -czf linux_log.tar.gz /usr/NX/var/log

That command will report warnings, however don’t worry about them. A linux_log.tar.gz package will be created in your home directory. Send this file to us using forum[at]nomachine[dot]com making sure you reference your topic.

[Giorgi-G.]

Do you have root access to your remote Ubuntu?

Without it you will not be able to check any of that 3 points and the only way is to talk with the administrator of that machine administrator. If you have it – you can just the follow links I sent in my previous post.

[Author]

Posts