매뉴얼 & 다운로드 Show
제품 지원온라인 상담
전화 상담
방문 상담
Yes I am thanks. More info for you: I have inserted a card and I see the following in Device manager: Also, under 'Disk Drives' I see 'HP USB20 HS-COMBO USB Device' which reveals drivers as in attached screen shot: so Win 10 is providing the driver(s) ? The next question is, if the slot stops working again, what do I need to do as I get no reaction from the computer of course and these items do not appear in Device manager and there is nothing in msinfo to show there is any problem? Thank you for your assistance so far. About Lenovo
Shop
Support
Resources
© Lenovo. Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Smart Card Troubleshooting
In this articleThis article explains tools and services that smart card developers can use to help identify certificate issues with the smart card deployment. Debugging and tracing smart card issues requires a variety of tools and approaches. The following sections provide guidance about tools and approaches you can use.
CertutilFor a complete description of Certutil including examples that show how to use it, see Certutil [W2012]. List certificates available on the smart cardTo list certificates that are available on the smart card, type Note Entering a PIN is not required for this operation. You can press ESC if you are prompted for a PIN. Delete certificates on the smart cardEach certificate is enclosed in a container. When you delete a certificate on the smart card, you're deleting the container for the certificate. To find the container value, type To delete a container, type certutil -delkey -csp "Microsoft Base Smart Card Crypto Provider" "<ContainerValue>". Debugging and tracing using WPPWPP simplifies tracing the operation of the trace provider. It provides a mechanism for the trace provider to log real-time binary messages. Logged messages can be converted to a human-readable trace of the operation. For more information, see Diagnostics with WPP - The NDIS blog. Enable the traceUsing WPP, use one of the following commands to enable tracing:
You can use the parameters in the following table.
Examples To enable tracing for the SCardSvr service:
To enable tracing for scfilter.sys:
Stop the traceUsing WPP, use one of the following commands to stop the tracing:
ExamplesTo stop a trace:
Kerberos protocol, KDC, and NTLM debugging and tracingYou can use these resources to troubleshoot these protocols and the KDC:
To begin tracing, you can use NTLMTo enable tracing for NTLM authentication, run the following command on the command line:
To stop tracing for NTLM authentication, run this command:
Kerberos authenticationTo enable tracing for Kerberos authentication, run this command:
To stop tracing for Kerberos authentication, run this command:
KDCTo enable tracing for the KDC, run the following command on the command line:
To stop tracing for the KDC, run the following command on the command line:
To stop tracing from a remote computer, run this command: logman.exe -s <ComputerName>. Note The default location for logman.exe is %systemroot%system32\. Use the -s option to supply a computer name. Configure tracing with the registryYou can also configure tracing by editing the Kerberos registry values shown in the following table.
If you used If you used the registry key settings shown in the previous table, look for the trace log files in the following locations:
To decode event trace files, you can use Smart Card serviceThe smart card resource manager service runs in the context of a local service. It's implemented as a shared service of the services host (svchost) process. To check if Smart Card service is running
To restart Smart Card service
You can use the following command at the command prompt to check whether the service is running: The following code sample is an example output from this command:
Smart card readersAs with any device connected to a computer, Device Manager can be used to view properties and begin the debug process. To check if smart card reader is working
Note If the smart card reader is not listed in Device Manager, in the Action menu, select Scan for hardware changes. CryptoAPI 2.0 DiagnosticsCryptoAPI 2.0 Diagnostics is available in Windows versions that support CryptoAPI 2.0 and can help you troubleshoot public key infrastructure (PKI) issues. CryptoAPI 2.0 Diagnostics logs events in the Windows event log. The logs contain detailed information about certificate chain validation, certificate store operations, and signature verification. This information makes it easier to identify the causes of issues and reduces the time required for diagnosis. For more information about CryptoAPI 2.0 Diagnostics, see Troubleshooting an Enterprise PKI. See alsoSmart Card Technical Reference FeedbackSubmit and view feedback for |