May 10, 2018 at 08:14 #18337
I have a Windows 10 Home host, connecting to Linux (Ubuntu 14, 16 – Centos 6, 7) / Windows (Windows 7, Windows 10, Windows Server 2012R2, Windows Server 2016) VM’s under VMWare ESXI. I have loaded the latest 6.1.6 version of software on all of the machines.
I have a serial port based device that I need to setup in USB Passthrough into a VM while I’m using it. However, on the Windows 10 host, there are no devices recognized to pass through, regardless of what I plug into the USB ports. The local device list is empty. This same behavior exists across three different PC’s, all running Windows 10, all needing to import a USB Serial device into a virtual session.
The hosts that exhibit this behavior:
x79 chipset 4930K Desktop – Windows 10 Professional
HP x360 Spectre i7 7750 – Windows 10 Home
Dell Latitude 7470 i7 6600 – Windows 10 Professional
How do I debug this and get it working? It does not matter what I plug into USB, phones, serial ports, mice, USB sticks. Nothing is recognized in the interface.
6 months ago, this all worked fine….. it seems that something has massively broke in NoMachine during this time. However, your software auto updates itself, so I’m not sure which version worked.
Chris VMay 10, 2018 at 08:16 #18344BritgirlKeymaster
Hi, please submit the image as an attachment again. Thanks!May 10, 2018 at 17:23 #18355
Can you please check if this file exists?
And if exists – what it contains?May 11, 2018 at 08:30 #18356
I’ve attached two images. One of NoMachine showing no USB devices at all. The other is of USBView, which shows my serial device, mice, keyboard and other devices plugged in under the Intel USB chipset.
If you have any ideas on how to get these devices to show up…NoMachine is not recognizing anything.
Attachments:May 11, 2018 at 14:45 #18365
Thanks for this images, it’s helpful.
The logs will hopefully tell us what’s wrong. Please compress and send us this folder C:\ProgramData\NoMachine\var\log
Regards.May 14, 2018 at 14:47 #18379
C:\ProgramData\NoMachine\var\log\nxusb.log does not exist.
Chris V.May 14, 2018 at 14:47 #18380
I’ve done a bunch of work tonight to solve this issue.
I had to recompile the driver on all of my target Linux VMs.
When I dual boot over to Linux on my hosts, using the Linux NoMachine 6.1.6, I can successfully attach USB Devices.
However, from Windows, I still have no devices recognized on the host. I’ve uninstalled, reinstalled NoMachine. No change. I reverted my Windows 10 from 1803 to 1709; still no change.
Still looking for suggestions.
Chris V.May 14, 2018 at 14:48 #18381
Last test for the evening. I have loaded 6.0.66, which was the original version that I had in my downloads directory.
This version now works. Therefore, something broke between 6.0.66 and 6.1.6 with USB and the configuration of these systems.
I’ll try to isolate this further when I have more time.
Chris V.May 16, 2018 at 09:59 #18399
Between 6.0.66 and 6.1.6 we added disabling of USB forwarding in case of detection of conflicting drivers. To check is it the reason why it not works on your VM’s we will need ziped logs from this folder C:\ProgramData\NoMachine\var\log
Thanks.May 23, 2018 at 12:15 #18465
Here are the logs. I’ve gone back to 6.0.80 on all of my nodes. Recompiled the linux USB driver. Everything then works. If I add 6.1.16 on any node, it does not work at all.
Here are the logs.
Attachments:June 7, 2018 at 10:35 #18596
Could you please define what “detecting conflicting drivers” mean? I’ve updated my usb drivers to the latest that the chip manufacturer offers. Asmedia and Intel. Still does not work with 6.1.6. However, I believe your new code is detecting a condition that does not exist in my system; since the code without this check works fine.
As I also stated before, This happens on every system I have… 7470 Dell laptop to Asus desktop x79 Deluxe to VMWare Virtual machines on an ESXI host with virtual usb. So, I think I will make a plain statement that your code is creating a false positive detection on every system I own.
Chris V.September 13, 2018 at 17:26 #19596
1. I checked attached logs and there is nothing strange correlated with usb forwarding module. Also it’s a bit problematic to read such a big log with different versions installed. So before collecting log it’s better to clean log folder and after restart the collection of new logs.
2. Please note that we released new version of NoMachine v6.2.4, that probably fixes issue you have. So consider updating.
3. “Could you please define what “detecting conflicting drivers” mean?”
– We simply check whether the ASMedia Root Hub driver exists in the system on the path “C:\WINDOWS\system32\drivers\asmthub3.sys”. And if it does, NoMachine disables the USB forwarding mechanism to avoid potential problems (in the worst scenario on rare occasions a BSOD). The only option to get worked USB forwarding on those machines is to completely uninstall ASMedia driver from the system and use default USB3.0 drivers from Windows.
You can check manually whether that file exists on your system now.
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.