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. IPv6 address of a DirectAccess server binds to the wrong network interface in Windows Server 2012

IPv6 address of a DirectAccess server binds to the wrong network interface in Windows Server 2012

View products that this article applies to.

Symptoms

Consider the following scenario:
  • External load balancing is enabled on a Windows Server 2012-based DirectAccess server in a network environment.
  • The network environment contains some IP version 4 (IPv4)-only intranet resources.
  • You use DNS64 to synthesize IPv6 addresses from the IPv4 addresses to reach internal IPv4 resources.
In this scenario, a DNS64 IPv6 address binds to the wrong network interface. Therefore, DNS64 does not function as expected.

More specifically, when you run the following cmdlet, DNS64 displays "Loopback Pseudo-Interface" as the interface name in the AcceptInterface field:
Get-NetDnsTransitionConfiguration
However, when you run the following command to view the status of the IPv6 addresses, the DNS64 address (prefix:3333::1) is not bound to the Loopback Pseudo-Interface interface:
netsh int ipv6 show address


Notes
  • The expected behavior is that the IPv6 address binds to the loopback interface.
  • DNS64 is a mechanism that synthesizes AAAA records (IPv6 address records) from A records (address records).
  • After you enable external load balancing, DNS64 accepts a loopback interface.

↑ Back to the top

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 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 be running Windows Server 2012.

Registry information

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

Restart requirement

You must 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 Server 2012 file information notes
Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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" 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.2.920 0.20 xxxWindows Server 2012RTMLDR
  • 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" 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
File nameFile versionFile sizeDateTimePlatform
Raconfigtask.dll6.2.9200.20737546,81606-Jun-201309:14x86

↑ Back to the top

Workaround

To work around the issue, you can manually move the DNS64 IPv6 address from the incorrect network interface to the loopback interface. To do this, follow these steps:
  1. Run the following command to obtain the necessary interface index information:
    netsh int ipv6 show int
  2. Run the following command to remove the DNS64 IPv6 address from the physical network interface: 
    netsh int ipv6 delete address  <physical network interface index> <ipv6 address>
  3. Run the following command to bind the DNS64 IPv6 address to the loopback interface:
    netsh int ipv6 add address  <loopback interface index> <ipv6 address> /128
  4. Run the following command to verify the changes:
    netsh int ipv6 show address
    Note The DNS64 IPv6 address should be bound to the loopback interface.
  5. Restart the computer.

↑ 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

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_a4edff6a6869fb967adb786d99bc5990_31bf3856ad364e35_6.2.9200.20737_none_cdca22ad9258947f.manifest
File versionNot applicable
File size703
Date (UTC)06-Jun-2013
Time (UTC)18:37
PlatformNot applicable
File nameMsil_microsoft-windows-raconfigtask_31bf3856ad364e35_6.2.9200.20737_none_c62545407569b9cb.manifest
File versionNot applicable
File size48,776
Date (UTC)06-Jun-2013
Time (UTC)09:25
PlatformNot applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2859347
Revision : 1
Created on : 1/7/2017
Published on : 9/27/2013
Exists online : False
Views : 266