Solved

Error adding WiFi virtual switch to Hyper-V on Win 8.1

Posted on 2015-01-18
9
834 Views
Last Modified: 2015-01-25
I've installed a VM on Hyper-V. I want it to share WiFi for full access. When I add a new virtual network switch for the WiFi adapter, I get this error:
[Window Title]
Virtual Switch Manager for PC
[Main Instruction]
Error applying Virtual Switch Properties changes
[Content]
Failed while adding virtual Ethernet switch connections.
[Expanded Information]
Ethernet port '{97D28A98-EFFD-4A4C-B56D-CDCC8E584C74}' bind failed: This operation returned because the timeout period expired. (0x800705B4).
So, why does it fail? And what's with all the stuff in the message about Ethernet?

I *do* have a virtual Ethernet switch, which installed correctly.
0
Comment
Question by:BlearyEye
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
9 Comments
 
LVL 81

Expert Comment

by:David Johnson, CD, MVP
ID: 40556803
create a new external switch binding it to the wifi network adapter.  hyper-v manager must be run as an administrator
0
 
LVL 1

Author Comment

by:BlearyEye
ID: 40557535
I believe that's what I was doing
0
 
LVL 39

Assisted Solution

by:Philip Elder
Philip Elder earned 500 total points
ID: 40557937
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 1

Author Comment

by:BlearyEye
ID: 40558170
Actually, I had seen that in my poking around; should have mentioned it, sorry.

My WiFi adapter already has the Microsoft Network Adapter Multiplexor Protocol installed (but not checked). WiFi propertiesI don't see any other recommendation.
0
 
LVL 39

Assisted Solution

by:Philip Elder
Philip Elder earned 500 total points
ID: 40558235
This is what my WiFi vSwitch looks like:
WiFi vSwitchYours looks to be missing a check mark.
0
 
LVL 1

Author Comment

by:BlearyEye
ID: 40558718
OK, I enabled the Microsoft LLDP Protocol Driver. Still no joy. And I don't understand why is says "Failed while adding virtual Ethernet switch connections" when I've selected the WiFi adapter.
0
 
LVL 39

Expert Comment

by:Philip Elder
ID: 40558970
Could you post a snip of the Hyper-V vSwitch properties that is bound to the WiFi as I did please?
0
 
LVL 1

Accepted Solution

by:
BlearyEye earned 0 total points
ID: 40560200
Well, the problem is that it wasn't binding at all, so I couldn't do that. However, I tried the universal specific: reboot Windows. This time it went through. I now have vEthernet (Ethernet) and vEthernet (WiFi) connections. Calling both vEthernet is a little confusing but I guess it's right.

So, the original question is answered. I'll accept my post as the answer and credit points for the help.
0
 
LVL 1

Author Closing Comment

by:BlearyEye
ID: 40569009
Phillip Elder's comments were helpful and, having exhausted suggestions, led me to the idea of a clean start which sorted things out.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Internal network config 4 54
RAID Configuration 18 78
P2000 SAN SAS - RAID5 or RAID50 10 85
Receiving error when  installing Service Pack 3 on Microsoft Exchange 2010 3 54
First I will try to share a design of a Veeam Backup Infrastructure without Direct NFS Access backup. Note: Direct NFS Access backup transport mechanism is only available in Veeam v9 In above I try to design the Veeam Backup flow between i…
Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question