Failing to connect to a USB 3 device on a Windows server using a Linux client

Client dmesg:

[ 2190.672074] usb usb1-port1: attempt power cycle
[ 2191.108110] usb 1-1: new high-speed USB device number 4 using vhci_hcd
[ 2191.108118] usb 1-1: SetAddress Request (4) to port 0
[ 2191.133021] usb 1-1: Invalid ep0 maxpacket: 9
[ 2192.032082] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 2192.038376] usb usb1-port1: unable to enumerate USB device
[ 2193.044079] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 2193.940208] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 2193.947048] usb usb1-port1: attempt power cycle
[ 2195.152056] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?

Server log:


2018-12-27 16:32:51 INFO :Found High speed device [0781:5580] "SanDisk, Extreme" at address 30
2018-12-27 16:33:15 INFO :192.168.42.209 connected as connection 1
2018-12-27 16:33:21 INFO :Device 30 [0781:5580] BOUND to connection 1

Server 3.8.1 on Windows 10 1809
Client 4.6.4 on Linux 4.9.0-7-amd64 #1 SMP Debian 4.9.110-3+deb9u2 (2018-08-13) x86_64 GNU/Linux

#2

Not supported at the moment. You need to use

Linux Server - and - Linux (4.14 or later) or Windows 10/server 2016 Client for USB 3.0 devices

#3

Is this something that is likely to be resolved anytime soon?

Just in the process of evaluating this and using Linux VM clients against a windows server on the host machine is a very compelling use-case for development. The devices we typically use (event cameras) really need USB 3 bandwidth so going via a USB 2 hub isn't really a sensible option.

Thanks!,

Geoff

#4

Probably not, Linux server has much better facilities for serving USB 3 devices