During the process of deploying an OVF (Log Insight in this example) using the vSphere Web Client running on a local windows vCenter instance, I encountered the following error: ‘A […]
During the process of deploying an OVF (Log Insight in this example) using the vSphere Web Client running on a local windows vCenter instance, I encountered the following error:
‘A connection error occurred. Verify that your computer can connect to vCenter Server.’
First step was to perform some basic ping tests of the vCenter FQDN, the results indicated that my vCenter host name was resolving to IPv6:
My next step was to disable IPv6 on the adapter:
Testing Ping again proved that by just disabling the checkbox on the adapter is not sufficient, even adding a host file entry did not remediate the name resolution:
This resulted in editing the registry to fully disable IPv6 on my vCenter machine:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip6\Parameters] “DisabledComponents”=dword:000000ff
Note: After creating the reg key a reboot the machine is required. If this is a production environment please ensure no other users or systems are impacted if rebooting your vCenter.
Name resolution complete for IPv4 Success!:
Now I can continue with deploying my OVF:
Note: I had to remove and reinstall the VMware Client Integration Plug-in 6.0.0 after making these changes.