Could not complete network copy for file /vmfs/PATH/FILE.vmdk

Products

• VMware vSphere ESXi

Issue/Introduction

• vmkping is unsuccessful when pinging remote ESX host on the vMotion vmkernel interface
• Migration type: Change compute resource. Leave VM on the original storage.
• vCenter recent tasks shows an error for event "Applying Storage DRS recommendations", with the message "Could not complete network copy for the file /vmfs/volumes/<UUID>/<VM Name>/File.VMDK" 
• vCenter vpxd.log has the following error:
  

  vpxd[5887]: Event [82598221] [1-1] [2025-10-21T17:33:42.045594Z] [vim.event.VmDeployFailedEvent] [error] [<username>] [<sitename>] [82597734] [Failed to deploy VM from template <vm-template-name> to <esx-host-name>, <datastore-name> in <sitename>: Could not complete network copy for file /vmfs/PATH/FILE.vmdk]

• Source ESX vmkernel.log has the following error:
  

  Wa(180) vmkwarning: cpu1:5873468)WARNING: VMotionUtil: 832: <UUID> S: failed to read stream keepalive: Connection closed by remote host, possibly due to timeout

• Target ESX vmkernel.log has the following error:
  

  In(182) vmkernel: cpu0:2099851 opID=########)Migrate: 323: nfc: Dest udtUUID = <UUID>, srcIP = <###.###.###.###> dstIP = <###.###.###.###>, encrypted
  In(182) vmkernel: cpu0:2099851 opID=########)MigrateNet: 529: vSphereProvisioning netstack not found. Using default netstack.
  ...
  Wa(180) vmkwarning: cpu12:7478038)WARNING: MigrateNet: 1953: <UUID> D: failed to connect to remote host <###.###.###.###> from host <###.###.###.###>: Timeout.
  Wa(180) vmkwarning: cpu12:7478038)WARNING: VMotionSend: 1210: <UUID> D: failed to create a connection with remote host <###.###.###.###>: The ESX hosts failed to connect over the VMotion network
  In(182) vmkernel: cpu12:7478038)Migrate: 101: <UUID> D: MigrateState: Failed
  Wa(180) vmkwarning: cpu12:7478038)WARNING: Migrate: 257: <UUID> D: Failed: The ESX hosts failed to connect over the VMotion network (0xbad010b) @0x420011edc88f

Environment

vSphere 8.x

Cause

Communication between ESX hosts is blocked in one or more directions on TCP port 902 and TCP port 8000 

Resolution

Ensure Source and Target ESX can communicate over management vmkernel on port 902 and vMotion vmkernel over port 8000. Work with your internal network and security team to ensure these ports are allowed through any firewalls between the two ESX hosts.

For testing you can use tools such as netcat, vmkping, and tcpdump-uw. See the following reference KBs for additional details on usage:

• NetCat: Troubleshooting network and TCP/UDP port connectivity issues on Hosts
• vmkping: Testing VMkernel network connectivity with the vmkping command
• tcpdump-uw: Packet Captures in ESXi using tcpdump-uw

Additional Information

Refer to Port requirements for VMware vSphere ESXi and VMware Ports and Protocols for more information on port requirements for ESX.