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. A connection request fails for some NAT instances in Windows Server 2012 R2

A connection request fails for some NAT instances in Windows Server 2012 R2

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2012 R2.
  • You create several network address translation (NAT) instances. For example, you create NAT instance A, NAT instance B, and NAT instance C.
  • You remove NAT instance B.
  • You try to connect to an internal virtual machine for tenant C from outside the environment by using a static mapping port such as RDP.

In this scenario, the connect request fails.

↑ Back to the top

Cause

This problem occurs because there is an issue in the NAT instance look-up logic.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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, go to 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 be running Windows Server 2012 R2.

Additionally, you must first install update 2919355 on Windows 8.1 or Windows Server 2012 R2.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

File information
The English (United States) 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 Server 2012 R2 file information and notes

Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" 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.17 xxxWindows 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 for Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimeHashes
Winnat.sys6.3.9600.17055172,54419-Mar-201408:07

Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_cfc6cd2903f8f5e81b5207b0d1546d3f_31bf3856ad364e35_6.3.9600.17055_none_dfd8e237e5493d0a.manifest
File versionNot applicable
File size698
Date (UTC)19-Mar-2014
Time (UTC)18:48
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-winnat_31bf3856ad364e35_6.3.9600.17055_none_a78382837019b611.manifest
File versionNot applicable
File size71,119
Date (UTC)19-Mar-2014
Time (UTC)13:58
SHA-1 hashNot applicable
MD5 hashNot 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

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2953218
Revision : 1
Created on : 1/7/2017
Published on : 5/20/2014
Exists online : False
Views : 177