Event ID 27 — KDC Encryption Type Configuration
Updated: December 16, 2008
Applies To: Windows Server 2008 R2
Kerberos allows certain encryption types that can be used to encrypt Kerberos tickets. Other encryption types can be configured for Kerberos clients that do not support the default encryption types.
|Product:||Windows Operating System|
|Message:||While processing a TGS request for the target server %1, the account %2 did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of %3). The requested etypes were %4. The accounts available etypes were %5.|
Configure an available encryption type
Kerberos supports several encryption types that are used to encrypt the tickets. If you are using a non-Microsoft Kerberos client to request a ticket from a Windows-based Kerberos server, the Kerberos client must support the same encryption type. Use the event log message to determine the available encryption type and configure the Kerberos client accordingly.
To verify that the Kerberos client is configured with an available encryption type, 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:
- Log on to a Kerberos client computer within your domain.
- Click Start, point to All Programs, click Accessories, and then click Command Prompt.
- Type klist tickets, and then press ENTER.
- 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.
- Close the command prompt.