eToken and RDP

Hi, all!

I’ve found this topic http://www.osronline.com/showthread.cfm?link=213631
And it’s really interesting for me, because I’m in the same situation.
I have an eToken which is on a server and when I try to connect through RDP or PCoIP to this server eToken Properties (application) doesn’t see the eToken device, but Windows do.
Under quick view, it looks like absolutely the same situation. I’m looking for the libraries which are involved in the process.

I’ll be glad for any helpful information.

This probably doesn’t help much, but we had so much trouble with eTokens, eAladdin, eToken support for Windows, and Windows support of eTokens that we gave up on them years ago. Not one thing ever worked smoothly, from VPN access to even just getting licenses renewed.

Ever try to put a corporate signing certificate on an eToken and use it with SignTool? Even the dev at MSFT couldn’t get it to work when he tried and said he’d look at it “when he had time.” (note: This was *several years ago*)

All the damn things did is drive us nuts. We tossed them and haven’t looked back.

Thanks for the opportunity to vent… Now we use SecurID and haven’t had even a moment’s trouble. Never realized VPN access could be so secure and so easy.

Peter
OSR

I’ve solved the problem by reverse and patching.