Support

I have installed the server: virtualhere generic arm-version (no pi at end of file) on a raspberry pi 3b raspbian
And the client on a Windows 10.
Server is found, the server lists the device correctly as webcam gadget (i had the film scanner installed locally previously).
But after some seconds the device disconnects. Some seconds later, it connects again. And keeps on reconnecting...
What can i do?

Hey,

Just wondering if you can have 2 or 3 users effectively share a USB scanner (No network port on it). Not all would need to scan at the same time but it would be placed as a central resource all 3 can access.

Thanks,
Matt

Hello!
This is to ask support with VirtualHere on a new QNAP Nas (full updated) where we installed VirtualHere.

It seems like randomly VirtualHere server stops working: on client we find a system message "Could not connect to 192.168.xx.xx:7575".

The only thing we do is to restart the NAS and then it correctly finds the Hub; no action is done in the meanwhile on client.

Is there a log on the QNAP Nas? What's going on? We already installed lasted VH version.

Thank you for your help and support!

Hello,
As 4K is becoming more relevant, I am transitioning to use VirtualHere on my Mi Box S from the Steamlink Hardware. I have been using VirtualHere for years, and I am completely satisfied as it is the only solution for connecting devices to my pc remotely without latency.

My Xbox One Controller works perfectly on both Steamlink Hardware and the Mi Box.

Hi I’ve not used my Brother HL 1430 Laser Printer for a while and when I connect the USB to VirtualHere to my Shadow cloud PC the Android server crashes. It’s a really old printer but it does the job. Anyway I have rolled back to a previous version on my Shield TV and it’s now working fine. Just thought I’d mention this as it something in the latest version of VirtualHere is not liking the printer. Thanks.

Hi, I've been using version 5.1.1 running as a Windows serivce sucessfully. I've updated the binary to 5.1.2 and now the service cannot start. I've restarted Windows, uninstalled and reinstalled the client as a service, however the problem persists. When I try to start the service manually, I get this error message:

"The VirtualHere Client USB Sharing service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other service or programs."

Running server on a pi3, client on Windows 10 64bit. Recently stopped working seems like after a MS update. the client connects and shows the connection, but I cannot use the usb ports on the pi or Windows doesn't recognize them. Here is the logs:
2020-11-15 17:53:31 INFO :VirtualHere Client 5.1.1 starting (Compiled: Nov 14 2020 20:33:06)
2020-11-15 17:53:31 INFO :Client OS is Windows 10 (build 19041), 64-bit edition
2020-11-15 17:53:31 INFO :Using config at C:\Users\weirp\AppData\Roaming\vhui.ini
2020-11-15 17:53:31 INFO :IPC available at \\.\pipe\vhclient

I've got a windows server with a license and a linux client where the can be run manually using the -n option and everything works fine. What i'd like to do now is setup the linux server so that i don't have to ssh in and start the client each time it needs to be rebooted. To do that it needs to be installed as a daemon which is a supported configuration and there's a near guide about it at https://virtualhere.com/client_service but i can't work out what to do with the script provided.

is it possible to access one usb port by two users at the same time, e.g. insert a flash drive and make it available for clients who can use it by two users, now when the device is used by the first user, the second user receives information that the port is busy and can't use it

We have a large number of raspberry pi's setup as thin clients for end users to use to connect to terminal servers. The users need to be able to use a webcam and Mic (USB) and join meetings. I'm able to get the webcam to work with VirtualHere but the mic (built in to the webcam) only shows up on my admin profile on the terminal server, the end users are not able to see the microphone device at all on any profile. When I was testing VirtualHere I did the initial test under my profile so all the drives installed under my admin profile.