Remove From My Forums. The HP Hardware team could not repro the issue in their labs, however they were using the 8 core processors as these are the only ones that are certified for Server But if I have any further updates on this I will post back here. I start the server and ports are working, port 4 is not. Enabled Ethernet adapter Port 4: Vista W7 Driver Date: Tuesday, April 16, 1:

Uploader: Taular
Date Added: 10 January 2017
File Size: 35.74 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 89506
Price: Free* [*Free Regsitration Required]

HP Ethernet 1Gb 4-port 331i Adapter, list of drivers

Sign in to vote. To test this I patched in one of the 8 NICs I was reserving to be used as a virtual switch, and selected this when adding the Hyper-V role.

This solution comes at a price though, as we’re losing 48 logical processors per server: After some further testing this morning the NICs are once again losing connectivity, so back to the drawing board I guess. If not, use tracert 4.

By continuing to browse this site, you agree to this use. HP software and our Microsoft support team are concerned that this is looking like it will be passed to them, without fully being tested, and they’ll ehhernet having to sift through thousands of log files only to determine that is indeed a driver issue, in which case it will be passed back to HP Hardware Enabled Ethernet adapter Port 3: So in the end once I’d got ethsrnet patched in and added my virtual switches, there probably wouldn’t been a problem anyway.


VMware Compatibility Guide – I/O Device Search

The driver and firmware versions are exactly the same as the server that currently works. OK so here’s an update from this afternoons tests: These servers are to take over our current Hyper-V production cluster, and will bridge two sites, so it’s vital that these NICs are stable.

There may be a relationship problem with Hyper-V trying to interact with a NIC and the driver, causing communication problems for the host. In addition, you can find a driver for a specific device by using search by id or by name. This behavior is also not restricted to just the on-board NICs, I have tested across the on-board NICs and the 4-port cards, and every time the ethsrnet fails.

Audio facilities are ensured by the integrated 7.

Select your language

Solid State Drives Crucial v4, informal shipments of which began in May, the day before were added to the price lists of dozens online stores across Europe, as well as clearly stated on the website crucial. How was this found? I need to run some more tests to feel confident that this has resolved the issue, but it’s looking good.

It seems these servers do not work with Hyper-V on Server dthernet Network facilities are backed by a separate gigabit Realtek GR controller. Vista64 W7x64 Driver Date: This site uses cookies for analytics, personalized content and ads.

I’m going to describe the issue as best as I can, but it’s extremely odd to say the least We have shown them numerous tests, which point to it being a problem with their driver. Ethdrnet NIC that fails, is always the fourth to be enabled. Hi, Thanks for sharing your experience! OK, finally we had to swap out the 10 core processors for the 8 core variants, and this solved this issue.


Quite the contrary, both GPUs differ from the etalons, chiefly due to the integration of Gaming App brand utility; the latter enables GPUs to run in one of three available pkrt We can now see both adspter clearly display the issue, and is easily replicated.

Have a nice day! But all in good time.

Hyper-V in Server – Strange NIC issues

Andrew France – http: Although these NIC issues seem to disappear once they are made into virtual switches, these 4 on-board NICs are critical for the running of the host server itself. It’s also stopping access from the host to the elected NIC.

Drivers are the property and the responsibility of their respective manufacturers, and may also be available for free directly from manufacturers’ websites. Currently HP Hardware are looking at this 331 slowly, and erring towards it being an OS issue not hardware.