Symptoms
Consider the following scenario:
-
You have a Windows Server 2008 R2 Service Pack 1 (SP1)-based multi-homed Routing and Remote Access service (RRAS) server that has network address translation (NAT) configured.
-
You change the TCP or UDP mapping time-out value by using the netsh command.
-
You restart the remote access service or the computer.
In this scenario, the NAT functionality fails. Additionally, if you open the NAT properties, the mapping information no longer contains any values. Instead, the mappings are displayed as hyphens (-) where the values should be displayed.
Note To open the NAT properties, expand Routing and Remote Access in Server Manager, expand IPv4, and then right-click NAT.
Additionally, a SharedAccess_NAT sourced 32003 event may be logged in the System log.
Resolution
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 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=supportNote 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 2008 R2 Service Pack 1 (SP1).
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 2008 R2 file information notesImportant Windows 7 hotfixes and Windows Server 2008 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 7/Windows Server 2008 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.1.760
1.
22xxxWindows Server 2008 R2
SP1
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information Windows Server 2008 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 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Ipnat.sys |
6.1.7601.22319 |
116,224 |
08-May-2013 |
03:56 |
x64 |
For all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Ipnat.sys |
6.1.7601.22324 |
310,784 |
14-May-2013 |
03:26 |
IA-64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For information about the netsh command, see Netsh Routing IP NAT Context Commands.
See the terminology Microsoft uses to describe software updates.
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
|
File name |
Amd64_b5afd6b8cfa00a5c31b22a6b4bb09d3e_31bf3856ad364e35_6.1.7601.22319_none_624fd66f16e13558.manifest |
|
File version |
Not applicable |
|
File size |
697 |
|
Date (UTC) |
15-May-2013 |
|
Time (UTC) |
06:48 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-ipnat_31bf3856ad364e35_6.1.7601.22319_none_b9cc9ecaab14a712.manifest |
|
File version |
Not applicable |
|
File size |
2,972 |
|
Date (UTC) |
08-May-2013 |
|
Time (UTC) |
06:45 |
|
Platform |
Not applicable |
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
Ia64_c209fa6895dee6c274cd4bf532252c28_31bf3856ad364e35_6.1.7601.22324_none_f6a1bb6e331e840d.manifest |
|
File version |
Not applicable |
|
File size |
695 |
|
Date (UTC) |
15-May-2013 |
|
Time (UTC) |
06:48 |
|
Platform |
Not applicable |
|
File name |
Ia64_microsoft-windows-ipnat_31bf3856ad364e35_6.1.7601.22324_none_5d9fd5def2c1dc16.manifest |
|
File version |
Not applicable |
|
File size |
2,970 |
|
Date (UTC) |
14-May-2013 |
|
Time (UTC) |
05:15 |
|
Platform |
Not applicable |
