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. The CA Ping tool always fails for IPv6 addresses in Windows Server 2012 R2

The CA Ping tool always fails for IPv6 addresses in Windows Server 2012 R2

View products that this article applies to.

Symptoms

When you run the CA Ping diagnostic tool in Windows Server 2012 R2, it always fails for IPv6 addresses. 

This issue may lead you think that problems are in low-level networking. However, they could actually be in the application stack. 

↑ 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 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, 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 R2.

Registry information

To apply this hotfix, 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 RT 8.1, Windows 8.1, and Windows Server 2012 R2 file information notes
Important Windows 8.1 hotfixes 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:
    Version Product Milestone Service branch
    6.3.960 0.17 xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2 RTM GDR
  • 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 x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTime
Vmsif.dll6.3.9600.1711462,46403-May-201404:43
Vmsnetsetupplugin.dll6.3.9600.1638433,79222-Aug-201309:52
Vmswitch.sys6.3.9600.17114691,20003-May-201407:35
Vmsif.dll6.3.9600.1711462,46403-May-201404:43
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49
Vmswitch.sys6.3.9600.17114691,20003-May-201407:35
Mslbfoprovider.sys6.3.9600.17114115,71203-May-201407:38
Wnv.sys6.3.9600.17114705,53603-May-201407:35
Wnvapi.dll6.3.9600.1638461,95222-Aug-201309:53
Vmsif.dll6.3.9600.1711462,46403-May-201404:43
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49
Vmswitch.sys6.3.9600.17114691,20003-May-201407:35
Vmsif.dll6.3.9600.1711462,46403-May-201404:43
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49
Vmswitch.sys6.3.9600.17114691,20003-May-201407:35

↑ 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 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_3e3701fbba1402afab8125a8ef450fc6_31bf3856ad364e35_6.3.9600.17114_none_107e9f93c672f2be.manifest
File versionNot Applicable
File size695
Date (UTC)04-May-2014
Time (UTC)01:21
File nameAmd64_9801120f2600aa297b6d561f302abe23_31bf3856ad364e35_6.3.9600.17114_none_61a91841d4663392.manifest
File versionNot Applicable
File size725
Date (UTC)04-May-2014
Time (UTC)01:21
File nameAmd64_eadab165e56a69141ec8f3c00b07c495_31bf3856ad364e35_6.3.9600.17114_none_7b8075b3e2386210.manifest
File versionNot Applicable
File size708
Date (UTC)04-May-2014
Time (UTC)01:21
File nameAmd64_ff10f186f568824d1e94afb44a8548e5_31bf3856ad364e35_6.3.9600.17114_none_8671793fd47acab8.manifest
File versionNot Applicable
File size701
Date (UTC)04-May-2014
Time (UTC)01:21
File nameAmd64_microsoft-hyper-v-d..ch-coresystem-state_31bf3856ad364e35_6.3.9600.17114_none_e89fb6fc43577d70.manifest
File versionNot Applicable
File size10,075
Date (UTC)04-May-2014
Time (UTC)01:21
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.17114_none_5a152e6e53db4aa1.manifest
File versionNot Applicable
File size7,637
Date (UTC)04-May-2014
Time (UTC)01:21
File nameAmd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.17114_none_026df58fea8f3828.manifest
File versionNot Applicable
File size21,645
Date (UTC)03-May-2014
Time (UTC)12:17
File nameAmd64_microsoft-windows-wnv_31bf3856ad364e35_6.3.9600.17114_none_a0b00b892a829011.manifest
File versionNot Applicable
File size54,090
Date (UTC)04-May-2014
Time (UTC)01:21
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.17114_none_53ef8848c520c395.manifest
File versionNot Applicable
File size3,379
Date (UTC)04-May-2014
Time (UTC)01:21
File nameAmd64_wvms_pp_coresys.inf_31bf3856ad364e35_6.3.9600.17114_none_626d9b8b600fd3c4.manifest
File versionNot Applicable
File size3,411
Date (UTC)04-May-2014
Time (UTC)01:21

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2965735
Revision : 1
Created on : 1/7/2017
Published on : 6/10/2014
Exists online : False
Views : 217