Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Verifying and troubleshooting networking connections that may cause VMware Converter to fail (1006607)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 50406Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Using VMware Converter fails

Unable to complete all of the steps in the VMware Converter conversion wizard

The conversion process fails between 1% and 2%

You receive one or more of these errors:

Unknown error returned by VMware Converter Agent

P2VError UFAD_SYSTEM_ERROR(Internal Error)

Failed to connect

Giving up trying to connect

Failed to establish Vim connection to hostname.domain.com.
Vmacore::Exception: The requested name is valid, but no data of the requested type was found.

Image processing task has failed with MethodFault::Exception: sysimage.fault.IncompatibilityFault

ERROR: Unable to open file %s

[NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server hostname.domain.com failed: The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for

sysimage.fault.FileOpenError

Task failed: P2VError FILE_OPEN_FAILED

Unable to find server

Resolution

For VMware Converter to function correctly, all servers involved in the process must be able to communicate with each other and resolve each other's hostnames to IP addresses. In particular, the source server must be able to communicate directly with both the server running VMware Converter (whether it is installed on a workstation or the vCenter Server), and the destination (ESX/ESXi server).

Ensure that DNS name resolution is working between the source and target servers involved in the conversion.

To ensure DNS name resolution is working between these connections:

Open a command prompt on the source server. For more information, see Opening a command or shell prompt (1003892).

Use this command to test name resolution for each server, using separate commands each time:

nslookup <hostname>

where <hostname> is the host name of the ESX/ESXi host or destination server, or VMware Converter server that you are testing.

If you are unable to resolve the DNS name to the IP address of the server, ensure the servers are registered in your DNS server on the network, or use the local hosts file to manually map the IP address to the DNS name.

If the destination server is an ESX/ESXi host, verify that ports 443 and 902 are open directly between the source server and the ESX/ESXi host. For more information, see Testing port connectivity with Telnet (1003487).

If the source and destination servers are on different non-connected networks, you can enable IP forwarding on the server running VMware Converter to pass traffic from the source to the destination. If VMware Converter is installed on Windows Server, you can use Routing and Remote Access services to accomplish forwarding.

Note: The preceding link was valid as of April 26, 2011. If you find the link to be broken, provide feedback on the article and a VMware employee will update the article.

If the source a virtual machine on an ESX/ESXi server managed by vCenter Server and the destination is a different vCenter Server, the connection may fail. To resolve this, connect the source ESX/ESXi server to the same vCenter Server as the destination.

Note: To reduce the number of variables to troubleshoot and network ports that are required, install VMware Converter on the source and specify an ESX/ESXi host as the destination directly, rather than the vCenter Server, where applicable.

Related Information

For related information, see:

Troubleshooting when VMware Converter fails to complete a conversion of a physical or virtual machine (1006284)

Troubleshooting a virtual machine that fails during preparation when using VMware Converter (1006285)

Testing port connectivity with Telnet
Opening a command or shell prompt
Troubleshooting when vCenter Converter fails to complete a conversion of a physical or virtual machine
Troubleshooting a virtual machine that fails during preparation when using vCenter Converter
VMware Converter で障害を引き起こす可能性のあるネットワーク接続を検証およびトラブルシューティングする
验证可能导致 VMware Converter 失败的网络连接问题并对其进行故障排除

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Converter Standalone

VMware vCenter Converter

Related Versions:

VMware vCenter Converter Standalone 6.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant