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. DirectAccess client receives incorrect response to reverse lookup query from a Windows Server 2012 R2-based DNS64 server

DirectAccess client receives incorrect response to reverse lookup query from a Windows Server 2012 R2-based DNS64 server

View products that this article applies to.

This article describes an issue in which client computers receive incorrect response to a reverse lookup query (PTR) from a Windows Server 2012 R2-based DNS64 server. Before you install this update, see the Prerequisites section.

↑ Back to the top

Symptoms

Assume that you have a DirectAccess client in the external network and an IPv4-only server in the internal network. The DirectAccess client knows a dynamically generated IPv6 address of the IPv4-only server. When the DirectAccess client sends DNS PTR queries to the DNS64 server that is used by DirectAccess to get the host name of the IPv4-only server, the response from the DNS64 server is incorrect (incomplete).  

↑ Back to the top

How to get this update

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

Method 1: Windows Update

This update is provided as a Recommended update on Windows Update. For more information about how to run Windows Update, see How to get an update through Windows Update.

Method 2: Microsoft Download Center

The following files are available for download from the Microsoft Download Center:

Operating systemUpdate
All supported x64-based versions of Windows Server 2012 R2Download Download the package now.


For more information about how to download Microsoft support files, select the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

↑ Back to the top

Update detail information

Prerequisites

To install this update, you should first install April 2014, update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) in Windows Server 2012 R2. 

Registry information

To apply this update, you don't have to make any changes to the registry.

Restart requirement

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

Update replacement information

This update doesn't replace a previously released update.

↑ 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

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables.
Windows Server 2012 R2
Notes
  • 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
    6.3.960 0.18 xxxWindows Server 2012 R2RTMGDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed 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.
x64 Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Adhapi.dll6.3.9600.1741523,04029-Oct-201401:27x64
Adhsvc.dll6.3.9600.1822877,82404-Feb-201616:39x64
Directaccessclientcomponents.psd1Not applicable1,07818-Jun-201314:56Not applicable
Httpprxm.dll6.3.9600.18228125,44004-Feb-201616:49x64
Httpprxp.dll6.3.9600.1822818,94404-Feb-201616:57x64
Iphlpsvc.dll6.3.9600.18229927,23205-Feb-201614:46x64
Iphlpsvcmigplugin.dll6.3.9600.1741571,68029-Oct-201402:03x64
Keepaliveprovider.dll6.3.9600.1741515,36029-Oct-201401:20x64
Msft_daclientexperienceconfiguration.cdxmlNot applicable8,06518-Jun-201314:56Not applicable
Msft_daclientexperienceconfiguration.format.ps1xmlNot applicable2,23718-Jun-201314:56Not applicable
Msft_daclientexperienceconfiguration.types.ps1xmlNot applicable68718-Jun-201314:56Not applicable
Msft_daconnectionstatus.cdxmlNot applicable2,35518-Jun-201314:56Not applicable
Msft_daconnectionstatus.format.ps1xmlNot applicable83218-Jun-201314:56Not applicable
Msft_daconnectionstatus.types.ps1xmlNot applicable1,04918-Jun-201314:56Not applicable
Msft_dasitetableentry.cdxmlNot applicable16,17618-Jun-201314:56Not applicable
Msft_dasitetableentry.format.ps1xmlNot applicable1,91018-Jun-201314:56Not applicable
Msft_dasitetableentry.types.ps1xmlNot applicable1,25018-Jun-201314:56Not applicable
Msft_ncsipolicyconfiguration.cdxmlNot applicable4,71918-Jun-201314:56Not applicable
Msft_ncsipolicyconfiguration.format.ps1xmlNot applicable1,34618-Jun-201314:56Not applicable
Msft_net6to4configuration.cdxmlNot applicable5,83618-Jun-201314:56Not applicable
Msft_net6to4configuration.format.ps1xmlNot applicable1,33118-Jun-201314:56Not applicable
Msft_net6to4configuration.types.ps1xmlNot applicable2,88718-Jun-201314:56Not applicable
Msft_netdnstransitionconfiguration.cdxmlNot applicable7,11118-Jun-201314:56Not applicable
Msft_netdnstransitionconfiguration.format.ps1xmlNot applicable1,87518-Jun-201314:56Not applicable
Msft_netdnstransitionconfiguration.types.ps1xmlNot applicable1,21418-Jun-201314:56Not applicable
Msft_netdnstransitionmonitoring.cdxmlNot applicable46018-Jun-201314:56Not applicable
Msft_netdnstransitionmonitoring.format.ps1xmlNot applicable1,49118-Jun-201314:56Not applicable
Msft_netiphttpsconfiguration.cdxmlNot applicable14,94118-Jun-201314:56Not applicable
Msft_netiphttpsconfiguration.format.ps1xmlNot applicable1,95818-Jun-201314:56Not applicable
Msft_netiphttpsconfiguration.types.ps1xmlNot applicable4,05418-Jun-201314:56Not applicable
Msft_netiphttpsstate.cdxmlNot applicable41318-Jun-201314:56Not applicable
Msft_netiphttpsstate.format.ps1xmlNot applicable93218-Jun-201314:56Not applicable
Msft_netisatapconfiguration.cdxmlNot applicable5,28718-Jun-201314:56Not applicable
Msft_netisatapconfiguration.format.ps1xmlNot applicable1,22818-Jun-201314:56Not applicable
Msft_netisatapconfiguration.types.ps1xmlNot applicable2,06318-Jun-201314:56Not applicable
Msft_netnattransitionconfiguration.cdxmlNot applicable7,73418-Jun-201314:56Not applicable
Msft_netnattransitionconfiguration.format.ps1xmlNot applicable1,82718-Jun-201314:56Not applicable
Msft_netnattransitionconfiguration.types.ps1xmlNot applicable2,25318-Jun-201314:56Not applicable
Msft_netnattransitionmonitoring.cdxmlNot applicable92718-Jun-201314:56Not applicable
Msft_netnattransitionmonitoring.format.ps1xmlNot applicable1,91818-Jun-201314:56Not applicable
Msft_netteredoconfiguration.cdxmlNot applicable7,06618-Jun-201314:56Not applicable
Msft_netteredoconfiguration.format.ps1xmlNot applicable1,54818-Jun-201314:56Not applicable
Msft_netteredoconfiguration.types.ps1xmlNot applicable1,18118-Jun-201314:56Not applicable
Msft_netteredostate.cdxmlNot applicable50018-Jun-201314:56Not applicable
Msft_netteredostate.format.ps1xmlNot applicable65718-Jun-201314:56Not applicable
Netdacim.dll6.3.9600.1741582,43229-Oct-201402:22x64
Netdacim.mofNot applicable7,37418-Jun-201314:56Not applicable
Netdacim_uninstall.mofNot applicable1,76618-Jun-201314:56Not applicable
Netnccim.dll6.3.9600.1741544,03229-Oct-201402:21x64
Netnccim.mofNot applicable4,61418-Jun-201314:56Not applicable
Netnccim_uninstall.mofNot applicable1,14818-Jun-201314:56Not applicable
Netttcim.dll6.3.9600.17415267,26429-Oct-201402:21x64
Netttcim.mofNot applicable60,23618-Jun-201314:56Not applicable
Netttcim_uninstall.mofNot applicable2,60218-Jun-201314:56Not applicable
Networkconnectivitystatus.psd1Not applicable75818-Jun-201314:56Not applicable
Networktransition.psd1Not applicable2,66918-Jun-201314:56Not applicable
Directaccessclientcomponents.psd1Not applicable1,07818-Jun-201312:28Not applicable
Iphlpsvcmigplugin.dll6.3.9600.1741559,90429-Oct-201401:28x86
Msft_daclientexperienceconfiguration.cdxmlNot applicable8,06518-Jun-201312:28Not applicable
Msft_daclientexperienceconfiguration.format.ps1xmlNot applicable2,23718-Jun-201312:28Not applicable
Msft_daclientexperienceconfiguration.types.ps1xmlNot applicable68718-Jun-201312:28Not applicable
Msft_daconnectionstatus.cdxmlNot applicable2,35518-Jun-201312:28Not applicable
Msft_daconnectionstatus.format.ps1xmlNot applicable83218-Jun-201312:28Not applicable
Msft_daconnectionstatus.types.ps1xmlNot applicable1,04918-Jun-201312:28Not applicable
Msft_dasitetableentry.cdxmlNot applicable16,17618-Jun-201312:28Not applicable
Msft_dasitetableentry.format.ps1xmlNot applicable1,91018-Jun-201312:28Not applicable
Msft_dasitetableentry.types.ps1xmlNot applicable1,25018-Jun-201312:28Not applicable
Msft_ncsipolicyconfiguration.cdxmlNot applicable4,71918-Jun-201312:28Not applicable
Msft_ncsipolicyconfiguration.format.ps1xmlNot applicable1,34618-Jun-201312:28Not applicable
Msft_net6to4configuration.cdxmlNot applicable5,83618-Jun-201312:28Not applicable
Msft_net6to4configuration.format.ps1xmlNot applicable1,33118-Jun-201312:28Not applicable
Msft_net6to4configuration.types.ps1xmlNot applicable2,88718-Jun-201312:28Not applicable
Msft_netdnstransitionconfiguration.cdxmlNot applicable7,11118-Jun-201312:28Not applicable
Msft_netdnstransitionconfiguration.format.ps1xmlNot applicable1,87518-Jun-201312:28Not applicable
Msft_netdnstransitionconfiguration.types.ps1xmlNot applicable1,21418-Jun-201312:28Not applicable
Msft_netdnstransitionmonitoring.cdxmlNot applicable46018-Jun-201312:28Not applicable
Msft_netdnstransitionmonitoring.format.ps1xmlNot applicable1,49118-Jun-201312:28Not applicable
Msft_netiphttpsconfiguration.cdxmlNot applicable14,94118-Jun-201312:28Not applicable
Msft_netiphttpsconfiguration.format.ps1xmlNot applicable1,95818-Jun-201312:28Not applicable
Msft_netiphttpsconfiguration.types.ps1xmlNot applicable4,05418-Jun-201312:28Not applicable
Msft_netiphttpsstate.cdxmlNot applicable41318-Jun-201312:28Not applicable
Msft_netiphttpsstate.format.ps1xmlNot applicable93218-Jun-201312:28Not applicable
Msft_netisatapconfiguration.cdxmlNot applicable5,28718-Jun-201312:28Not applicable
Msft_netisatapconfiguration.format.ps1xmlNot applicable1,22818-Jun-201312:28Not applicable
Msft_netisatapconfiguration.types.ps1xmlNot applicable2,06318-Jun-201312:28Not applicable
Msft_netnattransitionconfiguration.cdxmlNot applicable7,73418-Jun-201312:28Not applicable
Msft_netnattransitionconfiguration.format.ps1xmlNot applicable1,82718-Jun-201312:28Not applicable
Msft_netnattransitionconfiguration.types.ps1xmlNot applicable2,25318-Jun-201312:28Not applicable
Msft_netnattransitionmonitoring.cdxmlNot applicable92718-Jun-201312:28Not applicable
Msft_netnattransitionmonitoring.format.ps1xmlNot applicable1,91818-Jun-201312:28Not applicable
Msft_netteredoconfiguration.cdxmlNot applicable7,06618-Jun-201312:28Not applicable
Msft_netteredoconfiguration.format.ps1xmlNot applicable1,54818-Jun-201312:28Not applicable
Msft_netteredoconfiguration.types.ps1xmlNot applicable1,18118-Jun-201312:28Not applicable
Msft_netteredostate.cdxmlNot applicable50018-Jun-201312:28Not applicable
Msft_netteredostate.format.ps1xmlNot applicable65718-Jun-201312:28Not applicable
Networkconnectivitystatus.psd1Not applicable75818-Jun-201312:28Not applicable
Networktransition.psd1Not applicable2,66918-Jun-201312:28Not applicable
Additional file information
x64 Windows Server 2012 R2
File propertyValue
File nameAmd64_d5f7d4d8d1458708427d371c0b523f99_31bf3856ad364e35_6.3.9600.18229_none_ed762f4a06d49571.manifest
File versionNot applicable
File size720
Date (UTC)05-Feb-2016
Time (UTC)19:53
PlatformNot applicable
File nameAmd64_e1b2cc48b779658817a445c4caa150d4_31bf3856ad364e35_6.3.9600.18229_none_fdc15768eea55085.manifest
File versionNot applicable
File size720
Date (UTC)05-Feb-2016
Time (UTC)19:53
PlatformNot applicable
File nameAmd64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.3.9600.18229_none_02e72461501c7f42.manifest
File versionNot applicable
File size232,629
Date (UTC)05-Feb-2016
Time (UTC)20:00
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,723
Date (UTC)05-Feb-2016
Time (UTC)19:53
PlatformNot applicable
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.3.9600.18229_none_0d3bceb3847d413d.manifest
File versionNot applicable
File size216,352
Date (UTC)05-Feb-2016
Time (UTC)20:00
PlatformNot applicable

↑ Back to the top

Keywords: kbsurveynew, kbfix, kbexpertiseadvanced, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3139162
Revision : 2
Created on : 4/9/2020
Published on : 4/9/2020
Exists online : False
Views : 245