Menu ▾ ▴

USBIP Windows Client

Help
Galinette
2009-09-03
2018-02-21
1 2 > >> (Page 1 of 2)

  • Galinette

    Galinette - 2009-09-03

    Dear All,

    I am trying th USBIP windows client.
    The usbip -l command works and shows me the devices on the specified linux host

    However usbip -l shows me the followin error message:
    usbip err: usbip_vbus_ui.c:  49 (usbip_vbus_dev_node_name) usbvbus interface is not registered
    usbip err:       usbip.c: 374 (show_port_status) open vbus driver

    I have the feeling that the driver is not installed. When I right-click/install the bus.inf file I have no error message, but then I cannot find busenum.sys in the registry so I think nothing was installed. Reboot doesn't help.

    Thanks,

    Etienne

     

    • Galinette

      Galinette - 2009-09-03

      Sorry for the mistake : I wanted to say "usbip -l"  works but "usbip -p" displays the following error message

      Etienne

       

    • Cristiano

      Cristiano - 2009-09-09

      I had exactly the same problem. Turns out you have to actively install the driver with "Add Hardware" on Control Panel. Say you have already connected the hardware, choose "Install hardware manually from a list", then "Show All Devices", "Have Disk" and finally find the bus.inf file.

      These instructions are on a file somewhere (maybe on SVN?), but I don't remember where exactly.

       

      • Jeswin

        Jeswin - 2009-09-10

        You can follow the following steps.

        To install the virtual usb bus driver on Windows XP:

        1. Uncompress the downloaded binary package to a directory.
        2. Double-click the 'Add Hardware' wizard in Control Panel.
        3. At the 'Welcome to the Add Hardware Wizard', click 'Next'.
        4. Select 'Yes, I have already connected the hardware', then click Next.
        5. Select 'Add a new hardware device' from the list, then click Next.
        6. Select 'Install the hardware that I manually select from a list(Advanced)', and then click next.
        7. Select 'System Devices', then click Next.
        8. Click 'Have Disk', click 'Browse', choose the uncompressed directory, and click OK.
        9. Click on the 'Virtual USB Bus Enumerator', and then click Next.
        10. At 'The wizard is ready to install your hardware', click Next.
        11. Click Finish at 'Completing the Add/Remove Hardware Wizard.'

        To use it:

        1. open a command prompt window, cd to the uncompressed directory.

        2. run usbip -l 192.168.2.1 to list the exported devices from ip 192.168.2.1

        3. run usbip -a 192.168.2.1 2-1 to imported the device.

        (Of course, you should change 192.168.2.1 and 2-1 to something else)

         

  • Anonymous

    Anonymous - 2010-06-25

    Hi

    I installed as per instruction and all seems to be OK except error at beginning

    usbip -l 192.168.42.155

    usbip dbg: usbip_network.c: 229 (tcp_connect ) trying 192.168.42.155 port 3240

    usbip dbg: usbip_network.c: 255 (tcp_connect ) 192.168.42.155:3240, no destinati
    on to connect to
    - 192.168.42.155 failed

    any advice ?

    thanks
    Peter

     

  • Bill Kearney

    Bill Kearney - 2010-10-08

    Is the daemon actually running on the linux machine at 192.168.42.155?  You can start it from a terminal shell, just run it as a program.  usbipd with no parameters.  That'll leave it running in the terminal so you can see whatever messages it generates.

     

  • Raghavendra

    Raghavendra - 2011-04-29

    Hi

    The driver is installed as said in the above procedure on Windows XP.

    I am not able to attach the usb port for sharing on network.  When following command is run to attach

    somefolder>usbip -a 10.246.78.198 0
    usbip dbg: usbip_network.c: 229 (tcp_connect ) trying 10.246.78.198 port 3240

    usbip dbg: usbip_network.c: 255 (tcp_connect ) 10.246.78.198:3240, no destination to connect to
    usbip err:       usbip.c: 294 (attach_device) tcp connect

    Help to solve the problem.

    Thanks
    Raghavendra

     

  • Arjan Mels

    Arjan Mels - 2011-04-29

    Sounds like the daemon (usbipd) is not running on your server.

     

  • Raghavendra

    Raghavendra - 2011-04-29

    Thanks for the solution.  Where can I find it? How to run the daemon (usbipd)?

     

  • Arjan Mels

    Arjan Mels - 2011-04-29

    The daemon is part of the linux client tools. The latest precompiled version 0.1.7 can be downloaded from: https://sourceforge.net/projects/usbip/files/usbip/0.1.7/. The most recent version is present as source code in the SVN repositry.

     

  • Fred

    Fred - 2011-06-14

    I am attempting to fully understand how the windows client works.
    Currently I can establish a connection to the remote device, however the it seems the command prompt must stay open for the duration of the session as I have thew following: 

    new usb device attached to usbvbus port 1
Receive sequence:    47900

    If I close the terminal session the connection is closed.

    I am using version "usbip_windows_v0.2.0.0_signed"

    Is this a normal function?
    Is there a work around so that I don't have to keep a terminal session open at all times?
    How can I make it so that my usbip sessions are constant through restarts?

    Many thanks in advance for any comments.

    Regards

    Fred

     

  • Arjan Mels

    Arjan Mels - 2011-06-14

    You indeed have to keep rge program running. So normal function.

    To keep the sessions ocnstant during restart, you could use some startup scripts.

    I am busy developing a GUI version which will also support this.

    Regards,

    Arjan

     

  • Andrey Bogachenkov

    Andrey Bogachenkov - 2011-06-21

    Hi all,

    Driver 0.2.0 is installed properly and device "USB/IP Enumerator" is seen in System Devices.

    I can see shared devices with usbip -l <server>, but when I try to connect it with usbip -a, I get:

    C:\UsbIp>usbip -a 192.168.1.173 4-1
    request failed at peer, 1
    usbip err: usbip_windows.c: 712 (query_import_device) recv op_common
    usbip err: usbip_windows.c: 840 (attach_device) query

    or with debug option:
    C:\UsbIp>usbip -D -a 192.168.1.173 4-1
    usbip dbg: usbip_network.c: 223 (tcp_connect ) trying 192.168.1.173 port 3240

    usbip dbg: usbip_network.c: 243 (tcp_connect ) connected to 192.168.1.173:3240
    usbip dbg: usbip_windows.c: 767 (query_interface0) exportable 1 devices
    usbip dbg: usbip_windows.c: 784 (query_interface0)      4-1: Aladdin Knowledge
    ystems : HASP v0.06 (0529:0001)
    usbip dbg: usbip_windows.c: 785 (query_interface0)         : /sys/devices/pci00
    0:00/0000:00:1d.2/usb4/4-1
    usbip dbg: usbip_windows.c: 786 (query_interface0)         : Vendor Specific Cl
    ss / unknown subclass / unknown protocol (ff/00/00)
    usbip dbg: usbip_windows.c: 806 (query_interface0)         :  0 - Vendor Specif
    c Class / unknown subclass / unknown protocol (ff/00/00)
    usbip dbg: usbip_windows.c: 809 (query_interface0)
    usbip dbg: usbip_network.c: 223 (tcp_connect ) trying 192.168.1.173 port 3240

    usbip dbg: usbip_network.c: 243 (tcp_connect ) connected to 192.168.1.173:3240
    request failed at peer, 1
    usbip err: usbip_windows.c: 712 (query_import_device) recv op_common
    usbip err: usbip_windows.c: 840 (attach_device) query

    Can anybody help me?

    BR,
    Andy

     

  • Arjan Mels

    Arjan Mels - 2011-06-28

    Can you show the output of usbip -l? Usually device numbers take the form 4-1.1 (Bus 4-Device 1 function 1) (so I am suprised by the 4-1).

     

  • kinlau

    kinlau - 2011-06-29

    hello, arjanmels.
    I used client tool 0.2.0, attach a camera from ubuntu. When I start camera, something wrong on it.

    new usb device attached to usbvbus port 1

    usbip err: f:\usbip\windows\tag\usbip_windows-0.2.0.0\usbip_vbus_ui.c: 275 (usbi
    p_header_correct_endian) unknown command in pdu header: 0

    the messages on server(ubuntu) is:

    write “add 1-1” to /sys/bus/drivers/usbip/match_busid
    message: bind 1-1 to usbip, complete
    listen at  :3240
    usbipd start (usbip 0.1.7 ($ID: stub_server.c …)
    connected from …..
    connect 1-1

    whether  the version 0.1.7 on the server not match the version 0.2.0 on the client?
    or sth. else?

     

  • kinlau

    kinlau - 2011-06-29

    my ubuntu version: linux ubuntu 2.6.38-8-generic #42-ubuntu SMP Mon Apr 11

     

  • kinlau

    kinlau - 2011-06-29

    client side is win7 os

    before this, I could not attache the device in xp os

     

  • Mark

    Mark - 2011-07-24

    I'm seeing a slightly different problem….can't even get "-l" to work.

    Server (192.168.0.4) up and running, one device shared as per usage README.

    Client is XP-32bit. Drivers installed per instructions. I can ping the server no problem, but when I try usbip -l 192.168.0.4 I get:

    usbip err: usbip_network.c: 121 (usbip_recv_op_common) recv op_common, -1
    usbip err:       usbip.c: 216 (query_exported_devices) recv op_common
    usbip err:       usbip.c: 288 (show_exported_devices) query

    BTW - I checked in the device manager, and the USB/IP ENUMERATOR is listed and shows it is working properly. Any ideas?

    Thanks.

     

    • Ildar Mulyukov

      Ildar Mulyukov - 2013-11-18
       

      Last edit: Ildar Mulyukov 2013-11-18

  • Arjan Mels

    Arjan Mels - 2011-08-07

    Hi Kinlau, I have been on holidays for a while.  Did you solve your problem in the mean time?

    Epicmark is the usbipd (daemon) running on the linux box?

     

  • kinlau

    kinlau - 2011-08-08

    Welcome back, arjanmels.

    Now, I have connceted server(1.0.0) with usbip on xp/win7(I rebuilt it for version mismatch).
    usbip -l XXX can be used.
    usbip -a XXX x-x can be used, but when xp/win7 detected the device, it cannot find the divice driver.
    My device on the server is a camera, and it works well.

     

  • kinlau

    kinlau - 2011-08-08

    My vhci driver is version 0.2.0.0.

    Thanks!

     

  • kinlau

    kinlau - 2011-08-08

    Hi, arjanmels.
    Today, I have tested usbip.exe(0.1.0.0) to connect usbipd(0.1.7) successfully. And vhci driver is 0.2.0.0.
    I used two webcam to test it.
    usbip.exe can find the two webcam plugged in the server, and client OS can installed the cameraes's driver successfully.
    But when I start the first camera, it happens erros as follows:
    usbip err: usbip_vbus_ui.c: 266 (usbip_header_correct_endian) unknown command in pdu header: 0
    When I start the second camera, blue screen happens.

     

  • kinlau

    kinlau - 2011-08-10

    Who can help me, please?
    I have tested this enviroment many times in different machines.
    why does the usbip error happen? usbipd has no errors.

    Thank you!!!

     

  • Anonymous

    Anonymous - 2011-08-18

    Hi, I'm finding the same problem on a XP client, ArchLinux server. On the server, usbip -l localhost works fine, but on the client's doesn't: 

    C:\Documents and Settings\imasdetres\Escritorio\usbip>usbip -D -l 192.168.1.199
usbip dbg: usbip_network.c: 223 (tcp_connect ) trying 192.168.1.199 port 3240
usbip dbg: usbip_network.c: 243 (tcp_connect ) connected to 192.168.1.199:3240
- 192.168.1.199
usbip err: usbip_network.c: 121 (usbip_recv_op_common) recv op_common, -1
usbip err:       usbip.c: 216 (query_exported_devices) recv op_common
usbip err:       usbip.c: 288 (show_exported_devices) query

    and on the server I see 

    onnected from 192.168.1.170:2664
usbip err: usbip_network.c: 119 (usbip_recv_op_common) recv op_common, -1
usbip err: stub_server.c: 197 (recv_pdu    ) recv op_common, -1
usbip err: stub_server.c: 413 (process_comming_request) process recieved pdu
     
1 2 > >> (Page 1 of 2)

Log in to post a comment.