Hello,
I have several users reporting connectivity issues with their laptops, what these users have in common is that they run virtual machines using Hyper-V on their laptops.
OS: 8 & 8.1
NIC: some have Ethernet connection & Wifi but some only have wifi (with a USB to Ethernet adaptor)
VM connection to the internet:
- some user have our "recommended" settings: a "shared" internal NIC (the VM has its own separate network and the laptop "routes" the VM to the internet)
- some users have a direct external connection (not "recommended" because our pool of IP is not infinite and to avoid to VM with the same ID in case they did not import the template VM correctly)
1. Usually, they notice the connectivity issue when the switch from physical LAN: in that case, I tell them to go for ipconfig /release then /renew (it solves the "mix up" between old & new DHCP)
2. Some of them have only a wifi NIC on their laptop (no "physical" ethernet connection). In theory, Hyper-V can now run over wifi although it is not ideal yet. Is there any solution beside running only one VM at a time and avoiding browsing on both the VM and the host at the same time ?
3. in the Hyper-V virtual switch, some testing on a desktop that has no wifi but also had connection issues (it was used to check the configuration of Hyper-V) showed that unchecking the VLAN ID option in 8.1; before (in Windows 8) we used to check that option) somewhat improved things. Does anyone know how the VLAN ID option could affect the connectivity to Internet of both the host and the VM ?
Is there a more permanent solution to the connectivity issues than ipconfig /release / renew on the VM each time they swap location or VM ? because some of my users will complain that "this is not a solution..."
Has there been any changes to the latency of the DHCP cache for the VMs in Hyper-V between Windows 8 and Windows 8.1 that would explain the increased number of complains ?
Thanks for the ideas