I have a Dymo LabelWriter Twin Turbo that used to work correctly with VirtualHere. Now when the printer is set to be used in the VH client, the printer will not appear in Device Manager/Devices and Printers as expected (Windows 10/Server 1607). Previously, the printer would simply appear as if just plugged in once set to auto-use the port and device. Now, nothing perceptible happens, other than the device going offline on the server machine.
All other virtualized devices seem to work without issue, as I have other server machines using a single Dymo each in the same manner. I have tried recreating the config file on the machine where the server software is running (hosting the Dymo printer) to no avail.
Another thing of note: When the USB hub auto-discovery takes place, there seem to be 2 instances of this specific server machine reporting as connected. There is only one specified server configured with that particular IP address, but it shows up twice in the connected hubs window. Any ideas on what I can do to get the Dymo Twin Turbo to properly reconnect?
.
Nothing related to virtualhere has changed so it must be something local to that VM image. Download and run this https://www.uwe-sieber.de/usbtreeview_e.html and see if the printer or an error appears under one of the ports under the VirtualHere USB 3 Extensible host controller section in the left pane.
It is appearing twice because you must have specified the ip address of the server (in USB Hubs->Specify Hubs) and also have Auto-Find on
No errors are reported and
No errors are reported and the VH USB Host Controller port for the device seems to be missing completely. I was able to connect the printer's host machine to a different network, and everything seemed to work just fine and I was able to manipulate the printer on the client machine and send a test print. However, returning the host machine to the original network causes the issue to come up again. I also gave the host machine a different IP address on the original network to rule that out but the issue persists. Nothing has changed with that network configuration; The device just doesn't seem to show up anymore unless the host machine is on a different network.
It's worth noting that there is other host machines sharing Dymo printers in exactly the same way on the same network without issue. Just this one for some reason doesn't want to cooperate.
I'm wondering if there is a way to clear out all references for just this device/port/windows hub so it can be "rediscovered" like a new machine. I want all of the other working VH devices left untouched if possible, to avoid the need to reconfigure everything to fix one problem device. Any other suggestions?
.
Have you purchased virtualhere? Because it won't connect if you run the client as a service with the server in trial mode.
No. The client is not running
No. The client is not running as a service. Only the server software on the machines hosting the devices. One device per machine, as per the trial allowance. I specifically asked you a while back via email if any licenses were required for this configuration and you provided the following response:
"Hi,
If you are just using one device connected to each virtualhere server you can use the trial. One client running on a windows print server can connect to all the virtualhere servers and the network and you can use the dymo printer. Note that is like plugging in the dymo printer into the server directly so it will become unavailable from where its physically plugged in. But you can stop using it from your print server and its available again from the place where its plugged in.
So there is no cost if you are just using one device per virtualhere server. Otherwise you need to purchase a license for each.
Regards,
Michael"
.
ok well this is not related to virtualhere there is something wrong with that VM install
Fair enough. I'm just trying
Fair enough. I'm just trying to understand how VH works a little better to try to track down the issue, and I couldn't find any relevant posts on the forum related to this problem. The VM was built specifically for this purpose (Windows Print Server utilizing VH to manage multiple Dymo printers) and hasn't been changed (except Windows Updates). The only thing that has apparently changed is VirtualHere no longer properly passes the device from the VH Server to the VH Client as expected.
I was hoping that you could provide some insight on what to do to resolve an issue when a device that once worked properly with VH, arbitrarily stops working.
Perhaps there is a file that I can view/edit/delete that has corrupted data that is preventing the device from being properly recognized in Windows?
I appreciate the help.
.
Normally for this sort of thing, i would suggest looking in device manager. If the device appears "Working Normally" in device manager when passed in via VirtualHere then its very likely some windows issue. I havent changed anything with virtualhere and if it suddenly stops working, it might be the driver of the actual printer or something that is no longer compatible with the windows update. So i then suggest going to the printer driver website and double checking there you have the latest and there are no issues reported on their forums (if they have them).
Another thing to try is to roll back recent windows updates and see if that resolves it.