Hi TechNet folks, We've an odd situation to resolve and it's becoming more and more embarassing: Base Info: Smart Card: .NET V2+ Card Middleware: Gemalto V5 Smart Card Management: CLM 2007 Internal Reader: Microsoft Usbccid Smart Card Reader External Reader: SCM SCR3310 Drivers are up to date. Issue Description: The internal readers on workstations do not work for him, he has to use an external reader to logon with his Smart Card. Gemalto is able to read the card while it's inserted in both readers, but the card does not work to logon and CLM is not able to read it when it's inserted into the internal reader. If we retire his card or give him a blank card and try to personalize it with in the internal reader, we get the following error "A communication error with the Smart Card has been detected." The issue happens to this user only, on every workstation, and no one else using the same machines. He already got three replacement cards and even a different computer. If we personalize the Smart Card using the external reader, to read it in CLM is the same thing, to unlock the workstation it either says the certificate is invalid or that it had a communication error. However, CLM Smart Card Logon certificate seems to be correctly applied to the personal store when the card is personalized. I'm almost deleting this guy's ID and recreating it from scratch but this is far from being the appropriate solution. Any help or idea would be greatly appreciated.

Hi, Please refer the following article to troubleshoot this issue: Authentication Return Values http://msdn.microsoft.com/en-us/library/windows/desktop/aa374738(v=vs.85).aspx in addition, please visit .net forum support to get a better anwser: http://forums.asp.net/ Hope this helps! Best Regards Elytis ChengElytis Cheng TechNet Community Support

This sounds like a case where the drivers for your internal reader are not correct. That, or your internal reader is defective - If you can do all actions with one of your readers and not the other, you have identified a problem with the failing reader. It has nothing to do with the operating system or CLM. Brian

New ID; New machine; New card; Issue resolved. Although the setup is exactly the same, system load and drivers the same, it works now. Thank you!