Windows Server TechCenter >
Windows Server Forums
>
Windows Server 2008 R2 Hyper-V
>
NIC Drivers on HyperV-Server - HP NC110T
NIC Drivers on HyperV-Server - HP NC110T
- Hey guys,
i recently installed a 2008 R2 Hyper-V Server (the Core-Version) on a HP ML 150 G5. This Server has two HP NC110T PCIe NICs. After the 2008r2-Setup the server just found its Onboard NC105 NIC. So I went to the HP homepage and downloaded the 2008 R2 drivers for HP NC-Series E1E. After installation the server detects its nics. In remote computer management i could see following error: This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
I tried the same with a Intel PRO 1000 MT PCI Server Adapter but it ends up with the same error.
Thanks for the help!
Answers
Hi,
It seems that there are some compatibility between the driver and Hyper-V Server. I recommend that you contact the manufacture of the NIC for more details.
By the way, please try to install a full installation of Windows Server 2008 R2 to check whether it works.
Vincent Hu
- Marked As Answer byVincent HuMSFT, ModeratorTuesday, November 03, 2009 6:29 AM
Hi,
As I mentioned in my first reply, it seems that there are some compatibility issue with the driver, there is a post discussed the similar issue, you can refer to:
Hyper-V Server: Intel PRO/1000 only showing up as one NIC?
Vincent Hu
- Marked As Answer byMax B. Tuesday, November 03, 2009 8:11 AM
All Replies
- Hi Max, I'm also facing the same problem with a modern IBM Server, I added an aditional NIC and Windows report the same, that the device is not working because of drivers.
I also used the pnputil in order to install the lastest .inf from the manufacturer but I cannot get it to work. Maybe someone at MS could give a shot on this.
Thanks for your help.
Ing. Gabriel O. Zabal Hi,
It seems that there are some compatibility between the driver and Hyper-V Server. I recommend that you contact the manufacture of the NIC for more details.
By the way, please try to install a full installation of Windows Server 2008 R2 to check whether it works.
Vincent Hu
- Marked As Answer byVincent HuMSFT, ModeratorTuesday, November 03, 2009 6:29 AM
- Hi Vicent, I don't think that is a compatibility problem with the driver, as I already with two diferent aditional NICs. And Windows Hyper-V Server R2 detects and installs the MS driver fot both, then I tried with the manufactuer driver. Anyway today I'm reproducing the problem and going to install a W2008 R2 STD FULL in order to see if the problem persists, and I'll post the results.
Ing. Gabriel O. Zabal - Hi,
I tried the installation of W2008 R2 STD FULL too. The drivers were loaded correctly and the NICs are fully functional...- Marked As Answer byVincent HuMSFT, ModeratorTuesday, November 03, 2009 6:29 AM
- Unmarked As Answer byMax B. Tuesday, November 03, 2009 7:37 AM
Hey,
I don't think this is the answer! With W2008 HyperV Server R2 the drivers are NOT loaded correctly. But what's the problem here?Hi,
As I mentioned in my first reply, it seems that there are some compatibility issue with the driver, there is a post discussed the similar issue, you can refer to:
Hyper-V Server: Intel PRO/1000 only showing up as one NIC?
Vincent Hu
- Marked As Answer byMax B. Tuesday, November 03, 2009 8:11 AM
Thank you Vincent!
I will contact HP on this. But nevertheless I will switch to W2008 R2. Just because im interested, is there a difference with the driver models of Hyper-V Server and 2008 R2 Std/Ent?
Edit: For your information: I already tried the pnputil-thing with the "HP NC-Series Intel E1E Driver for Windows Server 2008 R2" without any positive results :(- I have same issue with any additional NIC I put into Hyper-V R2 box.
I'm also 100% sure that it is not driver compatibility problem as Intel PRO/100 S which was present at Hyper-V installation in PCI3 slot, shows same error when I put it into PCI1 or PCI2 slot and works only on PCI3 slot.
Any other Intel NIC using same driver (Intel PRO/100+ or Intel PRO/1000 M) shows same error no matter which PCI slot I put it in including PCI3.
It looks like Hyper-V R2 server has serious PnP problem. - I Also can confirm that it's not a driver / manufacturer isue, as I toke another server identicaly, installed Hyper-V Server R2 and installed the same NIC that didn't work on the other server, but this time tried diferent PCI slots and it detects and install the driver from Microsoft and works fine. The isue it's not on the driver but on the hardware detection / pnp of Hyper-V R2 as it seems. Also on WS2008 R2 FULL works fine, the isue it's not reproduced.
Going further I already tried this tool http://www.portlock.com/products/device_manager/ (free) that allows to install and load .inf driver. But it' reports an error when I try to install an updated driver for the non working NIC, that tells me that it's not a driver isue, as I cannot load new drivers either.
Ing. Gabriel O. Zabal - Any possibility for MSFT staff to return to this obiously unanswered question?
Intel do not provide support for built-in drivers for HyperV R2 (Windows 7 as well).
It is either fault of bulit-in drivers, certified by Microsoft, or Hyper-V R2 Server designed by Microsoft.
I think Microsoft should investigate this problem a little bit more than "Contact your hardware manufacturer". - I have some information, it's not a problem with the Intel driver, I reproduced the isue with a broadcom NIC, it's more an Hyper-V R2 thing.
I have reproduced to the step that if the Hyper-V is already configured with a virtual switch, any additional NIC that you insert wont work.
On a fresh install of Hyper-V, without configuring anything, I can add NIC (the same NIC that didn't work before) and works fine.
Looking at the event viewer I see that the pnp engine of hyper-v detect's and install fine the driver, but it fails to inject the service driver and start. So the problem it's not on the detection or driver but on the Hyper-V R2 Server. Could someone at MSFT confirm this ??
Ing. Gabriel O. Zabal - I hit the very same wall today. Is there an official solution for this from Microsoft? Do we need to reinstall, or is there a quick fix?
