Home

Incomplete DHCP/PXE/TFTP reply from VMs in Hyper-V 2019 with NIC Teaming Adapter bound to vSwitch

%3CLINGO-SUB%20id%3D%22lingo-sub-303416%22%20slang%3D%22en-US%22%3EIncomplete%20DHCP%2FPXE%2FTFTP%20reply%20from%20VMs%20in%20Hyper-V%202019%20with%20NIC%20Teaming%20Adapter%20bound%20to%20vSwitch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-303416%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22messageSidebar%22%3E%3CDIV%20class%3D%22votinglabel%22%3EWe%20have%20a%204%20node%20Hyper-V%20Cluster%20running%20under%20Windows%20Server%202019%20and%20encounter%20a%20Problem%20in%20VMs%20DHCP%20(possibly%20PXE%2FTFTP)%20Reply%20in%20Hyper-V%2C%20if%20the%20vSwitch%20is%20connected%20to%20a%20NIC%20Teaming%20Adapter.%3C%2FDIV%3E%3CDIV%20class%3D%22votinglabel%22%3EThe%20exact%20same%20Constellation%20did%20work%20in%20Hyper-V%202016.%3C%2FDIV%3E%3CDIV%20class%3D%22votinglabel%22%3EIt%20does%20work%2C%20if%20we%20dissolve%20the%20NIC%20Team%20and%20bind%20the%20single%20Adapter%20to%20the%20vSwitch.%3C%2FDIV%3E%3CDIV%20class%3D%22votinglabel%22%3ECurrently%20the%20conclusion%20leads%20to%20the%20Multiplexor%20Adapter%20Driver%20in%20Windows%20Server%202019%20or%20a%20combination%20of%20the%20Teaming%20Driver%20with%20the%20vSwitch%20Driver%2FArchitecture%2FSecurity%20Features.%3C%2FDIV%3E%3CDIV%20class%3D%22votinglabel%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22votinglabel%22%3EDid%20anybody%20see%20the%20same%20behavior%3F%3C%2FDIV%3E%3CDIV%20class%3D%22votinglabel%22%3EAre%20there%20any%20issues%20known%20regarding%20the%20above%20mentioned%20problem%3F%3C%2FDIV%3E%3CDIV%20class%3D%22votinglabel%22%3ECan%20somebody%20at%20MS%20please%20check%2C%20if%20there%20are%20any%20open%20issues%20on%20this%3F%20(Teaming%20Driver%2FMultiplexor%20Driver%26nbsp%3B%3CSPAN%3ENdisImPlatform.sys%20(Version%2010.0.17763.1)%3C%2FSPAN%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(Windows%20Server%20DC%201809%20Build%2017763.194)%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-303416%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EClustering%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
JanStroeder
Occasional Visitor
We have a 4 node Hyper-V Cluster running under Windows Server 2019 and encounter a Problem in VMs DHCP (possibly PXE/TFTP) Reply in Hyper-V, if the vSwitch is connected to a NIC Teaming Adapter.
The exact same Constellation did work in Hyper-V 2016.
It does work, if we dissolve the NIC Team and bind the single Adapter to the vSwitch.
Currently the conclusion leads to the Multiplexor Adapter Driver in Windows Server 2019 or a combination of the Teaming Driver with the vSwitch Driver/Architecture/Security Features.
 
Did anybody see the same behavior?
Are there any issues known regarding the above mentioned problem?
Can somebody at MS please check, if there are any open issues on this? (Teaming Driver/Multiplexor Driver NdisImPlatform.sys (Version 10.0.17763.1)

 

(Windows Server DC 1809 Build 17763.194)

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies