IKEv2 VPN connection fails with error 13806 when you use an ECDSA certificate in Windows 8.1 or Windows Server 2012 R2

Applies to: Windows 8.1 EnterpriseWindows 8.1 ProWindows 8.1

This article describes an issue when you use a Elliptic Curve Digital Signature Algorithm (ECDSA) as a signature algorithmin Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2. The issue is resolved in update rollup 2962409, or in hotfix 2961892 that is described in this article and has a prerequisite.

Symptoms


Consider the following scenario:

  • You have a certification authority (CA) that meets Suite B standards (Elliptic Curve Cryptography), and the CA issues the computer certificates for Internet Protocol security (IPsec) authentication by using ECDSA as a signature algorithm.
  • You have Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2-based computers that request an IPSec certificate from the CA.
  • You configure an Internet Key Exchange version 2 (IKEv2) VPN on the client computer.
  • You enable the Allow machine certificate authentication for IKEv2setting on the server.
In this scenario, when you try to connect to the server by using the IKEv2 VPN from the client computer, the connection fails, and you receive the following error message:

Error 13806 - The server does not have a certificate installed that is suitable for use with IKEv2

Resolution


To resolve this issue, install update rollup 2962409, or install the hotfix that is described in this article.

Update information

For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
2962409  Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: June 2014

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must first install the update 2919355 on Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: June 2014

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates.

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_f1390b73e1fea7cff4279372c5e08a55_31bf3856ad364e35_6.3.9600.17111_none_cce9d94ae847d889.manifest
File versionNot applicable
File size704
Date (UTC)30-Apr-2014
Time (UTC)18:51
File nameX86_microsoft-windows-rasbase-agilevpn_31bf3856ad364e35_6.3.9600.17111_none_445ab3adb385305d.manifest
File versionNot applicable
File size4,262
Date (UTC)30-Apr-2014
Time (UTC)18:51
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_6da129ddb2abf1164d14d157416c0e1b_31bf3856ad364e35_6.3.9600.17111_none_e5908a9eb1d6ada6.manifest
File versionNot applicable
File size708
Date (UTC)30-Apr-2014
Time (UTC)19:33
File nameAmd64_microsoft-windows-rasbase-agilevpn_31bf3856ad364e35_6.3.9600.17111_none_a0794f316be2a193.manifest
File versionNot applicable
File size4,263
Date (UTC)30-Apr-2014
Time (UTC)12:37
Additional files for Windows RT 8.1
File propertyValue
File nameArm_9005bb2c306b7f2663646796d5ba4293_31bf3856ad364e35_6.3.9600.17111_none_2514e6bec914b538.manifest
File versionNot applicable
File size704
Date (UTC)30-Apr-2014
Time (UTC)18:51
File nameArm_microsoft-windows-rasbase-agilevpn_31bf3856ad364e35_6.3.9600.17111_none_445d2605b3824f23.manifest
File versionNot applicable
File size4,262
Date (UTC)30-Apr-2014
Time (UTC)18:51