![vmware vcenter converter standalone agent vmware vcenter converter standalone agent](https://www.how2shout.com/wp-content/uploads/2019/11/Virtualize-a-physical-machine-using-VMware-Workstation-Pro-10-15.jpg)
If source machine cannot access vCenter etc. vCenter and PSC should resolve via FQDN on the source machine which is being converted also.If the source machine is behind NAT then all the TCP and UDP ports (0-65535) should pass through NAT. The firewall should be disabled on the source machine or VM which is being migrated to VMWare infrastructure.Add both of them in etc/hosts file on both source and converter machine.
![vmware vcenter converter standalone agent vmware vcenter converter standalone agent](https://content.spiceworksstatic.com/service.community/p/post_images/0000389743/5e4d9c8c/attached_image/agent.png)
Look at vcenter and ESXi host to determine FQDN even if admins connect to it using IP. Use proxy mode in case source and Vcenter cant talk directly. Basically the VM should be able to resolve PSC and vCenter using FQDN. The machine where converter is installed should use same DNS (may be same AD server) as used by VMWare infrastructure.Disable firewall on VM where converter is installed.After this restart "VMware vCenter Converter Standalone Worker" service.In most cases it improves conversion speed This could be in "Program Files (x86)" or in "C:\Users\All Users\VMware\VMware vCenter Converter Standalone" etc. Fine "converter-worker.xml" in VMWare installation.This can be a different machine or VM from the machine being converted