After creating a team or VLAN using Intel advanced networking service (ANS), any Hyper-V* virtual interface created cannot communicate to the network.
Failed network communications can be caused by either of the following:
- A virtual interface created on any team or VLAN cannot bind to the "Client for Microsoft* Network" protocol once an ANS team or VLAN has been created.
- VLAN IDs configured on the Virtual NIC and the ANS VLAN do not match.
Follow these steps for creating the virtual switch interface:
- Use Intel® PROSet to create the team or VLAN.
- Open the Network Control Panel.
- Open the team or VLAN.
- On the General Tab, uncheck all of the protocol bindings and click OK.
- Create the virtual NIC. (If you check the "Allow management operating system to share the network adapter." box you can do the following step in the parent partition.)
- Open the Network Control Panel for the Virtual NIC.
- On the General Tab, check the protocol bindings that you desire.
||For Server Core installations: |
In order to attach a Hyper-V virtual NIC to a team, you must disable all of the protocol bindings on the team. No command line tools are available to enable or disable protocol bindings on a Server Core installation. You must use a version of Windows Server* with a GUI to attach a virtual NIC to a team.
||If you create ANS VLANs in the parent partition, and you then create a Hyper-V Virtual NIC interface on an ANS VLAN, then the Virtual NIC interface must have the same VLAN ID as the ANS VLAN. Using a different VLAN ID or not setting a VLAN ID on the Virtual NIC interface will result in loss of communication on that interface.|
Hyper-V* Child Partition Cannot Communicate through RLB Team
| Windows Server 2008*, Windows Server 2008 Standard*, Windows Server 2008 Standard x64 Edition*, Windows Server 2008 Enterprise*, Windows Server 2008 Enterprise x64 Edition*, Windows Server 2008 Datacenter*, Windows Server 2008 Datacenter x64 Edition*, Windows Web Server 2008*, Windows Web Server 2008 x64 Edition*, Windows Server 2008 for Itanium-based Systems*
This applies to: