Windows VM lost network connectivity
search cancel

Windows VM lost network connectivity

book

Article ID: 401708

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Multiple Windows VM experience network connectivity issues.

  • VM cannot ping to its own gateway or any other VMs in its own VLAN/network.

  • Packet capture at VM vSwitch port ID notices no traffic being received.

  • The following error is reported in the /vmfs/volumes/<datastore>/<vm-name>/vmware.log for the problematic virtual machine: 

YYYY-MM-DD-T06:53:32.739Z Wa(03) mks - SOCKET 96555 (234) unable to determine remote IP address
YYYY-MM-DD-T06:53:32.739Z In(05) mks - SOCKET 96554 (234) AsyncTCPSocketSetOption: SendLowLatencyMode set to [1].
YYYY-MM-DD-T06:53:32.739Z In(05) mks - SOCKET 96555 (234) Creating VNC remote connection.
YYYY-MM-DD-T06:54:36.016Z In(05) mks - SOCKET 96554 (234) recv detected remote shutdown
YYYY-MM-DD-T06:54:36.016Z In(05) mks - SOCKET 96555 (234) VNC Remote Disconnect: socket closed.
YYYY-MM-DD-T06:54:36.016Z In(05) mks - SOCKET 96555 (234) Sending websocket close frame, status code = 1000
YYYY-MM-DD-T06:54:36.016Z In(05) mks - SOCKET 96554 (234) send error 32: Broken pipe
YYYY-MM-DD-T06:54:36.016Z In(05) mks - SOCKET 96555 (234) VNC Remote Disconnect: socket closed.
YYYY-MM-DD-T06:54:36.016Z In(05) mks - SOCKET 96555 (234) MVNCBackend: Spurious socket error?

  • Windows Guest OS triggered Windows event ID "16002".  Windows VM --> Run --> Event Viewer 

  Event ID: 16002 closing a UDP socket with local port number #### in process #### is taking longer than expected. 
  The local port number may not be available until the close operation is completed. This happens mainly due to misbehaving of network drivers. 
  Ensure latest updates are installed for windows and any third-party networking software including NIC drivers, firewalls, or other security products

 

Environment

VMware vSphere ESXi Host 7.x

VMware vSphere ESXi Host 8.x

Windows Virtual Machines

Cause

Outdated VMware tools fails to process the network traffic efficiently at vNIC level therefore causing the failure in network connectivity.

Resolution

Additional Information

Overview of VMWare tools : Reference KB 315382

To run packet capture at the VM switch port level, refer to the KB Packet capture on ESXi using the pktcap-uw tool