To enable conversion, the Converter Standalone server and client must be able to send data to each other, to remote machines, and to vCenter Server. Also, the source and destination hosts must receive data from each other. Designated ports are reserved for this communication.

If any of these ports is blocked, the corresponding conversion task fails.

Ports Used When Converting a Powered On Machine Running Windows

Ports Required During Windows P2V contains a list of the ports that must be open during the conversion of powered on source machines running Windows.

Table 1. Ports Required During Windows P2V

Communication Paths

Communication Ports

Notes

Converter Standalone server to powered on source machine

TCP - 445, 139, 9089

UDP - 137, 138

If the source computer uses NetBIOS, port 445 is not required. If NetBIOS is not being used, ports 137, 138, and 139 are not required. When in doubt, make sure that none of the ports are blocked.

Note:

Unless you have installed Converter Standalone server or agent on the source computer, the account used for authentication to the source computer must have a password, the source computer must have network file sharing enabled, and it cannot be using Simple File Sharing.

Converter Standalone server to vCenter Server

TCP - 443

Required only if the conversion destination is vCenter Server.

Converter Standalone client to vCenter Server

TCP - 443

Required only if the Converter Standalone server and client components are on different machines.

Converter Standalone server to the destination ESXi

TCP - 902

Converter server always requires access to ESXi at port 902.

Powered on source machine to ESXi

TCP - 443, 902

If the conversion destination is vCenter Server, only port 902 is required.

If the proxy mode feature is on, port 902 is not required.

Ports Used When Converting a Powered On Machine Running Linux

Ports Required During Linux P2V contains a list of the ports that must be open during the conversion of powered on source machines running Linux.

Table 2. Ports Required During Linux P2V

Communication Paths

TCP Ports

Notes

Converter Standalone server to powered on source machine

22

Used to establish an SSH connection between the Converter Standalone server and the source machine.

Converter Standalone client to Converter Standalone server

443

Required only if the Converter Standalone server and client components are on different machines.

Converter Standalone server to vCenter Server

443

Required only if the conversion destination is a vCenter Server.

Converter Standalone server to ESXi

443, 902

If the conversion destination is a vCenter Server, only port 902 is required.

Converter Standalone server to helper virtual machine

443

Helper virtual machine to powered on source machine

22

Used to establish an SSH connection between the helper virtual machine and the source machine. By default, the IP address of the helper virtual machine is assigned by DHCP. If no DHCP server is available on the destination network, you must manually assign the helper virtual machine an IP address.

Ports Used When Converting Virtual Machine Sources

Ports Required During V2V contains a list of the ports that must be open during the conversion of virtual machines.

Table 3. Ports Required During V2V

Communication Paths

Communication Ports

Notes

Converter Standalone server to Fileshare path

TCP - 445, 139

UPD - 137, 138

Required only for standalone virtual machine sources or destinations. If the computer hosting the source or destination path uses NetBIOS, port 445 is not required. If NetBIOS is not being used, ports 137, 138, and 139 are not required. When in doubt, make sure that none of the ports are blocked.

Converter Standalone client to Converter Standalone server

TCP - 443

Required only if the Converter Standalone server and client components are on different machines.

Converter Standalone server to vCenter Server

TCP - 443

Required only if the conversion destination is a vCenter Server.

Converter Standalone server to ESXi

TCP - 443, 902

If the conversion destination is a vCenter Server, only port 902 is required.