Updating the host file fixed it for me. The two domains didn't have DNS resolution though so that is why.
Hi Gibson, I got the issue before, to fix this you have to make sure the following > Firewall have to be disabled for both Converter Host Server, Destination Server and Source Server > vCenter Port (443) and ESXi Port (902) should be allowed in the Firewall > Update your Host File putting all the Host Name and Its IP of the Destination and vCenter Converter Server to Source Server > Update your Host File putting all the Host Name and Its IP of the Source to vCenter Server > Make sure Anivirus for both Source and vCenter Converter server/host is disabled. In some cases, Any antivirus will unexpectedly close/block the connection. *** Source (Can be Physical or Virtual) *** Destination (Your ESXi Host/DataStore) Let us know if it works. Good Luck Man! Keep Virtualizing! Regards, JOf
Yes, this worked for me
For me this was firewall port blocking, opened up a rule to allow it and it worked.
I also corrected the DNS before that, but didn't fix it entirely.
Setting the task to run in proxy mode seems to have sorted out the issue for me too.
My problems were compounded by:
1) My PC had multiboot option, where it would boot into a Media Player mode (which refused to copy out.)
2) My UAC settings had to be stepped down to "Do not Notify"
3) My Remote Access had to be "less secure"
4) My firewalls had to be disabled.
5) And the one which is most relevant to the thread, is "If your vCenter server has to be accessed via VPN, then the VPN has to be UP on your Source Machine."
Or it fails with the error above....
Enjoy, and I hope my reply was helpful!
Great! You saved my life (and my weekend too)