Choices for team types are the same as when there is no virtualization. Make sure you use the http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=2248 latest software and drivers. Version 14.0 was just posted and contains enhancements to work better with Hyper-V.
Receive Load Balancing (RLB) will not work with Hyper-V as explained in http://www.intel.com/support/network/sb/CS-029843.htm Hyper-V* child partition cannot communicate through RLB team. You should take a look at the steps for creating a team in http://www.intel.com/support/network/adapter/pro100/sb/CS-030354.htm Hyper-V* virtual NIC will not communicate before creating the team.
I am using version 14.0
When I team two nics using AFT and then create a virtual switch and add the teamed nic to the virtual switch NETBIOS over TCP becomes disabled causing problems accessing file shares and group policies. The parent is server core so getting all the settings for the physical and virtual nics is tricky. I beleive I found the proper registry keys and attempted to enable NETBIOS over TCP without any luck.
Any other ideas?
This does sound like a possible binding problem, doesn't it? I do not have any good ideas at the moment. I am going to ping some of my contacts here at Intel to see what ideas we can come up with.
I am not sure how many details you want to share in a public forum, but feel free to post more details about your setup to help us pinpoint the issue or come up with more suggestions. What are the NICs in the system? What steps, scripts, and such did you follow to setup the team and the virtual switch? What is the child OS where you are using the team? Do you have full TCP/IP connectivity on the team except for the NetBIOS functionality? If you disable one NIC on the team is the failover working?
If you are uncomfortable with posting details heare and you have Intel boxed adapters (retail, not OEM NICs) you might want to open a case with Intel Customer Support to get into the details. If you purchased through an OEM, then you would need to go through their support.
Good news. Our developers believe that the problem you described is a binding problem like we suspected. Although you do not have a GUI for manipulating the protocol bindings a Microsoft developer has written http://code.msdn.microsoft.com/nvspbind Hyper-V Networking Command Line Tool for Changing NIC Bindings. With this utility you can manipulate the bindings per http://www.intel.com/support/network/adapter/pro100/sb/CS-030354.htm Hyper-V* virtual NIC will not communicate from the command line.