| Event Id | 13 |
| Source | Microsoft-Windows-Security-Kerberos |
| Description | While using your smartcard for the Credential Manager the Kerberos subsystem encountered an error that appears to be from a missing or incorrect smartcard PIN. To remedy, launch the Stored User Names and Passwords control panel applet, and reenter the pin for the credential for %1%2%3. |
| Event Information | According to Microsoft : Cause This event is logged when using your smartcard for the Credential Manager the Kerberos subsystem encountered an error that appears to be from a missing or incorrect smartcard PIN. Resolution Change the stored PIN If your personal identification number (PIN) has changed and is stored on the local computer, you must change the stored PIN to the new PIN. You can change the stored PIN by using Stored User Names and Passwords. To change the stored PIN by using Stored User Names and Passwords: 1.Click Start, and then click Control Panel. 2.Double-click User Accounts. 3.Click Manage User Accounts. 4.If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. 5.Click the Advanced tab, and then click Manage Passwords. 6.In the Stored User Names and Passwords dialog box, click the appropriate user account, and then click Edit. 7.In the Password box, type the correct PIN, and then click OK. 8.Click Close. Verify To verify that the Kerberos client is correctly configured, you should ensure that a Kerberos ticket was received from the Key Distribution Center (KDC) and cached on the local computer. You can view cached Kerberos tickets on the local computer by using the Klist command-line tool. Note: Klist.exe is not included with Windows Vista, Windows Server 2003, Windows XP, or Windows 2000. You must download and install the Windows Server Resource Kit before you can use Klist.exe. To view cached Kerberos tickets by using Klist: 1.Log on to the Kerberos client computer. 2.Click Start, point to All Programs, click Accessories, and then click Command Prompt. 3.Type klist tickets, and then press ENTER. 4.Verify that a cached Kerberos ticket is available. Ensure that the Client field displays the client on which you are running Klist. Ensure that the Server field displays the domain in which you are connecting. 5.Close the command prompt. |
| Reference Links | Event ID 13 from Microsoft-Windows-Security-Kerberos |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.