E1000e Windows 10

[John555444]

Hi,

I had a Windows 10 2016 LTSB client that lost internet connectivity. It was using the default E1000e adapter, but I have now changed to vmxnet3. Are there known problems with the E1000e on Windows 10 as there was on Server 2012/Windows 8?

[asajm]

Hi John555444​

what is your virtualized environment version?

vmxnet3 is recommended

[Alex_Romeo]

Hi,

The problem of Vmxnet3 drivers in Windows Server 2012 was related to the wrong version of vmware tools, which was later solved:

VMware Tools version 10.3.0 has been deprecated due to a problem with the VMXNET3 driver.

Article KB 57796 (VMware Tools version 10.3.0 Recall and alternative solution tips) describes the problem (very serious because it leads to the blocking of hosts), the cause, but above all when it can occur.

At the moment it seems that the problem only occurs with these conditions (all necessary):

Hosts the vSphere ESXi 6.5VM version 13 hardware (the latest on ESXi 6.5) Guest operating system Windows 8 / Windows Server 2012 or later VMware Tools 10.3.0 installed in VMS guests Email card VMXNEX3

The VMXNET3 virtual network card driver could cause ESXi to shut down (yes, the host, not just the VM) with its Purple Diagnostic Screen (PSOD) or simply cause intermittent network problems in the VMs.

E1000e – This is emulated version of the Intel 82574 Gigabit Ethernet NIC. E1000E is the default adapter for Windows 8 and Windows Server 2012. But installing VMware tools in those systems changes this adapter type and installs VMXNET3.

VMXNET – you must install VM tools in order to use this network adapter type in your environment. It's an older version.

VMXNET2 – It's an enhanced version of VMXNET, and allows high-performance, has support for jumbo frames and hardware offloads. Still older card though.

VMXNET3 – latest, also called paravirtualized NIC which is the most performant and most advanced virtual NIC. Has everything you can find in VMXNET2 and provides multi-queue support (Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery.

On the new version of vSphere 6.7 there were no driver problems. You can also use VMXNET3 on Windows 10

Alessandro Romeo

[John555444]

The machine that had this problem is on a version 6 host (can’t go higher). Most of my hosts are on 6.7.

The issue was with the e1000e nic. I have now changed it to vmxnet3.....

[Alex_Romeo]

Perfect! I also always use VMXNET3

Alessandro Romeo

[TheBob1]

Dear all,

i have the same problem with one of our Win10 2004 Client based on latest ESXi 6.7 Version.

The VM is a Veeam Backup VM i have several Network Interupts:

Antwort von 192.168.1.111: Bytes=32 Zeit=9ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=14ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=10ms TTL=125

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Antwort von 192.168.1.111: Bytes=32 Zeit=2270ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=50ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=9ms TTL=125

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Antwort von 192.168.1.111: Bytes=32 Zeit=1784ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=8ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=39ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=49ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=9ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=9ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=8ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=9ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=18ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=8ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=9ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=9ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=9ms TTL=125

Antwort von 192.168.1.111: Bytes=32 Zeit=9ms TTL=125

Ping-Statistik für 192.168.1.111:

    Pakete: Gesendet = 1724, Empfangen = 1443, Verloren = 281

    (16% Verlust),

Ca. Zeitangaben in Millisek.:

    Minimum = 7ms, Maximum = 3906ms, Mittelwert = 21ms

STRG-C

The Ping Time is in this case a little bit higher do to VPN Connection. Internam i have same timout but under 1ms delay.

I have changed the card from e1000e to VMXNET 3 and before i have two card one wtih internal com on E1001e and vmxnet3 to SAN Storage.

I have also activate this registry settings:

MaxUserPort = fffe

TcpMaxDataRetransmissions = 5

TcpNumConnections = fffffe

TcpTimedWaitDelay = 1e

VMWareTools: Wird ausgeführt, Version:11265 (Aktuell)

All other VM's, some on same VLAN, have no problem

The VM is up and running since several Month but i get this problem starts on Weekend.

Has anybody the same problem or can help us?

wrbrgds

TBC

[TheBob1]

another INformation, if the timeout occures the VM is also not managed via VMWare Remote Conole or WebXConole. I get the Sceen but no action like login or any other input are possible.

[DStranz]

John,

I have exactly the same issue. Windows 10 x64 ver 2004, E1000 = unstable network,

vmxnet4 works fine

[Lalegre]

Hello folks,

To all who are facing issues with the vNICs and which network card to use always search on the VMware Compaitibility Matrix from the "Guest OS" section where it will show you the support for all the devices and also the recommended by VMware: VMware Compatibility Guide - Guest/Host Search

Here is an example with Windows 10 as it was the mentioned with the issue in the post and you can clearly see that it recommends to use VMXNET3 even the E1000e type is supported: VMware Compatibility Guide - Guest/Host Search. However you will see for example that the E1000 is not supported, that is why you should always check this first regarding any new OS you are planning to deploy.

Regards and hope you all fix your issues!

[nachogonzalez]

Hey hope you are doing fine
Since there was several issues with Windows 7 and Windows server 2008 using E1000 Nics i've insisted on all customers having VMXNET3 nics.
I have seen issues between win 10 and E1000

Warm regards