Skip to main content

How to install USB/IP for Windows on Server 2008 R2

By
USB/IP Project aims to develop a general USB device sharing system over IP network. To share USB devices between computers with their full functionality, USB/IP encapsulates "USB I/O messages" into TCP/IP payloads and transmits them between computers.

A fork of USB/IP client on Windows is located here. Getting this forked version to work with Windows Sever 2008 R2 is not straightforward. I have documented below how I was able to get it to work 2008 R2.
  • Download 0.1.0 (https://github.com/cezanne/usbip-win/releases/tag/v0.1.0), download all into a directory excluding source*
  • Remember to unblock the files
  • Save to c:\usbip
  • Download x64 build for Win7 (https://github.com/cezanne/usbip-win/files/4743857/usbip_vhci_v0.1.0_win7_x64.zip)
  • Unblock the zip file
  • Extract
  • Copy the files and overwrite files in c:\usbip

Allow running non-validated driver
bcdedit.exe /set TESTSIGNING ON
Restart computer


Import certificates manually
  • Run mmc.exe
  • File | Add/Remove Snap-in…
  • In Available snap-ins, select Certificates
  • In This snap-in will always manage certificates for: select Computer account
  • In This snap-in will always manage: radio options, select Local computer: (the computer this console is running on)
  • Click on OK
  • Navigate to Certificates (Local Computer) | Trusted Root Certification Authorities | Certificates
  • Do Actions | All Tasks | Import…
  • Click Next
  • In File name: Browse to C:\usbip\usbip_test.pfx
  • In Password: type usbip
  • In Certificate Store select Place all certificates in the following store
  • Click Next
  • Click Finish
  • Click OK
  • Verify USBIP Test Certificate is added
  • Next add the certificate into Trusted Publishers, Navigate to Certificates (Local Computer) | Trusted Publishers
  • Repeat steps 8 to 16

Install driver manually
  • Open cmd.exe to c:\usbip
  • Run pnputil -i -a usbip_vhci.inf
  • Add legacy device manually, run devmgmt.msc
  • Select root item (ComputerName) Do Action | Add legacy hardware
  • In Welcome to the Add Hardware Wizard, click Next
  • In What do you want the wizard to do? select Install the hardware that I manually select from a list (Advanced) then click Next
  • In Common hardware types: select Show All Devices and hit Next
  • In Select the device driver you want to install for this hardware, click Have Disk…
  • In Install from Disk browse to c:\usbip
  • In Model select USB/IP VHCI and hit Next
  • In Hardware to install: hit Next
  • Wait and hit on Finish

To list devices that can be attached
usbip list -r <ip>
usbip list -r 192.168.1.2

To connect to specific USB device
usbip attach -r <ip> -b <bus id>
For example, to connect to a USB device on bus 5-1 (from the command above), do:
usbip attach -r 10.223.22.154 -b 5-1

Related issues:
https://github.com/cezanne/usbip-win/issues/154

Labels:

Comments

Post a Comment

Popular posts from this blog

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

By
Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re
11 comments
Read more

The following add-ins could not be started MonoDevelop.GnomePlatform

By
Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.
21 comments
Read more