Support

Michael,

We're getting on well with our two (Linux & Win64) servers - currently offering 47 dongles to 10 users.

Something you may have already considered and rejected, but which I feel may be of benefit to those with large number of attached devices is a method of grouping 'like' dongles.

For example, we have 9 different types of software license dongles attached, with between 2 and 7 dongles of each type. In order to identify them, I have used nicknames so they currently show as:

I wish to create a script using the API to allow certain client machines to connect to just one specific port on a server.
Looking at the API documentation I can see the command to connect to a server from a client example vhui64.exe -t "USE,QNAP.114", am I correct in assuming the QNAP is the FQDN of the server and the .114 is the port number? I've tried using the command in this way but it fails.
Again for the command "STOP USING,
" would it be [FQDN].[portnumber]?

Thanks for your help,
Rob

Before I begin I would like to thank you for making this software.

Running the Virtualhere win64 version in Windows 7. I want to only show 1-2 devices to clients. Tried using, 'AllowedDevices=54c/268', but it doesn't work. The client still shows all connected devices. What's weird is, 'IgnoredDevices=54c/268', works in hiding the device. Am I doing something wrong?

Any help is appreciated. Thanks!

Michael,

Have just started setting up the windows server after installing the licence... I appreciate the windows VH is still in development...

The windows machine (Win7 x64) we're using has three devices attached (mouse, keyboard, printer).

Keyboard - 45E/DD
Mouse - 45E/39
Printer - 3F0/4E17

I tried ignoring all three through the client which initially got rid of the mouse and printer, but only amended the config.ini with the details of the keyboard and mouse!

I sent this in via email but then thought that might not be the right media for support.

I've recently switched from the QNAP Server to the Windows Server. At the present time I'm using three devices. A USB 2 flash drive, a 1TB USB3 HDD and a 4TB Seagate Portable HDD.

The first two work fine but the 4TB drive shows. The following error in the eventlog.

:Cannot capture device USB\VID_0BC2&PID_AB28\MSFT30NA7P19PB because it is of class SCSIAdapter

I've tried moving it to a USB2 port which shows the same issue.

Hello!

First of all, congratulations on excellent service and this really good concept.

Right, what I`m trying to do, is connect my ham radio to my Raspberry Pi 2 and access remotely from my shed. (The radio is in a cupboard in a house)

A few details if you will indulge me...

Rig: Icom IC-7100 - Has own built-in USB sound card (as a Silicon Labs CP virtual COM port and virtual USB audio device...
Raspberry Pi: Latest Raspbian Jessie / VNC
Connection: Cat 7 u/ftp cabling

Awesome product.
I would like to get some input of my proof on concept.

I have 20 printers, all identical. To them I want to connect 20 android phones, that is running the android server.
The android devices will VPN to a private network where the client also resides on a single windows machine.

The 20 printers will be represented as usual windows printers, they will be renamed in windows to prevent them being auto-named as Printer (Copy1), Printer (Copy2) etc. I plan to use the client API to control the devices on the client side.

Hello (Sorry for the bad English)

configuration:

OS remote: steam OS 2.0 update 1:2.70
OS local: Windows 10 home 64 bit

I purchased the VirtualHere from Steam. From Windows 10 configure the application to connect to the steam link, but the failed connection.
From Steamlink start the application locally, but it closes after entering the steam user password (start using "sudo").

What can I do?
Thank you

Hello

I recently posted this on the steam link forums but have not had a response, I don't know what relationship you have with valve and how your product is integrated into the link but hopefully you can help

I have PC(192.168.0.55), host server(100.111.111.111), pi (192.168.1.2 or when in the same router 192.168.0.44)

when the pi and the PC under same router, the Virtual Here Share USB over Internet could easily find the shared usb ip: 192.168.0.44:7575, and it works perfect.

Now, I made Pi connect with a different network. its internal ip changed to 192.168.1.2 and the public ip also changed for sure.

I think use SSH is kind of the best solution, and I actually do not quite know other solutions.

Pi -> Server -> PC