Check in the device manager/advanced tab for those network cards and see what hardware/vendor ID's are showing up.
On a DL380 G5 I have with the NC373i, I get:
PCI_164C14E4 SUBSYS_7038103C
I've never heard of being able to flash the firmware on these in such a way that it alters the vendor ID... the Broadcom flash merely updates whatever it needs.
If I had to guess, I'd say that on Windows Server 2012 R2, it's using some built-in drivers maybe, and that's what's showing up? Or it installed some other driver where that hardware ID is considered equivalent (same driver file) as the Broadcom 5708. That actually may be true...
What happens if you install the cp*.exe file for the NC373i manually? Does it give you any error?
I think the latest for the Broadcom multifunction cards is cp021772.exe (7.8.50.0). Note that the download pages for G5 servers don't really include Server 2012 options, but it should be the same multifunction driver from the G6/G7 models.
Also note that 7.8.50.0 seems to be working fine for Hyper-V, unlike it's predecessor which caused issues, 7.8.6.0. There's a whole thread on here about that little stinker and the Hyper-V issues in particular.
On a DL380 G5 I have with the NC373i, I get:
PCI_164C14E4 SUBSYS_7038103C
I've never heard of being able to flash the firmware on these in such a way that it alters the vendor ID... the Broadcom flash merely updates whatever it needs.
If I had to guess, I'd say that on Windows Server 2012 R2, it's using some built-in drivers maybe, and that's what's showing up? Or it installed some other driver where that hardware ID is considered equivalent (same driver file) as the Broadcom 5708. That actually may be true...
What happens if you install the cp*.exe file for the NC373i manually? Does it give you any error?
I think the latest for the Broadcom multifunction cards is cp021772.exe (7.8.50.0). Note that the download pages for G5 servers don't really include Server 2012 options, but it should be the same multifunction driver from the G6/G7 models.
Also note that 7.8.50.0 seems to be working fine for Hyper-V, unlike it's predecessor which caused issues, 7.8.6.0. There's a whole thread on here about that little stinker and the Hyper-V issues in particular.