Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 954
  • Last Modified:

How to acces a smart card reader connected to a Windows 2003 server

HI Expert,

I developed and installed a java application on a Windows 2003 Server machine. For security puporse , this application has to access a smart card inserted in a reader which is itself connected to the server.

The problem is that the application is not seeing any smart card reader.

The reader is Omnikey CardMan 6121. The smart card device redirection is disabled.

Furthermore i tried to access the reader using the Diagnostic tools (installed on the server) provided by Omnikey. The Diagnostic tools behave as if there was no reader connected to the server machine (just as the java application).

When I enable the smart card device redirection, both my application and the card dignostic tools are able to acces the smart card reader connected to the TERMINAL but not the one directly connected to the SERVER.

How could I actually access the smart card reader connected to the windows 2003 server machine?

Thanks.

0
bricesime
Asked:
bricesime
  • 3
1 Solution
 
ParanormasticCryptographic EngineerCommented:
Make sure you have the current versions of the drivers and diag software - the cd might be out of date... also make sure correct version of 32 bit vs. 64 OS.

http://www.omnikey.com/index.php?id=69

If that doesn't help, check device manager and make sure no ! exist.

There is a good chance that you will need to reboot after installing this driver - its been a couple years but that was the case then.  Hopefully they managed to fix that by now.

If you are trying to test multiple readers, remove/uninstall any competing products.  Test with this being the only installed reader.

Try another USB port - try on in the back if you aren't already to make sure is a powered USB.  Do not use a non-powered up, especially with multiple devices.

Sorry, a little rusty on this one for remembering this model exactly vs. the other half dozen vendors' readers I used to test with, so if it doesn't make sense I apologize - in device manager see if there might be multiple virtual readers present - if so, remove all except one and then insert device.

Check services.msc and verify Smart Card service is present and started.

Since a server, I am assuming no software firewalls that might be hindering, but just throwing it out there in case.
0
 
ParanormasticCryptographic EngineerCommented:
Also, have you tried this while logged in locally instead of through RDP?  You can also try using Remote Desktops MMC and when creating the connection make sure to check the 'connect to console' box and see if that acts differently than normal RDP connection.

If you are trying to read from the locally connected device and not from remote users at all, then you should look at the middleware - are you using a product along with this device for handling the certificates, doing SSO, etc.?  There may be a vendor created service for handling the remote connections and disabling that might help out.  If not, you might try talking to the middleware company to see what permutations they support and if there is anything special you need to do that is specific to their product.
0
 
ParanormasticCryptographic EngineerCommented:
Usually this type of situation is resolved either by troubleshooting, as described above, or else it is an issue with either the reader driver, reader firmware, or the smartcard middleware.  If troubleshooting did not solve it - problem tickets should be opened both the the middleware vendor and Omnikey.  If neither of them will accept the issue (blaming the other) then you should get them on a conference call or shared email chain so they can work with each other on the issue instead of trying to pass it off.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now