Hyper-V Virtual Switch and VLAN Tagging Not Working?

hi all,

we're in process of testing server 2012 hyper-v before upgrade our production cluster summer.  we seem having issue vlans when being tagged through hyper-v virtual switch.  the test switch hp procurve 2810 , i've triple checked vlan settings on physical ports make sure correct.

i create new virtual switch , allow management os access no vlan identifier.  the management interface works fine , traffic going out untagged on physical nic expected , has connectivity.  if add vlan identifier on management os no longer external connectivity.  i have tried multiple vlans same effect.  i believe had same problem last time tried tagging vm traffic can't yet test this.

if create team instead of virtual switch on physical interface, can create multiple virtual adapters vlans tagged on switches physical port , each virtual adapter gets connectivity.

we have tried on 3 different physical network cards (broadcom, intel , realtek) same results.  

any suggestions? hot fixes?  

i'm running windows updates on box right see if anything changes.

hi lawrence

thanks update info, can confirm update installed on server.  additionally although simalar our problem, in our case vm's , management vethernet adapters not network connectivity @ point when using vlans.

have managed things working on broadcom cards.  it appear each physical network card has have settings configured in order correctly pass vlan tags virtual switch.  (even though pass vlan traffic tagged via virtual interface on team odd!) 

quoted following article: http://social.msdn.microsoft.com/forums/de-de/winserverhyperv/thread/cb771a3a-870d-4771-8658-97f0dcc47672 post mikelascha - 

"the "real" issue 802.1q tagging not enabled on host nic drivers.  having "vlan , priority" set "enabled" not enough!
 
in case unlucky in nic's use (broadcom bcm5708c netxtreme ii gige, , intel(r) pro/1000 pt dual port server adapter) both have call "non standard" names setting. 
 
for broadcom's, changing vlan id property 0 1 enables vlan tagging , works expected.  thanks on setting.
 
the intel's tougher nut crack settting not exposed through nic's advanced properties, through registry .  changing hklm\system\currentcontrolset\control\class\{guid}\xxxx\vlanfiltering registry key (where {guid} guid containing network adapter configuration , xxxx nic confgured) 1 0 , rebooting corrects issue.  the easiest way find proper key in system use find command in regedit enough of network adapter name (i.e. intel's, find "1000 pt")."

it's shame isn't better documented took lot of searching around find answer, i'm sure lot of other people falling foul of this.  all hyper-v documentation implies can enable these features without configuring of network card.  would have information more visible.

help.  onwards testing fancy new features!

Windows Server  >  Hyper-V