Support

Description

Support for VirtualHere hardware and software

UPS on QNAP

Forums

I've got a Cyberpower UPS connected via USB to my QNAP NAS. The QNAP built in software detects it as a valid UPS but I prefer to use the UPS USB connection shared out to a VM via VirtualHere. I'm wondering if ths built in software conflicts with it as the Cyberpower software is unable to detect the device even though I can successfully 'use' it from the Windows client but it shows up as just a 'USB input device'.

COM (serial-to-usb) device appears twice on Win7 device manager - only one instance working

Forums

Hi,

setup:
client - win7, vh 3.2.4
server - rpi2, vh 2.6.0, Prolific USB-to-serial device

Usually all works well, a single COM port appears on device manager on Win7.

Once in 2-3 days or so, I reach a case where the "COM" stops functioning.
Then, if selecting 'stop using' and the 'Auto-use port' on VH client, a second functional COM port is added to device manager.
(i.e. the 1'st 'non functioning' com port remains visible on the device manager list)

WiFi dongle stops working, Win7 client, error 10054 appears in vh log

Forums

Hello,

Setup:
client - win7, vh 3.2.4
server - rpi2, vh 2.6.0, Wifi dongle EW-7822 (note: USB3.0)

Usually all works well.
Once in 2-3 days of extensive usage, I reach a case where dongle stops working:
- On Win7 WiFi dialog, no networks are visible
- both Win7 and VH display the device, as usual. Then after restarting VH client, the device no longer displayed neither on VH or on Win7.

Are device addresses globally unique?

Forums

Let's say I have two identical servers (A & B), and I attach two identical devices (X & Y), one to each server, in the same ports.

"LIST"ing from the shell client, I would see something like:

Server A (1.2.3.4:7575)
--> Device X (ADDRESS_A_X)
Server B (5.6.7.8:7575)
--> Device Y (ADDRESS_B_Y)

Are ADDRESS_A_X and ADDRESS_B_Y the same in this case? Or are they guaranteed to be unique?

Error in SSL_accept after upgrading server and clients

Forums

Hi,

everything was working fine.
After upgrading the server and clients to the latest version I get the following error on one client:

Error in SSL_accept, error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

The certs and keys did not change. The certs are still valid.

Any idea?

vhusbdarmpi2 v2.5.5
VirtualHere USB Server for Raspberry Pi (Optimized build)

VirtualHere Client 3.1.9 starting (Compiled: Oct 16 2015 18:47:55)

Device driver not loading

Forums

Hello ,

I have running VirtualHere on a Raspberry Pi2 with different devices successful. But if we want use it with a "Fritz!Card USB V2.1" the driver where not installed successfully on Windows 7 32Bit and also 64Bit. We get an error "Code 10". The device is working directly at the computer without any Problems.

Any idea?

Thanks in advance