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. VPN gateway becomes unresponsive and a connection can't be established in Windows Server 2012 R2

VPN gateway becomes unresponsive and a connection can't be established in Windows Server 2012 R2

View products that this article applies to.

This article describes virtual private network (VPN)-related issues that occur in Windows Server 2012 R2. A hotfix is available to resolve these issues. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

On a computer that's running Windows Server 2012 R2, you may encounter one of the following issues.

Issue 1

A memory leak reduces the system memory in the Routing and Remote Access Service (RRAS) gateway. Therefore, the VPN gateway becomes unresponsive and does not provide site-to-site VPN services.  

Issue 2

Assume that you install NDIS 5.x VPN client software on Windows Server 2012 R2. When you try to connect to the VPN server through the VPN client software, the VPN connection can't be established. Additionally, and you can't access your internal resources.

↑ Back to the top

Resolution

To resolve these issues, install the following hotfix. Even though these issues have been observed only in Windows Server 2012 R2, the hotfix also applies to Windows 8.1 and Windows RT 8.1. 

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

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:
http://support.microsoft.com/contactus/?ws=support
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 have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

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

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8.1 and Windows Server 2012 R2 file information and notes

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.17xxxWindows RT 8.1, Windows 8.1, and Windows 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 are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Ndiswan.sys6.3.9600.17793167,93608-Apr-201503:01x86
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Ndiswan.sys6.3.9600.17793205,82408-Apr-201504:28x64
For all supported Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Ndiswan.sys6.3.9600.17793144,38408-Apr-201501:48Not applicable

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_2702a00ab17975246d405f592d571bbd_31bf3856ad364e35_6.3.9600.17794_none_a005167a717ee1b1.manifest
File versionNot applicable
File size703
Date (UTC)10-Apr-2015
Time (UTC)16:27
PlatformNot applicable
File nameX86_microsoft-windows-rasbase-ndiswan_31bf3856ad364e35_6.3.9600.17794_none_87cd762c72ec87ba.manifest
File versionNot applicable
File size7,684
Date (UTC)08-Apr-2015
Time (UTC)23:14
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_2ce8018dd0311002a40d71635419a9f6_31bf3856ad364e35_6.3.9600.17794_none_7e31fadaa43e9a9e.manifest
File versionNot applicable
File size707
Date (UTC)10-Apr-2015
Time (UTC)16:28
PlatformNot applicable
File nameAmd64_microsoft-windows-rasbase-ndiswan_31bf3856ad364e35_6.3.9600.17794_none_e3ec11b02b49f8f0.manifest
File versionNot applicable
File size7,688
Date (UTC)08-Apr-2015
Time (UTC)23:21
PlatformNot applicable
Additional files for all supported Windows RT 8.1
File propertyValue
File nameArm_f141e7877e0857cc3cdd52e74e20b3af_31bf3856ad364e35_6.3.9600.17794_none_5a0cc6c11ea5a308.manifest
File versionNot applicable
File size703
Date (UTC)10-Apr-2015
Time (UTC)16:27
PlatformNot applicable
File nameArm_microsoft-windows-rasbase-ndiswan_31bf3856ad364e35_6.3.9600.17794_none_87cfe88472e9a680.manifest
File versionNot applicable
File size7,684
Date (UTC)08-Apr-2015
Time (UTC)23:03
PlatformNot applicable

↑ 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

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 3046798
Revision : 1
Created on : 1/7/2017
Published on : 5/12/2015
Exists online : False
Views : 239