Support

Description

Support for VirtualHere hardware and software

Linux console client, use device and homonyms

Forums

<p>Hello,
</p>
<p>If we have read properly the client documentation, connecting to a device is made by<br />
'vhclient -t use,<device address>', the address being taken through 'vhclient -t list'.
</p>
<p>We have homonyms in the client list (from different VH servers) :
</p>
<p>Server 1<br />
--> device A (raspberrypi.112)<br />
--> device B (raspberrypi.114)<br />
Server 2<br />

How VirtualHere communicates via the Network

Forums

VirtualHere essentially takes the USB signals from a USB device and converts those signals into data packets that are sent over an IP network to a remote client. The USB signals are then recreated on the remote client transparently, giving the effect of direct access to a remote USB device. Once the USB signal is captured by the VirtualHere server it is converted to data packets and sent out to clients via one (or more) of the methods described here:


TCP

User name not showing (In use by at MYPC)

Forums

The user name is not showing in the client (4.6.7).

This occurs when on the local network and when connected remotely via a VPN (windows client).

I tried my Mac client via the VPN and it doesn't find any hubs at all (but that's probably a different issue). I haven't tried the Mac client on the local network.

The changelog claims the issue was fixed in 4.6.6, so it may be a regression in 4.6.7 or maybe it's not completely fixed. Also it might be a Windows 10 thing?

I have a screenshot. How do I attach it to the support discussion?