Legacy Network Adapter behind NAT


hi,

i've discovered problem hyper-v "legacy network adapters"

i trying setup virtual internal network access internet through nat (i've tried internet connection sharing , rras) running on host machine.  works fine in windows server 08 guest vms integration components using regular network adapter.  but, won't work ubuntu vms using legacy network adapters.

i figured out problem when added legacy network adapter windows server 08 vm , tried connect internet.  same problem ubuntu vms - if try ping, resolve ip address, request times out.

what different legacy network adapter in hyper-v isn't allowing internet connections behind nat work?  ideas?  how else vms on internal network connect internet?

thanks,
dave

fyi... update last post.

the change required go device manager, go properties of physical nic used create virutal external network in hyper-v, click on advanced tab , change setting ipv4 checksum offload none.

no registry entries or else needed.  can toggle ipv4 checksum offload feature on , off , watch legacy adapters can no longer ping google.com.  

i still don't understand why legacy adapters affected - in hyper-v rc0 should expect fixed in final release?

dave


Windows Server  >  Hyper-V



Comments

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

Event ID 64,77,1008 Certificates Events Windows Server 2008, 2008R2