Issue with card reader

Hello!

I am using VirtualHere version 3.5.0 for Windows.
When I start vhui, I can see my card reader and I can click on 'Use' and then in 'Devise Manager' I can see smart car Gemalto and smart card reader. The issue is that when I am starting application which requires this card and try to login, I get error information that there is no card.
What can I do?

Thank you in advance,
Joanna.

#2

I am testing that on a VirtualMachine.

#3

Are you using windows 10? If not you should try on win10 as that uses the new virtualhere driver that is more compatible with smartcard readers like the gemalto

#5

OK if possible try on win 10, if you are in a vm it should be pretty easy to setup

Hey again!
I have tried on Windows 10 virtualbox and it did not help. What else I could try?
Thank you in advance.

In reply to by joanna_malysa

#8

OK i did a search and found this: https://www.virtualhere.com/node/546 from last year (he is using a gemalto)

His worked once and he was using a pi. Are you using a pi for the virtualhere server?

I never did find out if it got fully working. However i suspect these dongles cant be used by one computer and reused on another without replugging, just like the iLok.

Is is possible your server is interacting with the gemalto dongle before its given to virtualhere for remote access, perhaps that is using up the "one-plug" limit?

In reply to by Michael

#9

We are not using pi for the virtualhere server. We are using a native running debian. It is not being virtualized.
But maybe the issue is with USB.

Thanks for help.

OK, when you plug the gemalto into your debian server, watch the syslog and see if any driver is bound to that device. If so then disable that debian driver and it may then work via virtualhere

Thats from logs:

Mar 9 10:57:17 virtualhere vhusbdx86_64: Unmanaging device 121112
Mar 9 10:57:17 virtualhere vhusbdx86_64: Warning, unbinding device at /sys//devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2.1/1-2.1.1/1-2.1.1.1/1-2.1.1.1.2 with 1 outstanding in-flight URBs
Mar 9 10:57:18 virtualhere kernel: [163910.646644] usb 1-2.1.1.1.2: new full-speed USB device number 108 using ehci-pci
Mar 9 10:57:18 virtualhere kernel: [163910.757444] usb 1-2.1.1.1.2: New USB device found, idVendor=0529, idProduct=0620
Mar 9 10:57:18 virtualhere kernel: [163910.757459] usb 1-2.1.1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 9 10:57:18 virtualhere kernel: [163910.757469] usb 1-2.1.1.1.2: Product: Token JC
Mar 9 10:57:18 virtualhere kernel: [163910.757477] usb 1-2.1.1.1.2: Manufacturer: Aladdin
Mar 9 10:57:18 virtualhere vhusbdx86_64: Found Full speed device [0529:0620] "Aladdin, Token JC" at address 121112
Mar 9 11:01:32 virtualhere vhusbdx86_64: 10.3.101.104 connected
Mar 9 11:01:48 virtualhere kernel: [164180.669993] usb 1-2.1.1.1.2: reset full-speed USB device number 108 using ehci-pci
Mar 9 11:01:48 virtualhere vhusbdx86_64: Device 121112 BOUND to connection 40
Mar 9 11:06:07 virtualhere vhusbdx86_64: Device 121112 UNBOUND from connection 40

In reply to by joanna_malysa

#12

OK, it doesnt seem to be loading a driver server side so i think we can assume the token is not being interacted with locally on the server so i dont know what the problem is, it looks like this particular token wont work with virtualhere for some unknown reason.

You are definately using the latest token drivers on the client side? I have had customers with a not working token via virtualhere (different brand) and updating to latest token drivers gets it working...

In reply to by Michael

#13

Yes, I have checked that. So its token fault.
I will find another way. Thanks again.

#14

Hi Michael, thx for your product.
I activated my license and have a working link between Omega Onion.io server (OpenWRT binary) with expansion dock and Windows 10 Pro running into a Virtualbox on a debian host at OVH.
When I put a USB stick, it's not that fast but it works listing the directory.
When I connect my ARC38u (same with HMC) it shows in My Computer; when I put my Belgian eID smartcard it shows the card; driver is successfully displayed in the reader's propoerties. Nevertheless the reader is not recognized by calling applications (.Net nor Java).
Any ideas ?
Kr,
Hervé

#15

Is it using libusb to interact between java and the card? and if so what version of libusb