Support

Hi,

I am trying to register my license of USB server for windows but the isn't a license option when I right click on settings. Am I doing something wrong?

A great feature would be a usb reset for devices such as ilok which is painfull when you need to switch over another computer ...

Good morning everyone
I have one VirtualHERE server in my company (host of HASP key) installed on a RaspberryPI 3. The client is Windows 2012 Server virtual machine. Client software runs a service. I have bought one license for the server.
I'm thinking of a solution that I can prepare in case of Raspberry PI failure. My idea is to buy another RPI and make a duplicate of the SD Card from the working RPI. In case of a failure I could easily disconnect the old RPI and run the backup one and have my HASP key availabe in minutes.

2017-10-23 16:11:18 INFO :Installing driver for class SmartCardReader {50DD5230-BA8A-11D1-BF5D-0000F805F530}
2017-10-23 16:11:18 INFO :Downloading https://www.virtualhere.com/sites/default/files/usbserver/windows/win64…
2017-10-23 16:11:40 ERROR :There was an error downloading, Couldn't connect to server (0)
2017-10-23 16:11:40 ERROR :Could not install driver for class SmartCardReader

I'm trying to run a VM linux (openSuse Leap 42.3) machine on my Windows 10 PC and get access to the USB device plugged into windows.
I have the server running on windows and started the vhclientx86_64 as a deamon using the root account, so far so good.
I manually added the windows USB hub as it did not find it automatically, again all good so far.
I then did a -t LIST and my windows hub and all available devices are shown, great!
If I use DEVICE INFO or GET CLIENT STATE I receive sensible information about the device, so again all good.

Hello,

VirtualHere USB Server v3.3.7 (Built: Aug 8 2017, 20:15:44)
VirtualHere Client 4.2.1
Device: 28a1:0601 AVEST-SYSTEMS AvBign
Server OS: Red Hat Enterprise Linux Server release 7.4 (Maipo) 3.10.0-693.2.2.el7.x86_64
Client OS: CentOS Linux release 7.4.1708 (Core) 3.10.0-693.2.2.el7.x86_64

Device works without problem when its local connected. But while its connected via virtualhere device has i/o erros when vendor's java application works with it. App works with device via pcscd (pcsc-lite-1.8.8-6.el7.x86_64).

Hello,

Server service crashes when client logs off without closing Virtualhere client. Steps to reproduce:

1) Login to windows
2) Start virtual here client
3) Specify hub manually (don't know if this matter)
4) use device from server (I used usb disk)
5) Logout from windows without closing VH client
6) In half-minute VirtualHere service will stop

OS: Server - Win2016, Client - Win2012R2.

so firstly thanks so much for the app, it works nicely. my only beef is for some reason perhaps of my own making, i cannot get it to reattach to the shield. in other usb redirection apps after ejected the storage or device returns to the host usb. i eject from my computer, and then exit the app on my shield and but it will not reattach itself until i restart the shield. is this normal behavior or am i missing something? thanks in advance!

initially i setup my server on recent debian and ubuntu builds (16.04) it all worked with the exceptyion of the fact that i had to restart the service every few connections which was far from ideal, so i scrapped it once again and went back to a nice non systemd ubuntu server 12.04, now it works great but after carefully naming the many devices connected to it i wanted to backup the config.ini, id played with it loads before due to the many issues id had with the server, so i ssh in and hitup the config.ini with nano, mainly intending to backup all my naming as the other one lost it a few

Hi,

As the title suggests, I'm using an Android server to host a USB device, which I am picking up on a Windows 10 64 Bit Client.

It used to work fine, until around a month ago, and now it keeps dropping the connection.

I tried using a different Android Tablet (Amazon Fire) and that is working fine.
I can also ping the tablet in question from the command prompt on the PC and it pings no problem.

If I connect the Fire tablet at the same time, it recognises that as Android2.local.:7575 and works fine.