Have a HP Pro Liant ML 370 Hyper-V Host with a HP NC375i Integrated Quad Port Multifunction Gigabit Server Adapter, running on x64 Windows Server 2008 SP2 Core installation, Enterprise Edition.
Have created a new virtual machine and installed x64 Windows Server 2008 standard with integrated SP2 (Volume Licence, MSDN download DVD). The installation worked fine, the virtual machine gets an IP address, but IP v4 connectivity is limited: Can only ping the VM itself and the Hyper-V Host where the VM is running on, but no other machines.
- Have reinstalled the integration services, same problem.
- Have created a new VM with Windows XP SP3. This machine has no connectivity problems at all with a Standard Hyper-V NIC.
- Have removed the network adapter from the W2008 VM, added a "legacy network adapter", and the connectivity problem was solved!
- Have removed the "legacy network adapter", added a standard network adapter. After starting the W2008 VM, the machined detected a "Microsoft virtuakl machine bus network adapter #2", and the connectivity problem is here again!
- Have verified the eventlogs of the hyper-v host and of the Windows 2008 server guest. There is absolutely no hints why the guest has no connectivity.
My questions:
- Has anyone an idea why only a legacy network adapter is working on a x64 Windows 2008 server with sp2 VM?
- Before posting this, I googeled and found that problems like this can arise when "TCP offloading" features are enabled on a hyper-v host. Has anyone a hint how to disable TCP offloading on a hyper-v host that is running on server core?
Thank you all in advance for any help.
Franz
Have created a new virtual machine and installed x64 Windows Server 2008 standard with integrated SP2 (Volume Licence, MSDN download DVD). The installation worked fine, the virtual machine gets an IP address, but IP v4 connectivity is limited: Can only ping the VM itself and the Hyper-V Host where the VM is running on, but no other machines.
- Have reinstalled the integration services, same problem.
- Have created a new VM with Windows XP SP3. This machine has no connectivity problems at all with a Standard Hyper-V NIC.
- Have removed the network adapter from the W2008 VM, added a "legacy network adapter", and the connectivity problem was solved!
- Have removed the "legacy network adapter", added a standard network adapter. After starting the W2008 VM, the machined detected a "Microsoft virtuakl machine bus network adapter #2", and the connectivity problem is here again!
- Have verified the eventlogs of the hyper-v host and of the Windows 2008 server guest. There is absolutely no hints why the guest has no connectivity.
My questions:
- Has anyone an idea why only a legacy network adapter is working on a x64 Windows 2008 server with sp2 VM?
- Before posting this, I googeled and found that problems like this can arise when "TCP offloading" features are enabled on a hyper-v host. Has anyone a hint how to disable TCP offloading on a hyper-v host that is running on server core?
Thank you all in advance for any help.
Franz