Hyper-V Network Virtual switches

Hi,
Good Day!
We have some doubts on Hyper-V Network Virtual Switches:
There are two physical NICs on a Hyper-V Host. One is connected to the public and other connects the internal VM Network. We create two virtual switches; "CustomerNetwork" and "PublicNetwork". "CustomerNetwork" has 192.168.x.x
series IP Address and "PublicNetwork" has a public IP Address.
We have also setup a software router VM with two virtual NICs. One vNIC connects to "CustomerNetwork" and other one connects to "PublicNetwork". We assign an IP address to the vNIC connected to "CustomerNetwork". The IP Address
assigned is 192.168.2.99.
Confusion here is that we don't know which IP Address we should assign to the VNIC of router VM which is connected to "PublicNetwork". We have only one public IP Address. Shall we assign public IP Address to the VNIC of Router VM or the "PublicNetwork"
virtual switch or we should remove the public IP Address from the virtual switch?
Thank you for your time for clarifying our doubts! As always, appreciate your help!
Thank You,
Aurther L

On your router VM , Public IP should be assigned to Public network . Beaaware you are only allowed one external switch per hyper V host. Alternatively Create two VNic from from Private network, Assign public IP to one and local IP to another
assuming you have internet connection on local network.
hope this helps
thanks
mumtaz

Similar Messages

Cannot create Hyper-V external virtual switch Server 2012 R2

Hi,
I am unable to create an external virtual switch on server 2012 R2. I have two Broadcom NICS bridged on a DC fully functional now. I can install Hyper-V but the option is grayed out to create an external switch. I try binding it to the
network bridge, connecting my two NICS and it makes no difference.
Am I correct in assuming that I cannot use Hyper-V on this server if the two NICS are bridged?

try command "New-VMSwitch" from Powershell to get more information
Windows 2012 & Hyper-V: Converged Network and QoS
Hyper-V Virtual Switch 101: How to create and use Virtual Switches to connect Virtual Machines to Network
Have a nice day !!!

Poor network when create virtual switch in hyper-v 2012

Hello,
i installed on DELL R620 windows server 2012 STD and add the hyper-v role
when i created a virtual switch , the speed of network in the HOST( the server itself) is ver poor ( copy file from fileserver is 300Kbs)
when i remove the virtual switch , the speed of the network is better( copy file from fileserver is 10-20Mbps)
i spoke with DELL support center , and after check up , no problem has found.
i tried all the chnges with the offload checksum etc but nothing helped
Please your comment about this issue
Thanks
Dotan

Need some additional information
Which Team type are you utilizing?
Which Raid Controller are you using on the hosts?
I would suggest you try this as well while its specific to 10Gb CNA's it can help with 1Gb in some cases. SMB
FILE COPY PERFORMANCE
Also utilizing the low latency Bios settings can often offer additional NIC performance
Dell 12th Gen Low Latency Bios Settings
-Sean

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking and Hyper-V.

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking!
http://www.youtube.com/watch?v=8mOuoIWzmdE
Hi thanks for reading. Now I may well have my terminology incorrect here so I will try to explain as best I can and apologies from the start.
It’s a bit of both Hyper-v and Server 2012R2.
I am setting up a lab with Server 2012 R2. I have several physical network cards that I have teamed called “HostSwitchTeam” from those I have made several Virtual Network Adaptors such as below
examples.
New-VMSwitch "MgmtSwitch" -MinimumBandwidthMode weight -NetAdaptername "HostSwitchTeam" -AllowManagement $false
Add-VMNetworkAdapter -ManagementOS -Name "Vswitch" -SwitchName "MgmtSwitch"
Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "MgmtSwitch"
When I install Hyper-V and it comes to adding a virtual switch during installation it only shows the individual physical network cards and the
HostSwitchTeam for selection. When installed it shows the Microsoft Network Multiplexor Driver as the only option.
Is this correct or how does one use the Vswitch made above and incorporate into the Hyper-V so a weight can be put against it.
Still trying to get my head around Vswitches,VMNetworkadapters etc so somewhat confused as to the way forward at this time so I may have missed the plot altogether!
Any help would be much appreciated.
Paul
Paul Edwards

Hi P.J.E,
>>I have teams so a bit confused as to the adapter bindings and if the teams need to be added or just the vEthernet Nics?.
Nic 1,2
HostVMSwitchTeam
Nic 3,4,5
HostMgmtSwitchTeam
>>The adapter Binding settings are:
HostMgmtSwitchTeam
V-Curric
Nic 3
Nic 4
Nic 5
V-Livemigration
HostVMSwitch
Nic 1
Nic 2
V-iSCSI
V-HeartBeat
Based on my understanding of the description , "HostMgmtSwitchTeam and
HostVMSwitch " are teamed NIC .
You can think of them as two physical NICs (do not use NIC 1,2,3,4,5 any more , there are just two NICs "HostMgmtSwitchTeam and
HostVMSwitch").
V-Curric,
V-Livemigration , V-iSCSI ,
V-HeartBeat are just VNICs of host (you can change their name then check if the virtual switch name will be changed )
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Routing of Network Traffic Between VLANs on a Hyper-V Virtual Switch

I am trying to discover how network traffic generated by reads and writes to RDVH User Profile Disks is routed through my network. I have a pool of Hyper-V
desktop vm’s in their own VLAN (vlan1) with their own NIC bound to a Hyper-V Virtual Switch. On the same server I have another management NIC for the OS on a different VLAN (vlan2) and finally on another server I have a virtual machine which hosts the User
Profile Disks. The VM that hosts the User Profile Disks is on the same VLAN as the management NIC for the OS (vlan2).
When tracing the flow of network traffic to and from the User Profile Disk VM it all comes through the vlan2 NIC on the server where the virtual
desktop VMs reside and nothing comes through the vlan1 NIC on this server. I would have expected the traffic to the virtual desktop VMs to come in through the desktop VMs VLAN NIC (vlan1).
This leads me to two possibilities as to how the desktop vm’s on vlan1 get their data to and from the User Pofile Disk vm on vlan2 without routing.
The desktop vm’s Hyper-V Virtual Switch automatically routes the User Profile Disk traffic from vlan1 to vlan2 internally using a virtual switch learning algorithm
Hyper-V itself handles all reads and writes to the User Profile Disks and since that is using the management NIC for the OS it is already on vlan2 and so the network traffic never leaves vlan2.
Any comments on the reason for traffic taking the path it does (as outlined above) as opposed to being layer-3 routed from VLAN1 to VLAN2?

Thanks for your reply Brian. I think your last paragraph above is what I have set up:
If you simply forward one VLAN to one physical NIC and the VMS on the corresponding External Virtual Switch simply end up on that VLAN without Hyper-V doing anything at all - but this dedicats one physical NIC per VLAN.
The Virtual Machines NIC that the vSwitch is patched to and the NIC for the OS are on different VLANS (both NICs are plugged into un-tagged ports on my switch).
The vNICs on the VM's are not tagged to a VLAN (The VLAN ID\ 'Enable virtual LAN identification' box is unticked)
My vSwitch is set up as connected to 'External Network' and isnt shared with the management network.
What I am trying to get at is how would network traffic on the VLAN my vm's are on get to the VLAN that the NIC for the OS is on without going through the router (even though a routable path is available) ?
Is it possible the 'learning algorithm' referneced in a Technet article below is involved here (sorry I cant post links)?
For the virtual machine to communicate with the management operating system, there are two options. One option is to route the network packet through the physical network adapter and out to the physical network, which then returns the packet back to
the server running Hyper-V using the second physical network adapter. Another option is to route the network packet through the virtual network, which is more efficient. The option selected is determined by the virtual network. The virtual network includes
a learning algorithm, which determines the most efficient port to direct traffic to and will send the network packet to that port. Until that determination is made by the virtual network, network packets are sent out to all virtual ports.
Thanks,
Andrew

Hyper-V Network Configuration Problem - Virtual Switch

Hi guys,
I'm looking for some help with a Hyper-V Network issues. I have been handed over a project by a client that is not fully complete and the person who built it is not available at all. The setup is a HP C7000 blade chassis and a HP SAN.
The previous guy built a hyper-v cluster with 2 nodes; HV1 & HV2 - this works fine, I can live migrate etc and all is good.
This is how it was handed over to myself, my job is to add the third node to the cluster so I have installed the OS, drivers etc. Hyper-V role and clustering role. My problem arises with the Hyper-V switch configuration.
Points;
Each node has two NIC adapters, both of these network adapters are teamed
A virtual switch is created on each node using the aforementioned NIC Team
On the existing nodes I can see the management IP for the node is set on the virtual switch adapter
On the third node (HV3) I created NIC Team using both of the NIC's, I then created an external virtual switch using this teamed network adapter. However when I try to apply a management IP address to the virtual switch adapter it won't respond and I see
a yellow triangle on the network adapter in the corner. When I remove the virtual switch and apply and IP address to the NIC Team the server is contactable and shows in the Cluster manager as up. However the problem then is I don't have a virtual switch.
If someone could help me with this that would be great - please tell me if you require further information.
Below is a screenshot of the adapter for HV1 (working fine) from failover cluster manager;
thank you advance :)

Hi Brian, thanks for the reply. This is what I tried initially. However I just restarted the server I tried it again - still no luck.
Just to clarify when I team together the two flexfabric network adapters and apply an IP address to the team for testing - the team works fine, so the team doesn't seem to be an issue.
Once I create the virtual switch and assign the team to the switch and enable management OS to share I apply the IP address to the vEthernet adapter and I can't ping the default gateway or anything for that matter.
Any other ideas ?

Maximising throughput of a team in converged networking scenario using Hyper-V virtual switch

Hi,
Recently I have been looking into the converged network scenario, I have read quite a few resources about this but I am struggling to make sense of maximising the bandwidth I have available.
I understand that a single TCP stream can only go down 1 physical NIC, so even if I had a team of 6 x 1Gbps NICS – the team would be 6Gbps, but I will never have a single transfer go faster than 1 Gbps. I’m pretty sure that’s right, how I understood it anyway.
To make a converged network, I need to team adapters together, then make a virtual switch, and make virtual NIC’s off of that virtual switch. Each vNIC I can assign for different purposes,
such as ISCSI, data sync and backup traffic. In the diagram below I have shown this configuration, each green pNIC is only 1Gbps, on my blue vNICs I use the minimum weighting configuration.
In my example below, I have 1 ISCSI vNIC, if a physical NIC failed then I understand that to mean that the bandwidth won’t reduce for ISCSI because a single stream can only go down one
NIC anyway, the team will reduce to 5Gbps. No vNIC will go faster than 1Gbps.
If this is correct, then how would I increase bandwidth to the disk system using ISCSI, is it simply a case of creating an additional vNIC for ISCSI traffic, adding it to the same team
and configuring MPIO so the traffic will eventually end up through different pNICS? In my mind, MPIO can’t round robin ISCSI data to more physical NICs because the ISCSI and MPIO only know about the vNIC, I assume it is the team that ultimately handles the
placement of the stream onto the pNICS.
Do I simply do the same for Data Sync and Backup traffic?
I’m not too concerned about the VMNET team, I am mostly focused on getting the best out of the core cluster resources I have. I haven’t shown the physical switches to the right of the diagram,
but these are already configured to accept the VLAN traffic on the ports and the same is all configured for the other half of the solution.
Just a little confused over the whole thing on how I could potentially achieve the 6Gbps I have at my disposal. In this configuration and testing so far, it seems quite difficult for me
to exceed about 1.5-2Gbps combined across all the vNICS (in this particular test server I am limited to 1 physical disk so it’s hard to gauge the performance, the disk will take probably about 200MB/2Gbps maximum, that’s with ISCSI (file copying) and data
Sync going on between two servers at the same time.
many thanks for your help
Steve

Hi,
Recently I have been looking into the converged network scenario, I have read quite a few resources about this but I am struggling to make sense of maximising the bandwidth I have available.
I understand that a single TCP stream can only go down 1 physical NIC, so even if I had a team of 6 x 1Gbps NICS – the team would be 6Gbps, but I will never have a single transfer go faster than 1 Gbps. I’m pretty sure that’s right, how I understood it anyway.
To make a converged network, I need to team adapters together, then make a virtual switch, and make virtual NIC’s off of that virtual switch. Each vNIC I can assign for different purposes,
such as ISCSI, data sync and backup traffic. In the diagram below I have shown this configuration, each green pNIC is only 1Gbps, on my blue vNICs I use the minimum weighting configuration.
In my example below, I have 1 ISCSI vNIC, if a physical NIC failed then I understand that to mean that the bandwidth won’t reduce for ISCSI because a single stream can only go down one
NIC anyway, the team will reduce to 5Gbps. No vNIC will go faster than 1Gbps.
If this is correct, then how would I increase bandwidth to the disk system using ISCSI, is it simply a case of creating an additional vNIC for ISCSI traffic, adding it to the same team
and configuring MPIO so the traffic will eventually end up through different pNICS? In my mind, MPIO can’t round robin ISCSI data to more physical NICs because the ISCSI and MPIO only know about the vNIC, I assume it is the team that ultimately handles the
placement of the stream onto the pNICS.
Do I simply do the same for Data Sync and Backup traffic?
I’m not too concerned about the VMNET team, I am mostly focused on getting the best out of the core cluster resources I have. I haven’t shown the physical switches to the right of the diagram,
but these are already configured to accept the VLAN traffic on the ports and the same is all configured for the other half of the solution.
Just a little confused over the whole thing on how I could potentially achieve the 6Gbps I have at my disposal. In this configuration and testing so far, it seems quite difficult for me
to exceed about 1.5-2Gbps combined across all the vNICS (in this particular test server I am limited to 1 physical disk so it’s hard to gauge the performance, the disk will take probably about 200MB/2Gbps maximum, that’s with ISCSI (file copying) and data
Sync going on between two servers at the same time.
many thanks for your help
Steve

Server loses internet connection after creating virtual switch in hyper-v

On a fresh Server 2012R2 Essentials install, I set up Hyper-v and created an external virtual switch. Connection to the vm is good but Health Report no shows loss of internet connectivity and that the router is incorrectly setup.
However, I still have a working internet connection? I worry that the server may not update or allow Anywhere Access at some time. Any suggestions? Thanks

If Hyper-V virtual switch behaves strange and server is destined for testing, then it's correct and I recomend delete this virtual switch and create it again.
Here is some issues with internet connection and Hyper-V switch, none of them does not match your problem, but can be inspirative for troubleshooting:
Windows 8 Hyper-V - how to give VM internet access?
Hyper-V kills internet connection when bridging
Configuring Hyper-V for multiple subnets with only one NIC (Server 2008 R2 Edition)
How does basic networking work in Hyper-V?
Best Regards,
thennet

How to route traffic across subnets when one NIC is a hyper-V virtual switch?

Having a bit of a problem with a hyper-V environment which does not seem to route network traffic on two different subnets between each other.
If it were a purely physical server with two NICs and a gateway set traffic would automatically be forwarded between the two different subnets.
However when one of those NICs is a hyper-V virtual switch this simple routing no-longer seems to work and no traffic gets forwarded between subnets?
Situation is:
Hyper-V server with two NICs
NIC 1 = 192.168.0/24 - main Internal company network.
NIC 2 (hyper-V virtual switch.) = 192.168.1/24 - connects to ADSL internet router
Virtualized Domain Controller.
One or two virtualiszed NICs as necessary
How then does traffic get routed between these two subnets? If RRAS has to be configured to do this where is the best place to do it, on the hyper-V host or on the virtualized domain controller?
Thanks,

Hi ,
You can create an internal virtual switch and configure an IP for it (I assume it is 192.168.1.2/24) .
After you enable RRAS in hyper-v host there will be two gateways for different subnets .
" NIC 2 (hyper-V virtual switch.) = 192.168.1/24 - connects to ADSL internet router "
The problem is here ,if these VMs need to access internet .
So , these VMs can not configure their gateway same as the IP of internal virtual switch , you may set VM's gateway as the ADSL internet router's IP meanwhile add a static route entry for every VM .
Please refer to the Syntax :
route add -p 192.168.0.0 mask 255.255.255.0 192.168.1.2
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to get the maximum bandwidth/MaxSpeed/Capacity of a Hyper-V virtual-switch?

We are trying to monitor Hyper-V environment (Windows 2008 R2 and Windows 2012) using WMI, and have a very specific question Hyper-V virtual-switch.
We have referred the below mentioned classes and their properties.
1. Win32_NetworkAdapter (namespace:root\cimv2, property:Speed)
2. Msvm_InternalEthernetPort (namespace:Root\virtualization\v2, property: Speed and Maxspeed)
3. Msvm_EthernetSwitchBandwidthData (namespace:Root\virtualization\v2, property:Capacity and Reservation)
All of the above classes and their properties returns 10000000000 (10 GBps) as MaxSpeed, which is NOT correct (as we know that our network connection is of 1 GBps)
Here is our question: How to get the maximum bandwidth/MaxSpeed/Capacity of a Hyper-V virtual-switch?

Until MSFT makes a change to increase the max speed of the virtual switch (and the resulting virtual ports) it will be 10 Gbps.
It has been this way since the original introduction in 2008.
What you are looking for is the most limiting segment in the path. The virtual switch does not assume the properties of the most limiting segment. Since the physical side could be a team, it could be a single NIC.
Your management layer must interpret the most limiting segment.
If you have not already been here:
http://blogs.msdn.com/b/tvoellm/archive/2009/04/23/monitoring-hyper-v-performance.aspx Then take a look.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

2012 R2 Hyper-V Virtual Switch Refuses to Be Created -- Error Messages Not Especially Helpful

Windows Servers 2012 R2 Standard
4 NICs
Windows 8.1 is guest of the host
Hyper-V
Virtual Switch Manager
External
Create Virtual Switch
External network
Choose a NIC that is connected to the physical Ethernet switch but otherwise unused
Tick Allow management operating system to share this network adapter
Untick everything else
Click Apply
"Error applying Virtual Switch Properties changes"
"Failed while adding virtual Ethernet switch connections."
"External Ethernet adapter "<name-of-adapter>" is already bound to the Microsoft Virtual Switch protocol."
Close
Cancel
Control Panel\Network and Internet\Network Connections
Change Properties of NIC to untick Virtual Switch protocol
Repeat steps as above
"Virtual Switch Manager for <name-of-server>"
"Error applying Virtual Switch Properties changes"
"An internal error occurred while processing the results of creating a new virtual switch."
"To refresh the results, close and then reopen this window."
Close
Dead in the Water
An internal error occurred while processing the results of creating a new virtual switch. To refresh the results, close and then reopen this window.
The first one is to use a tool called “nvspscrub.js”. Download nvspscrub.js then from cmd run: “cscript nvspscrub.js”, this will delete all vswitches, virtual NICs in the parent partition and will unbind the switch protocol from all physical NICs.
This script aborts when a class turns up undefined. Maybe this old script applies solely to Windows Server 2008. Dunno.
NVSPbind
What I do now?
It is an internal error. Internal to what?
MARK D ROCKMAN

Hi Mark,
I just came across the same issue!
After troubleshooting, I deleted all my Virtual Switches and reinstalled my WiFi and Ethernet NIC drivers.
I'm now able to create the Virtual Switches without error.
Hope this helps.
Regards
Lee

Windows 8.1 - Hyper-V Virtual Switch fails to create

I'm running into a problem with creating a new virtual switch on my Windows 8.1 RTM box. Frist time attempt at Hyper-V on this system.
The error I get is as follows:
Error applying Virtual Switch Properties changes
Failed while creating virtual Ethernet switch.
switch create failed, name= 'B57B7B7B-64314AF5-AB8F-4521CBAA9FFBA', friendly name = 'New Virtual Switch': The system cannot find the file specified. (0x80070002)
The steps I have taken to try and resolve this issue.
1. Uninstall and reinstall Hyper-V...numerous times - no change.
2. Uninstall Hyper-V, reboot, uninstall NIC, reboot, reinstall NIC, reboot, reinstall Hyper, reboot - no change.
3. Uninstall it all again. Get new NIC drivers, for ASUS Sabertooth 990FX, first gen. Reinstall it all again - no change.
4. Updated BIOS, and check for virtualization, and DEP are enabled. - no change.
5. User powershell to create virtual switch - no change.
6. Tried resetting Hyper-V networking using the netcfg commands posted
here, failed, file not found.
Any help to resolving this would be greatly appreciated.
Thank you,
Sean

Hi Dw3xx,
Unusual problem,my suggestion is :
uninstall any anti-virus software then try to create the virtual switch
insert Win8 media and fix OS
Hope this helps.
Elton Ji

Hyper-V host 1Gbps NIC negotiated at 100 Mbps when used for Virtual Switch

Hi all,
Hoping someone can shed some light on this one as I’ve been trying to hunt down a solution for a week now.
Setup
HP ProLiant ML350 G6 with HP NC326i PCIe Dual Port Gigabit Server Adapter network adapters
Windows Server 2008 R2 Core with only the Hyper-V role installed
SBS 2011 installed as guest
Port 1 on Dual port NIC configured a physical port or management of Host only
Port 2 on Dual port NIC configured for use as an External Virtual Switch port for use by guests only
The issue is that the physical port connected to the Hyper-V virtual Switch negotiates with the network switch at 100 Mbps full duplex while the management port negotiates at 1 Gbps full duplex. All clients (brand new HP Z210 workstations) also negotiate
with the switch at 1 Gbps.
During file copies and backups the network port connected to the Virtual Switch does not show any errors and transfers data at close to 100 Mbps. File transfers between individual workstations and workstations and server core again show no errors, but transfers
at 1 Gbps.
One observation is that the physical NIC connected to the Virtual Switch does not negotiate with the switch until the Hyper-V service has started (I’m guessing) the virtual switch.
Also, while staging the server the Hyper-V virtual switch created when the server was connected to a 100 Mbps switch not a 1Gbps switch as it is in production.
Has anyone encountered anything similar and if so how did you get the physical NIC to operate at full capabilities? Any assistance would be greatly appreciated.

Hi,
I purchased one gigabyte switch for home used several days ago, I just performed some copy tests between virtual machines and physical machines(not
Hyper-V host machine)in the same LAN, the average copy speed is 350Mb/s.
Best Regards,
Vincent Hu

OneDrive and Hyper-V Virtual Switch don't mix

Since the release of Windows 10TP I have had a Hyper-V VM configured running Win10TP. Since that time I have had OneDrive synchronisation problems IN THE HOST OS (as well as in Win10TP, but that is not my focus here).
In summary, if the path from OneDrive in the host Win8.1 installation to the Internet is via a Hyper-V Virtual Switch, OneDrive will not sync up any file beyond around 1-2MB. It will sync up deletions, and it will sync down any changes that happen
in the cloud. This happens even if the host OS is the only OS connected to the Virtual Switch - I.e the guest OS has no virtual adapter connected to the VSwitch.
Details:
Configuration A. Surface Pro with Windows 8.1 connected to the Internet via WiFi. Hyper-V has always been installed on this box (for the Windows Phone Emulator) but no VM is normally active. In this configuration the host OS connects directly
to the WiFi adapter.
Configuration B. As above, but a Hyper-V Virtual Switch is in place with the host OS connected to the Internet via this VSwitch, and thence via the WiFi adapter. There is a guest Win10TP VM created. It doesn't matter whether this VM
is running or not, or whether it also has a connection to the Internet via the VSwitch, as far as the tests described below are concerned.
In configuration A, OneDrive syncing works correctly and uploads occur at roughly the speed of my uplink (not high). OneDrive has always worked correctly for me and in the month prior to installing the Win10TP I travelled around the country (Australia)
using sometimes dodgy Internet connections in motels etc., and it always worked.
In configuration B, OneDrive (in the host OS Win8.1) simply will not work correctly. It will sync all downloads correctly. It will sync up file deletions. It will sync up small files. But it WILL NOT sync up larger files.
Attempting to sync up any file above around 1-2MB results in sync hanging at "0.0KB out of x.xMB". In the OneDrive app it shows the file as Pending. Nothing I can do will make it sync those files. Deleting the offending file and
pausing and restarting syncing will straighten everything out and small syncs will continue to work. When this problem is present, there is no traffic visible between the Sync Engine and the cloud.
I can alter the machine setup between Configuration A and B and back and so on and no matter how often I switch from A to B to A to B... configuration A always works and configuration B always fails.
So...
Am I possibly missing something in configuring Hyper-V VSwitches? Otherwise what is incompatible between OneDrive traffic and the VSwitch? There is nothing obvious to me.
I should note that all other operations on the network from the host OS or from the Guest OS appear to be working correctly.

When you performed configuration B - what more did you do other than create a Virtual Switch and check the box "allow management OS to share"?
If you did more than that - there is your issue.
The only difference between the two configuration should be the existence of the Virtual Switch - I mention this because it is not clear in your description and there are some folks that do strange internet sharing configurations that the OneDrive client
is not necessarily compatible with.
Another issue that might happen is that during the sync of your large files the power savings of the NIC is kicking in and interrupting that data transfer.
In this case try disabling all power savings on the physical NIC driver (when there is a Virtual Switch present).
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Cannot Configure Hyper-V Virtual Switch - VM has no internet access...

HI:
As stated in the title, I cannot configure my VM (OS Windows 7 Pro...) to access the internet...
When I attempt to configure a Virtual Switch with all defaults, I get this error: 0x800705B4.
I found an article online that advised to create the Switch internally without choosing the 'Connect to external network' option, then manually bridging the connections... which also didn't work...
Now I've got 'Hyper-V Virtual Ethernet Adapters' Stuck in my Device Mgr, and my VM still won't connect to the internet.
Help?

Hi GloFields,
As for the Office issue please try to post it here :
http://social.technet.microsoft.com/Forums/en-US/home?category=officeitpro&filter=alltypes&sort=lastpostdesc
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V Network Virtual switches

Similar Messages

Maybe you are looking for