New
#11
Agreed (with @cereberus): I've seen the bandwidth bug on all of my 1803 PCs with Hyper-V enabled. Sigh.
--Ed--
Hi folks
I'm mystified by this as well
On VMWare using Bridged (not NAT) networking --that's the equivalent in HYPER-V of using an external switch I'm getting around 115 MB/s (not Mb/s note) over wifi file transfer on Lan between a HYPER-V VM and a separate Windows machine (i.e not the one the VM is hosted on) so there's got to be something with the networking stuff.
Host machine running HYPER-V is a decent machine so it's not lack of hardware resources.
I'm going to test ESXi -- this is another Type 1 Hypervisor -- see if same problem arises with network -- note for ESXi for Home users you'll need a separate machine to configure and access the VM's as the console product which can run on the hosting machine is a commercial (i.e paid) product. If you've got a spare laptop / other machine then no probs with VM creation and accessing them. Big problem for some -- if the network card is incompatible then the whole Esxi process fails -- bog standard Ethernet works -- wifi is questionable but USB-->Lan might work depending on your machines BIOS.
Cheers
jimbo
Hi cerberus,
i'm not familiar enough with hyper-v to give you a step by step solution but hopefully I can give you a hint to resolve the issue.
Using NAT you basically are using a subnetwork inside your host machine, not visible in you LAN; usually if you need to expose VM services to the LAN (i.e. RDP service) you have to set up port forwarding (i.e. host 3388 port -> VM port 3389) from the Host to the VM.
HTH.
I registered myself just to post this link:
How To Fix Slow DNS Response and Page Loading with Hyper-V Default Switch pauby.com
- Hannu