locked
External Ethernet Adapter is already bound to the microsoft virtual switch protocol RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have a Virtual Switch that already bound to a Physical Adapter, and I would like to create another Virtual Switch to be bound to the same Physical Adapater, but I'm getting an error: "External Ethernet Adapter is already bound to the microsoft virtual switch protocol" Any help?

    Tuesday, January 12, 2016 11:33 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, one physical NIC can only be bound to one Virtual Switch.

    Network Bridges (like XenServer / ESX use) allow more than one per physical NIC.  And that is their VLAN application model.  It does not work that way with Hyper-V.

    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    • Proposed as answer by Leo Han Wednesday, January 13, 2016 5:59 AM
    • Marked as answer by Leo Han Monday, January 25, 2016 6:58 AM
    Tuesday, January 12, 2016 3:44 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote 
    New-VMSwitch -Name "VDI Network" -NetAdapterName "VDI Networks"
New-VMSwitch : Failed while adding virtual Ethernet switch connections.
External Ethernet adapter 'Microsoft Network Adapter Multiplexor Driver #2' is already bound to the Microsoft Virtual
Switch protocol.

    Tuesday, January 12, 2016 11:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, one physical NIC can only be bound to one Virtual Switch.

    Network Bridges (like XenServer / ESX use) allow more than one per physical NIC.  And that is their VLAN application model.  It does not work that way with Hyper-V.

    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    • Proposed as answer by Leo Han Wednesday, January 13, 2016 5:59 AM
    • Marked as answer by Leo Han Monday, January 25, 2016 6:58 AM
    Tuesday, January 12, 2016 3:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Brain, Does that means losing redundancy when it comes to multiple subnets of tagged and untagged traffic? Its real unfortunate that Hyper-v networking is just pain in the nick and it doesn't work the same as other virtualization platforms such as Citrix or VMWare... simplicity always win on long run... 1 Server, 2 pSwitches, 2 pNICs, 1 vSwitch and multiple VirtualLANs (PortGroups).. that's the way Hyper-v should approach networking.

    Thanks a lot for your answer, I have to live with how things being tailored.

    Regards,

    Wednesday, January 13, 2016 6:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The host operating system on Hyper-V host is also running inside a virtual machine (parent partition),
    which means that you can add and manage virtual network adapters to it in a similar manner as to
    other virtual machines. Each virtual network adapter can be connected to a separate Hyper-V virtual
    switch, or to the same Hyper-V virtual switch as other adapters. You can create multiple parent virtual
    network adapters that you then use for different purposes such as live migration, accessing the storage
    area network (SAN), and parent operating system management. You can also limit bandwidth for each
    virtual network adapter by assigning the QoS policy to the adapter. If you want to create a virtual network
    adapter in the parent partition, run the following Windows PowerShell cmdlets:


    Add-VMNetworkAdapter –ManagementOS –Name Management
    Add-VMNetworkAdapter –ManagementOS –Name Storage
    Add-VMNetworkAdapter –ManagementOS –Name “Live Migration”

    This may help you.....



    • Edited by HyperVbro Wednesday, January 13, 2016 12:26 PM
    Wednesday, January 13, 2016 12:25 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    "Does that means losing redundancy when it comes to multiple subnets of tagged and untagged traffic? "

    Hyper-V creates a virtual switch.  Just like a physical switch, you can run multiple subnets and/or VLANs on that switch.  I don't see how the inability to create multiple virtual switches on a single physical NIC loses redundancy.  Two virtual switches would then be dependent upon a single NIC.  The since NIC remains the single point of failure in both situations.

    "Its real unfortunate that Hyper-v networking is just pain in the nick and it doesn't work the same as other virtualization platforms such as Citrix or VMWare"

    You left out KVM and VirtualBox and ...  There are no standards in place.  What is developed by one vendor for their particular architecture does not always fit with another vendor's architecture.  Each one has its own strengths and weaknesses.  Viva la difference!  That is what makes progress.  I'm sorry that you find Hyper-V networking a 'pain in the nick [sic]'.  I've been using it from its inception and have found it to be sufficient for everything I have needed.

    . : | : . : | : . tim

    Wednesday, January 13, 2016 1:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have a Virtual Switch that already bound to a Physical Adapter, and I would like to create another Virtual Switch to be bound to the same Physical Adapater, but I'm getting an error: "External Ethernet Adapter is already bound to the microsoft virtual switch protocol" Any help?

    I have the same problem but I should add that I am unable to delete the previous Virtual adapter and I am unable to see it in the Hyper V management panel but it is there with a big fat X in networking. I just want to remove all virtual switches and have this windows 10 work.
    • Proposed as answer by Matt Paxman Wednesday, December 14, 2016 7:32 AM
    • Unproposed as answer by Matt Paxman Wednesday, December 14, 2016 7:32 AM
    Thursday, October 27, 2016 2:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You might have to uninstall the Hyper-V option and then re-install it. It sounds something was done improperly to get an 'unseen' adapter. Maybe uninstall/re-install will clear it up.

    . : | : . : | : . tim

    • Proposed as answer by Iains Thursday, July 18, 2019 1:57 PM
    Thursday, October 27, 2016 3:23 PM
  • Question
    Sign in to vote
    29
    Sign in to vote

    I had this issue and fixed it by unchecking the "Hyper-V Extensible Virtual Switch" option in the LAN properties:

    1. Network and Sharing (Win7)/Network (Win 10)
    2. Change adapter settings/options
    3. Right-click Local Area Connection
    4. Go to Properties
    5. Scroll to the bottom of the list
    6. Uncheck "Hyper-V Extensible Virtual Switch" option

    Once I had done this I could create a new Virtual Switch just fine.

    • Proposed as answer by joppe77 Monday, January 23, 2017 12:13 PM
    Wednesday, December 14, 2016 7:35 AM
  • Question
    Sign in to vote
    4
    Sign in to vote

    The nuclear option that works with Windows Core is using netcfg to wipe out all your networking settings and re-initialize the network card drivers.

    #WARNING! DANGER! THIS WILL DELETE ALL YOUR NETWORKING SETTINGS!
netcfg -d

    That seems to work better than nvspbind.exe or various other PowerShell commands when I really screw up my Hyper-V VMSwitch or LBFOTeam networking settings.

    Thursday, February 2, 2017 4:55 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It works with me. Thanks a lot!
    Monday, September 11, 2017 1:06 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I had this issue and fixed it by unchecking the "Hyper-V Extensible Virtual Switch" option in the LAN properties:

    1. Network and Sharing (Win7)/Network (Win 10)
    2. Change adapter settings/options
    3. Right-click Local Area Connection
    4. Go to Properties
    5. Scroll to the bottom of the list
    6. Uncheck "Hyper-V Extensible Virtual Switch" option

    Once I had done this I could create a new Virtual Switch just fine.


    That worked for me, thanks a lot.
    Monday, October 23, 2017 2:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, this worked for me as well.
    Thursday, November 23, 2017 9:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Perfect solution 
    Monday, May 21, 2018 12:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you thank you. I have been pounding my head against a wall for days. I had torn down and rebuilt the virtual network several times with several configurations. I could get to the internet I could ping out to other networks but they could not ping back. Finally I deleted everything and gave your answer a try before rebuilding and omg it worked.
    Sunday, October 28, 2018 6:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had this issue and fixed it by unchecking the "Hyper-V Extensible Virtual Switch" option in the LAN properties:

    1. Network and Sharing (Win7)/Network (Win 10)
    2. Change adapter settings/options
    3. Right-click Local Area Connection
    4. Go to Properties
    5. Scroll to the bottom of the list
    6. Uncheck "Hyper-V Extensible Virtual Switch" option

    Once I had done this I could create a new Virtual Switch just fine.


    I just had this same problem and used nearly the same methodology to fix the issue. Removing the LAN connection from the Hyper-V protocol (like the error says you should do) works.
    Wednesday, November 7, 2018 1:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello, 

    Fantastic, thanks, 

    Aguascalientes, Mexico

    Tuesday, March 5, 2019 6:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Your solution works for me, many thanks !

    Téva

    Tuesday, May 28, 2019 8:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    good job thanks it solved
    Friday, January 31, 2020 9:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Guys,

    Is there a powershell command to do the equivalent of the uncheck of "Hyper-V Extensible Virtual Switch" option?

    We use Server Core and i'm having a hard time finding the right powershell command.

    Shaun

    Wednesday, March 4, 2020 3:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You posted to a query that was marked as answered more than four years ago.  If the answer to the original query does not answer your question, you should create a new post with your detailed question.  Doing thus helps future people looking for answers as each post is then dealing with a single question and is easier to search.  Please create a new post with your detailed question.

    tim

    Friday, March 6, 2020 4:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    works perfect! Thanks a lot
    Wednesday, May 13, 2020 6:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks!!!!
    Thursday, August 6, 2020 3:19 AM