VMware Cloud Community
sphar
Contributor
Contributor

ESX6 VMs lost connectivity (Windows Server 2012 R2 and VMXNET3 NICs)

Hi All,

Has anyone also experienced an issue with ESX 6.x VMs where some but not all Server 2012 R2 workloads:

  • Loose their active network connection object in Network and Sharing Center
  • Cannot be pinged
  • The static IP configuration disappears (reverts to DHCP)
  • The VMXNET3 adapter is visible in Device Manager
  • The System Log of Event Viewer reports:
    1. Isatap interface isatap.{534E7BEC-57CF-41F0-80CD-256175FAB38D} is no longer active.
    2. The reason specified was: 0x40030011 [Operating System: Network Connectivity (Planned)]
    3. The TCP/IP NetBIOS Helper service was successfully sent a stop control.
    4. The TCP/IP NetBIOS Helper service entered the stopped state.
    5. 6to4 interface 6TO4 Adapter is no longer active.
    6. NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)
    7. The TCP/IP NetBIOS Helper service entered the running state.

VMXNET3 power management is enabled on *all* Server 2012 R2 workloads (checkboxes ticked "Allow the computer to turn off this device to save power", "Allow this device to wake the computer", “Only allow a magic packet to wake the computer”).

NOTE: According to Microsoft KB article, the NIC power management is for machines that enter sleep mode and shouldn't impact VMs that are online.

https://support.microsoft.com/en-au/help/2740020/information-about-power-management-setting-on-a-net...

The Windows Server 2012 R2 VM's were Hyper-V VMs migrated to ESX6 (with Hyper-V components including hidden devices being removed post migration).

Workaround / Temporary Resolution:

Open Device Manager then remove the VMXNET3 NIC / re-scan for it to be re-installed.

The Ethernet connection was then returned to active.

Manually re-entered static IP/SNM/Gateway/DNS

Based on "The reason specified was: 0x40030011 [Operating System: Network Connectivity (Planned)]"

Disabled VMXNET3 power management on all Server 2012 R2 workloads (checkbox unticked "Allow the computer to turn off this device to save power")

URL Link:

Network randomly drops, The TCP/IP NetBIOS Helper service was successfully sent a stop control. The reason specified was: 0x40030011 [Operating System: Network Connectivity (Planned)]

https://answers.microsoft.com/en-us/windows/forum/windows_7-networking/network-randomly-drops-the-tc...

Reply
0 Kudos
1 Reply
VickyJ
Contributor
Contributor

Hello,

We just experienced this same issue on a Windows Server 2012 R2 VM that was recently migrated from a vSphere 5.5 cluster to a new 6.5 cluster.

Did you find a permanent resolution? Did disabling power management work?

Thanks

Reply
0 Kudos