OPERATIONAL DEFECT DATABASE
...
...
You may receive these errors, which can indicate blocked ports: Unable to contact the specified hostThe host is not available, there is a network configuration problem, or the management services on the host are not respondingFailed to connect to peerError: Failed to connect to serverThe operation failedIncorrect user credentialsUnable to SSH to the source machinePlease check if a firewall is blocking access to the SSH daemon on the source machineFailed to clone the volumeUnable to connectFAILED: The request refers to an unexpected or unknown typeFailed to connect ISO image to remote VMFAILED: unable to obtain the IP address of the helper virtual machinessh: Could not resolve hostnameName or service not knownFAILED: An error occurred during the conversionUnable to obtain IP addresss of helper virtual machineA general system error occurred: unknown internal errorA file I/O error occurred while accessing
This article describes the ports required to be open for VMware vCenter Converter.Following the article and ensuring the ports are open ensures that common firewall configurations in your environment are compatible with Converter.
VMware vCenter Converter fails if one or more required ports are blocked. Follow the section that matches your conversion scenario. In this article, these terms are used: Source computerThe physical or virtual machine that is being converted.Converter serverThe server portion of VMware vCenter Converter. In a typical installation, both the Converter server and Converter client are installed at the same location. By default, this is the installation method that is used.Converter clientThe client portion of VMware vCenter Converter. In a custom installation, the Converter client can be installed to a different computer than the Converter server.VirtualCenterThe VirtualCenter computer that is being used as the conversion destination, if such was chosen.ESXThe VMware ESX host that is being used as the conversion destination, if one is chosen, or the ESX host that is hosting the target virtual machine.Fileshare pathThe path to a virtual machine's .vmx file, if the source is an existing or standalone virtual machine, or the path to a directory if the destination is to be a standalone virtual machine.Standalone virtual machineA virtual machine that is being managed by a VMware product other than VMware ESX.Helper virtual machineWhen converting a powered on Linux operating system (P2V), this is the target virtual machine that is being used temporarily for the purpose of copying files from the source computer. It uses the TCP/IP information that is entered in the Converter wizard for the target virtual machine. Ensure that this IP address can communicate directly with the source computer. Notes: If you perform a corrective action, determine if the problems initially encountered are still being experienced.To test port connectivity, do so from a command or shell prompt. For more information, see Opening a command or shell prompt (1003892).To test TCP port connectivity use the telnet command. For more information, see Testing port connectivity with Telnet (1003487).To test UDP port connectivity from Linux or MacOS use the traceroute command. For more information, see a traceroute man page.To test UDP port connectivity from Windows use the Portqry utility. For more information, see the Microsoft Knowledge Base article 310099.For powered-on Windows conversions to vCenter destinations, Proxy Mode feature in Converter 6.0 is introduced. By selecting this option, no direct connectivity is required from the source machine to the destination ESX host. Note: The preceding links were correct as of March 15, 2009. If you find a link is broken, provide feedback and a VMware employee will update the link. Converting a powered on Windows operating system (P2V) Source Destination TCP Ports UDP Ports Notes Converter server Source computer 445, 139, 9089 or9090 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. If in doubt, ensure that none of the ports are blocked. Port 9089 is used for Converter Standalone versions,and 9090 isused for the Converter plugin. Note: Unless you have installed Converter server to 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 server VirtualCenter 443 Only required if the conversion target is VirtualCenter. Converter client Converter server 443 Only required if a custom installation was performed and the Converter server and client portions are on different computers. Source computer ESX/ESXi 443, 902 If the conversion destination is vCenter Server, only port 902 is required from the source to the ESX/ESXi host management IP. Converting a powered on Linux operating system (P2V)Note: These are the default ports. If custom ports were used when installing vCenter Server, these will need to be changed to match your environment. Source Destination TCP Ports Notes Converter server Source computer 22 The Converter server must be able to establish an SSH connection with the source computer. Converter client Converter server 443 Only required if a custom installation was performed and the Converter server and client portions are on different computers. Converter server VirtualCenter 443 Only required if the conversion target is VirtualCenter. Converter server ESX/ESXi 443, 902, 903 If the conversion destination is vCenter Server, only port 902 is required from the source to the ESX/ESXi host management IP. Converter server Helper virtual machine 443 Helper virtual machine Source computer 22 The helper virtual machine must be able to establish an SSH connection with the source computer. By default the helper virtual machine gets its IP address assigned by DHCP. If there is no DHCP server available on the network chosen for the target virtual machine you must manually assign it an IP address. Converting an existing virtual machine (V2V)Note: These are the default ports. If custom ports were used when installing vCenter Server, these will need to be changed to match your environment. Source Destination TCP Ports UDP Ports Notes Converter server Fileshare path 445, 139 137, 138 This is only required 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. If in doubt, ensure that none of the ports are blocked. Converter client Converter server 443 Only required if a custom installation was performed and the Converter server and client portions are on different computers. Converter server VirtualCenter 443 Only required if the target is VirtualCenter. Converter server ESX/ESXi 443, 902 If the conversion destination is vCenter Server, only port 902 is required from the source to the ESX/ESXi host management IP.
For translated versions of this article, see: Español: Puertos de VMware vCenter Converter requeridos (2033057)Português: Portas necessárias do VMware vCenter Converter (2032593)日本語: 必要な VMware vCenter Converter のポート (2078649)简体中文: 需要使用的 VMware vCenter Converter 4.x/5.x 端口 (2081918) Testing port connectivity with TelnetOpening a command or shell promptPortas necessárias do VMware vCenter ConverterPuertos de VMware vCenter Converter requeridos必要な VMware vCenter Converter ポート需要使用的 VMware vCenter Converter 4.x/5.x 端口
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
