Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

Converting a virtual machine using vCenter Converter Standalone fails at 1% with the error: "Cannot communicate with the remote host, either due to network errors or because the host is not responding" (56473)

Last Updated: 2/14/2020Categories: TroubleshootingTotal Views: 22521Language:
English

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Symptoms

Converting a virtual machine using vCenter Converter Standalone fails.

Converter task fails at 1%.

In the vmware-converter-worker-X.log file located at C:\ProgramData\VMware\VMware vCenter Converter Standalone\logsyou see entries similar to:

2018-06-05T12:08:41.753-07:00 info vmware-converter-worker[02332] [Originator@6876 sub=task-10] Got remote helper VM IP addresses as: fe80::250:56ff:fe80:6fe7
2018-06-05T12:08:41.753-07:00 info vmware-converter-worker[02332] [Originator@6876 sub=task-10] Connecting to Converter Helper on fe80::250:56ff:fe80:6fe7:443 over TCP/IP over SSL
2018-06-05T12:08:41.753-07:00 info vmware-converter-worker[02332] [Originator@6876 sub=task-10] Connecting to Converter Helper with retry, retryCount 600, interval 1, times left 600
2018-06-05T12:08:41.753-07:00 warning vmware-converter-worker[01320] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x022d8b18, h:2604, <TCP '0.0.0.0:0'>, <TCP '[fe80::250:56ff:fe80:6fe7]:443'>>, e: system:10051(A socket operation was attempted to an unreachable network)
2018-06-05T12:08:41.753-07:00 error vmware-converter-worker[01320] [Originator@6876 sub=HttpConnectionPool-000000] [ConnectComplete] Connect failed to <cs p:0216be60, TCP:[fe80::250:56ff:fe80:6fe7]:443>; cnx: (null), error: class Vmacore::SystemException(A socket operation was attempted to an unreachable network)
2018-06-05T12:08:42.760-07:00 info vmware-converter-worker[02332] [Originator@6876 sub=task-10] Connecting to Converter Helper with retry, retryCount 599, interval 1, times left 599
2018-06-05T12:08:42.760-07:00 warning vmware-converter-worker[01456] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x060a5590, h:2844, <TCP '0.0.0.0:0'>, <TCP '[fe80::250:56ff:fe80:6fe7]:443'>>, e: system:10051(A socket operation was attempted to an unreachable network).

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs when the helper virtual machine is getting automatically assigned an IPv6 address, while the environment is not configured for IPv6.

Resolution

To resolve this issue, disable IPv6 and assign static IPv4 address. For more information, see the Configure the Network for the Helper Virtual Machine section of the VMware vCenter Converter Standalone User's Guide.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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

Support Assistant