In my test-lab, the problem was IPv6. I have these components:
- ESXi 6.0U1 -host
- vCenter 6.0U1 running on Server 2012R2 VM, top of the ESXi
- All management components installed on that VM
- Server 2012R2 is on workgroup, running DNS-service, static IPv4 -records to vCenter and ESXi
1.) Disable IPv6 -protocol from vCenter nic.
2.) On vCenter, create new DWORD (32-bit) value to the registry:
3.) Disable IPv6 from ESXi
4.) Reboot vCenter and ESXi
After these steps it works. However, this is only workaround. Final fix seems to be create IPv6 -records to DNS.
1 person found this helpful
Guys you can try to disable IPv6 if you are not using it it worked with me like magic
This happened to me with the 5.5 web client and I was able to get around it by logging off the VPN I was connected to.
The error above went away and I was able to deploy a VM with an ovf through the web client.
In my case.. I had same problem when i was trying to deploy OVF on same host whre was installed vcenter.
When i try to deploy OVF from different host, from pc in network.. - everything was working..
Problem was in DNS resolving name (on dns server.. myvcenter host was added properly.. ) - but on host "myvcenter.domain.com" when i ping name - it resolved it on 127.0.0.1 -> ::1 insted of public IP.
I open file C:\Windows\System32\drivers\etc\hosts and add one record :
myvcenter.domain.com -> add mapping to my Public Interface IP
and now i can deploy also OVF from mycenter host.
Deploying the OVA template from a server different than vCenter helped me accomplish the task. Thank you!
If you're not using DNS you need to add entries for vcenter to your hosts file
Disabled IP6 worked for me also.
No consistency on this though:
- Al work done in Workstation 12 with Chrome 56 (the one that works with Integration plugin)
- 2 virtual servers running Win2012R2 with vCenter 6 build 2994041
- vCenter 1 could deploy OVF
- vCenter 2 could not. OVF deploy from other windows-os could deploy on vCenter 2.
If IP6 was disabled on vCenter 2 deployment was possible. If I enabled it again = didnt work.
- Other NICs in virtual machine can also cause trouble. Disconnect.
- Older disconnected NICs can still be shown in Windows and cause confusion. Remove completely.