Support

Hello, I recently learned about the technology called USB over Ethernet, and I was considering applying it to the project I am currently developing, as it would be the ideal product for me.
However, the operation of the remotely connected USB Camera is very unstable in my current environment.
First of all, in the Windows 11 environment, it worked great as if it was directly connected, but in the Ubuntu environment (Client #2) that is scheduled to be configured in the project, the USB camera video and captured images appear broken.

Hello.
I want to start server on Mac OS and share iLoks, but if I trying to connect my dongles on clients (Mac), it shows an error "iLok Sharing Error". 
USB Hubs - D-Link DUB-H7 Rev. D
How to fix that?

phone : xiaomi redmi A3
usb Device: belkin INC001, Lemorele TC35L

First of all, the USB device is USB to Ethernet.

The phone recognizes the USB device. The evidence is that Internet tethering works through the USB device connected to the phone.

However, your VH server does not seem to recognize this device. For some reason, only 1000M-supporting devices are not recognized. The devices that have a problem with recognition do not generate a pop-up asking 'Allow VirtualHere to access 'device'?'.

Hello, I've tried searching and haven't really been able to find the answer. I have VH running on a small computer that is inside my laser, I can connect to the laser and see the camera. I can connect to the camera but it will not display in Lightburn. i used another USB over ip software and the camera functions as it should, so I'm not sure what the issue is or how I resolve it.

Thanks

Hello Michael,
This command seems broken, could you verify it please ?

Environment:

• Licensed : yes
• Server version : 4.7.2 (linux)
• Client version : 5.8.0 (windows)

I was trying to stop all active connections from a specific server, hence I launched virtualhere in admin mode (using -a flag) and tried those commands :

Hi Michael..

I have a request for update the server and client to support authentication using the Hardware id like bios serial number or motherboard sn as values $MACHINE_ID$  like get $CLIENT_HOSTNAME$  in the authentication script .

Like using edit the virtualhere client to get the bios serial number (wmic bios get serialnumber) and send it as $MACHINE_ID$ to virtualhere server ...

I have a situation where I want to run the virtual here server and client on the same raspberry pi.  That is, my devices are plugged into the USB ports on the Pi where the VH server is running and sometimes I want to access them from that machine and other times I want to access them remotely.  When I run the client on the server machine and claim one of the devices, the machine doesn't see the device.  Of course, if I don't run the client, the server sees the devices as natively plugged in.

Hi Michael.

We are, at the moment, migrating usb devices from an old virtualhere server to a new one.

We have about 69 usb devices on the old server, all of them with a customized name.

How can I migrate all of this usb devices to the new server maintaining the same name? Is there a database I can copy from the old server?

I've tried to copy the DeviceNicknames from the old config.ini file to the config.ini file on the new server but when I move a usb device from the old server to the new server it does not assume the its name from the old server.

Hi Michael,

We are running commands on the VirtualHere Windows client from a batch file. After running commands listed in https://www.virtualhere.com/client_configuration_faq, such as:

vhui64.exe -t "STOP USING,<server>.<port>"

We get the result (OK) in a small Windows dialog and have to press the dialog's "OK" button in order for the script to continue.

Hi!

We've been using VirtualHere (paid version) for years over LAN, but recently had to move the server to another location, breaking the existing networking. I'm trying to get it back online using EasyFind, but it's not working and I don't know how to debug further. I'm using Wireshark and seeing traffic on both the client and server to/from 143.198.145.150:443, but that's as far as I've gotten. Can you please let me know other settings or logs I can check?

Thanks,

Jake Levitt