Support

I've just purchased the product, and fumbled around trying to get everything set up. Definitely need to ask for help now as I'm not making any progress.

I have my server hosted on a Win2012R2 just fine and am trying to set up a client on an Ubuntu 16.04 LTS Server console. When I run the vhclientx86_64 I get the error
modprobe: FATAL: Module vhci_hcd not found in directory/lib/modules/4.4.0-31-generic USBIP client drivers are not available, you will have to compile/install your own from the linux kernel source.

I got the trial server running on a Rpi 2 Minibian (easiest thing I've ever done on Linux).

Use case:
MacBook Pro Retina Late 2013 Sierra latest
WLAN AC <-> fritzbox 7490 Router
<-> Exsys 1188hms USB3 Hub
<-> USB eLicenser
Latest version of eLC Software and VH Server Demo

Windows10 PC latest
Ethernet <-> fritzbox 7490 router
latest version of VH Cient
Connecting to USB eLC @ MacBook

Connection seems to be established, according to VH Client

Running Cubase or any other eLC protected software @ W10 results in a "no eLC found" error message

Stop using eLC @ W10

I get the error "VirtualHere Client: IPC fgets failed, error 0 (No error information)" in the syslog pretty consistently, which necessitates a restart of the service.

This is running on Debian 8, and I am communicating with VirtualHere via the named pipes client API from a Java application. Given the error from VirtualHere is "fgets failed", I assume that I am breaking the /tmp/vhclient pipe somehow.

We have Safenet Sentinel (Ultra Pro) dongles at work connected to a Raspberry Pi.

I can access them from home, using Win7 guest, via Virtual Box on Mac Book (OS X El Capitan 10.11.6). The Win7 is using a Putty SSH connection to the RPi.

When using VH Client on OS X I can see and connect to the dongles, however they don't appear as usb devices. They don't seem to enumerate. They are not listed in System Profiler and "lsusb" doesn't show anything either.

I have the latest Safenet Sentinel drivers installed (and OS X 10.11 is supposed to be supported).

Hello,

I am interested in running the USB server on various of hosts that would reverse connect to a client. Packaging these for linux or windows are not a problem, but how would one go about it for Android?

What's the best practice for deploying the android server configuration file and all the certificate files that are needed for mutual server and client authentication?

Also, is client certificate and server authentication performed for reverse connections?

Thank you,
Harri

Hi all,

I'm slowly in the process of migrating from my Lenovo NAS to FreeNAS and I just noticed that there is no direct VirtualHere server build for FreeNAS. Using the Linux Server info (found here: https://virtualhere.com/usb_server_software) I can get up to step 3 (sudo ./vhusbdx86_64 -b), but I get the error "Sorry, user root is not allowed to execute './vhusbdx86_64 -b' as root on freenas.local." (freenas is what I'm using as the name for my NAS in the interim).

Hello,

I just bought and installed VirtualHere but it does not work, here is the Log server then the msg that appears on the client.

Serveur :
- 2017-01-16 18:25:41 INFO :Installing driver for class USB {36FC9E60-C465-11CF-8056-444553540000}
- 2017-01-16 18:25:41 INFO :OK driver installed try again...
- 2017-01-16 18:25:41 ERROR :Could not bind installed server driver for class USB
- 2017-01-16 18:25:41 ERROR :Error binding device 4 [13fe:4200] to connection 3, BIND_ERROR

Client:
- There was a error using this device

Hello all, from a new user of VirtualHere and a new member of the forum.

I'm having trouble handling when clients add multiple servers with the same name. I'm using the Windows service to add servers. When a user adds a server, they enter the IP address and port number. To get the name of that server, the LIST or SERVER INFO commands need to be used. With the LIST command, if two servers are connected with the same server name and same hostname:port, then there is no way to tell the difference between the two. Also the SERVER INFO command seems to only return info for the first server it finds with that name.