Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. L2TP connection fails with error 789 on a Windows Server 2012 R2-based RRAS server

L2TP connection fails with error 789 on a Windows Server 2012 R2-based RRAS server

View products that this article applies to.

This article describes an issue that occurs in a Windows Server 2012 R2-based Routing and Remote Access service (RRAS) server. A hotfix is available to fix this issue. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

Consider the following scenario:
  • You deploy DirectAccess and Layer Two Tunneling Protocol (L2TP) VPN connections in Windows Server 2012 R2.
  • An IP-HTTPS certificate from a public certification authority (CA) is installed.
  • A second certificate from an internal CA is installed for the L2TP/IPsec VPN connection.
In this scenario, the L2TP/IPsec VPN connection doesn't work, and you receive a 789 error code that looks something like this:

Error 789: The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.

↑ Back to the top

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

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

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

After you install this hotfix, the following registry subkey is configured:
HKLM\System\CurrentControlSet\Services\RemoteAccess\Parameters
Name: DoNotUpdateAuthCert
Type: REG_DWORD
Value: 0

To apply this hotfix, you have to change the value of the registry subkey to 1. Then, set the following registry subkey with the L2TP/IPsec certificate thumbprint:
HKLM\System\CurrentControlSet\Services\RemoteAccess\Parameters : ServerAuthCert

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.

↑ Back to the top

Status

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

↑ Back to the top

Cause

This issue occurs because DirectAccess populates the following registry subkey with the IP-HTTPS certificates hash during the configuration:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters : ServerAuthCert

↑ Back to the top

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.
Windows Server 2012 R2
Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.18xxxWindows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes aren't listed, are signed with a Microsoft digital signature.
x64 Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Raconfigtask.dll6.3.9600.18053547,32811-Sep-201523:44x86
Additional file information
x64 Windows Server 2012 R2
File propertyValue
File nameAmd64_460549fc224692e8189024ad47235fff_31bf3856ad364e35_6.3.9600.18053_none_16a64ae36a86d55b.manifest
File versionNot applicable
File size703
Date (UTC)11-Sep-2015
Time (UTC)23:46
PlatformNot applicable
File nameAmd64_db9cbc30bfdc15358d803b34720914f0_31bf3856ad364e35_6.3.9600.18053_none_d3a150e6ca39d600.manifest
File versionNot applicable
File size724
Date (UTC)11-Sep-2015
Time (UTC)23:46
PlatformNot applicable
File nameAmd64_microsoft-windows-r..donotupdateservauth_31bf3856ad364e35_6.3.9600.18053_none_62c2c9dce0d4fb41.manifest
File versionNot applicable
File size728
Date (UTC)11-Sep-2015
Time (UTC)15:44
PlatformNot applicable
File nameMsil_microsoft-windows-raconfigtask_31bf3856ad364e35_6.3.9600.18053_none_5d768727a693015c.manifest
File versionNot applicable
File size48,443
Date (UTC)11-Sep-2015
Time (UTC)23:46
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,103
Date (UTC)11-Sep-2015
Time (UTC)23:46
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbqfe, kbsurveynew, kbfix, kbautohotfix, kbhotfixserver, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 3093272
Revision : 1
Created on : 1/7/2017
Published on : 11/4/2015
Exists online : False
Views : 237