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.

A virtual machine that is configured to use the DLC protocol does not connect to an SNA host on Hyper-V Server 2012 or Hyper-V Server 2012 R2


View products that this article applies to.

Symptoms

You use Microsoft Hyper-V Server 2012 or Microsoft Hyper-V Server 2012 R2 to host a virtual machine such as for Microsoft Host Integration Server 2009. If the virtual machine is configured to use the Data Link Control (DLC) protocol to connect to a Systems Network Architecture (SNA) host such as an IBM Mainframe z/OS system, the connection fails.

↑ Back to the top


Cause

This problem occurs because Hyper-V Server 2012 and Hyper-V Server 2012 R2 do not support 802.3 frame types that do not have a Sub-Network Access Protocol (SNAP) header.

↑ 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: 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 have the following installed:
  • Microsoft Hyper-V Server 2012 or Microsoft Hyper-V Server 2012 R2
  • Windows Server 2012 or Windows Server 2012 R2

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

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 file information and notes

Important Windows 8 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.16 xxxWindows Server 2012RTMGDR
  • 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
Vmsif.dll6.2.9200.1638462,46422-Aug-201309:34x64
Vmsnetsetupplugin.dll6.2.9200.1638433,79222-Aug-201309:52x64
Vmswitch.sys6.2.9200.16455686,08004-Nov-201314:42x64
Vmsif.dll6.2.9200.1638462,46422-Aug-201309:34x64
Vmsntfy.dll6.2.9200.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.2.9200.16455686,08004-Nov-201314:42x64
Mslbfoprovider.sys6.2.9200.16423115,71208-Oct-201307:38x64
Wnv.sys6.2.9200.16423705,02408-Oct-201307:36x64
Wnvapi.dll6.2.9200.1638461,95222-Aug-201309:53x64
Vmsif.dll6.2.9200.1638462,46422-Aug-201309:34x64
Vmsntfy.dll6.2.9200.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.2.9200.16455686,08004-Nov-201314:42x64
Vmsif.dll6.2.9200.1638462,46422-Aug-201309:34x64
Vmsntfy.dll6.2.9200.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.2.9200.16455686,08004-Nov-201314:42x64

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 Blue RTM" 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 Blue RTM" 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.16 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 sizeDateTimePlatform
Vmsif.dll6.3.9600.1638462,46422-Aug-201309:34x64
Vmsnetsetupplugin.dll6.3.9600.1638433,79222-Aug-201309:52x64
Vmswitch.sys6.3.9600.16455686,08004-Nov-201314:42x64
Vmsif.dll6.3.9600.1638462,46422-Aug-201309:34x64
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.3.9600.16455686,08004-Nov-201314:42x64
Mslbfoprovider.sys6.3.9600.16423115,71208-Oct-201307:38x64
Wnv.sys6.3.9600.16423705,02408-Oct-201307:36x64
Wnvapi.dll6.3.9600.1638461,95222-Aug-201309:53x64
Vmsif.dll6.3.9600.1638462,46422-Aug-201309:34x64
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.3.9600.16455686,08004-Nov-201314:42x64
Vmsif.dll6.3.9600.1638462,46422-Aug-201309:34x64
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.3.9600.16455686,08004-Nov-201314:42x64

↑ 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


Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_0b4fc84dea5792e29a4cf05eb3e8c5db_31bf3856ad364e35_6.3.9600.16455_none_b78aa1aa7e19601a.manifest
File versionNot Applicable
File size695
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_6f380143bfa5e960cd7f432ca77f906c_31bf3856ad364e35_6.3.9600.16455_none_243066685e60888a.manifest
File versionNot Applicable
File size725
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_853d86a411b564995f5b07226db4389e_31bf3856ad364e35_6.3.9600.16455_none_bdc45f30146a5852.manifest
File versionNot Applicable
File size701
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_cf8dce77c0319e5eccd5d8e1a0e210bd_31bf3856ad364e35_6.3.9600.16455_none_398c33059703f1a2.manifest
File versionNot Applicable
File size708
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-hyper-v-d..ch-coresystem-state_31bf3856ad364e35_6.3.9600.16455_none_e87594104376e45f.manifest
File versionNot Applicable
File size10,075
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.16455_none_59eb0b8253fab190.manifest
File versionNot Applicable
File size7,637
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.16455_none_0243d2a3eaae9f17.manifest
File versionNot Applicable
File size21,660
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-windows-wnv_31bf3856ad364e35_6.3.9600.16455_none_a085e89d2aa1f700.manifest
File versionNot Applicable
File size54,090
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.16455_none_53c5655cc5402a84.manifest
File versionNot Applicable
File size3,379
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_wvms_pp_coresys.inf_31bf3856ad364e35_6.3.9600.16455_none_6243789f602f3ab3.manifest
File versionNot Applicable
File size3,411
Date (UTC)05-Nov-2013
Time (UTC)22:52
SHA-1 hashNot Applicable
MD5 hashNot Applicable

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_0b4fc84dea5792e29a4cf05eb3e8c5db_31bf3856ad364e35_6.3.9600.16455_none_b78aa1aa7e19601a.manifest
File versionNot Applicable
File size695
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File nameAmd64_6f380143bfa5e960cd7f432ca77f906c_31bf3856ad364e35_6.3.9600.16455_none_243066685e60888a.manifest
File versionNot Applicable
File size725
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File nameAmd64_853d86a411b564995f5b07226db4389e_31bf3856ad364e35_6.3.9600.16455_none_bdc45f30146a5852.manifest
File versionNot Applicable
File size701
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File nameAmd64_cf8dce77c0319e5eccd5d8e1a0e210bd_31bf3856ad364e35_6.3.9600.16455_none_398c33059703f1a2.manifest
File versionNot Applicable
File size708
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File nameAmd64_microsoft-hyper-v-d..ch-coresystem-state_31bf3856ad364e35_6.3.9600.16455_none_e87594104376e45f.manifest
File versionNot Applicable
File size10,075
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.16455_none_59eb0b8253fab190.manifest
File versionNot Applicable
File size7,637
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File nameAmd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.16455_none_0243d2a3eaae9f17.manifest
File versionNot Applicable
File size21,660
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File nameAmd64_microsoft-windows-wnv_31bf3856ad364e35_6.3.9600.16455_none_a085e89d2aa1f700.manifest
File versionNot Applicable
File size54,090
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.16455_none_53c5655cc5402a84.manifest
File versionNot Applicable
File size3,379
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File nameAmd64_wvms_pp_coresys.inf_31bf3856ad364e35_6.3.9600.16455_none_6243789f602f3ab3.manifest
File versionNot Applicable
File size3,411
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File namePackage_1_for_kb2902821~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,304
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File namePackage_2_for_kb2902821~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,908
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File namePackage_3_for_kb2902821~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,004
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File namePackage_4_for_kb2902821~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,873
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File namePackage_5_for_kb2902821~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,847
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File namePackage_6_for_kb2902821~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,074
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable
File namePackage_for_kb2902821_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size4,858
Date (UTC)05-Nov-2013
Time (UTC)22:52
PlatformNot Applicable

↑ Back to the top


References

See the terminology  that Microsoft uses to describe software updates for more information.

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2902821
Revision : 1
Created on : 1/7/2017
Published on : 2/10/2014
Exists online : False
Views : 321