HP had to get it from somewhere. RSS topic feed Posts [ 1 to 25 of 75 ]. But when we enabled NIC-teaming, the server started rebooting itself atleast once a day, removing NIC-teaming stopped it. Biff Ars Tribunus Angusticlavius Tribus: Wednesday, October 24, 3:

Uploader: Yokree
Date Added: 13 January 2012
File Size: 56.80 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 33340
Price: Free* [*Free Regsitration Required]

Do you think that updating bxvbdx.

Sorry for my inexperience: Could you please give us some screen captures to help us understand your current scenario, and for further troubleshooting. Ok, I will try replacing all files I tested replacing only those two using regular w2k3, but it doesn’t work, same “Unable to nc33i network adapters” message.

I don’t even see them unless i untick the box ‘hide adapters that are unavailable for teaming’ btw have installed the correct drivers as far as i’m aware downloaded them from the hp site, though they were windows server R2 drivers Regards Regards Glenn Rose-Ward. Sat Jan 26, 3: Sign in to vote. It is WAY over my head or I would try and explain it to you so your issue can be solved to.


Highlander is working on an update to BartPE that will fix most of the issues with sound video and oddball devices that require advanced PnP support.

Adapters not available for teaming

I belive we need some registry entries added to your build to make this fly. That driver is also a match Select “Compatible Ids” from the drop down Just to be sure, is it correct if first I replace in the latest nightly 9. Fri Jan 25, I’m WAY to lazy to do that so I just rename them when it happens.

Yes i’ve resolved the problem and now have teaming working correctly.

Can you create teaming for these two onboard NICs? Best thing to do is to just update all the files in B I suspect that there could also be some missing registry entries that may be required to allow it to work properly. Edmonton, AB, Canada Registered: Live Migration Network Configuration Guide http: It is my belief that missing registry entries are teqming obstacle.

Oct 5, Posts: We call that helping us to help you – and we like that a lot! This site uses cookies for analytics, personalized content and ads.


But when we enabled NIC-teaming, the server started rebooting itself atleast once a day, removing NIC-teaming stopped it. What about in the Hardware Ids selection? Please login or register. We build every server from a ghost image but nonetheless on basically every model of HP server we have at one time or another the NIC labeled as ” 1″ on the back of the server comes up as NIC 2 in Windows.

HP DL380 G5 NIC identification problem with Win2003

Lawrence TechNet Community Support. Attempting change is of your own free will.

You must login or register to post a reply. Apr 24, Posts: The host unmanagable comes up everythime, but I have tried the beta workaround Running Local Server Manager as Administrator was exactly the same. Jun 14, Posts: