Support

Hello Michael,

while a new Windows client version is started, its driver will be installed.

But since the program name changes each time, I got several entries now in list of installed programs:
Windows Driver Package – VirtualHere (vhhcd) USB (MM/DD/YYYY )
Windows Driver Package – VirtualHere (vhhub) USB (MM/DD/YYYY )

Please change the program name to a unique one, that the old one can be overwritten or add a deinstallation of old version first.

Hi!

since yesterday i have a strange behaviour. I have 3 Devices connected to my banana pi. Only two devices work at the same time.
After taking a look in the logfiles on the server, i recognized, that it seems, that the server is binding twot devices to the same connection. Is there a manual way to prevent it?

Here the Log:

I am running CentOS7 on a Rasberry Pi2B with a licensed version of VirtualHere and everything works as expected.
When i invoke:
[root@rpi2 ~]# /usr/sbin/vhusbdarmpi2 -b -c /root/config.ini
the program starts as a daemon and runs. But when I try to enable automatic start via systemd the service starts but then exits after a short time.

Here is the systemd service file. I used the one from this forum:

Hello,

I want to use a Canon DR-F120 scanner connected to my Synology NAS.

My problem is that the VirtualHere client recognises the scanner (I can see it in the list under USB Hubs / Synology Hub), but I'm unable to use the scanner from any program. For instance if I go into Adobe Acrobat and select the Cannon scanner I get a message that says "Can't locate device; check cable and power.(-4536)" and then another that says "Acrobat could not communicate to this device."

Dear Support,

I have a setup using:

- Server running on Synology DS212j DSM 6.0 registered with "3 device" license
- Attached FT232RL USB device (RFXtrx433)

- Client running on Raspberry Pi
- Client running in daemon mode - using the provided init script
- device connected via network and used as /dev/ttyUSB0

So far I was able to connect and use the /dev/ttyUSB0 device for a couple (5-10) seconds. Then the whole Raspberry Pi hangs - no network access / ui freezes. Reboot is needed on the client.

I have a USB dongle that I want to use with my Synology. Unfortunately, the dongle needs to be in a different location than my Synology server. I would like to make Synology have remote access to this dongle using VirtualHere. I tried to run VirtualHere client on synology, but I receive the following error:
USBIP client drivers are not available, you will have to compile/install your own from the Linux kernel source
Is it possible to run VirtualHere client on Synology server?

I'm not sure if this has been discussed yet - I've searched through the support logs for any reference, but found none.

We use quite a generic (read unfriendly) username logon at work - a five digit number, so when I have a dongle in use it show 'In use by 12345 at PC5'

Is it possible to assign friendly names to the user, so 12345 becomes 'Richard'?

Thanks

Richard (12345)

Hello,

I installed today a Synology DS216J. I enabled "Any Publisher". But there is no "VirtualHere" in "all modules" list. I try every Synology build with manual install, but it failed for all of them.

Is this NAS supported ?

Thanks for your help

Hi,

I'm using an unlimited version (registered) on raspberry Pi, connecting from windows client.

Your software is really nice as it's usable over VPN remotely. So Far i managed to switch on my Ham Radio
(IC-7300) with the remote control software and control it.

Unfortunately, the audio doesn't seem to come thru. The device in device manager is basically the same.

The Device is identified as Speakers (USB Audio CODEC): inf name audioendpoint.inf, using a microsoft driver.

Running VirtualHere on Windows7. I have Steam Link build 513. At first, VirtualHere was unable to see the steam link, even when manually assigned via "specify hubs". Eventually, without warning, VirtualHere was able to see the SteamLink (without using specifiy hubs) and this ability remained for several hours. After that, it stopped again and hasn't resumed since.