Template/Clone fails with Network Copy issue - NOT DNS Related

[ctsadmin]

When I try to deploy a VM guest through a Template I get the

"Network copy failed - cannot copy xxxxxx.nvram"

I tried adding the FQDN in the host files on the VC server and the ESX server to no avail.

This problem started when a firewall was added between VC and teh ESX server. Port 902 is open and VC can connect to the ESX server, but I cannot Cold-migrate; Clone or deploy templates to this server.

Are there other ports that need to opened on the firewall between the VC and ESX server?

Thanks,

[Dave_Mishchenko]

See page 183 for the ports you need open: http://www.vmware.com/pdf/vi3_301_201_server_config.pdf

But you problem you have may be related to network name resolution. Are you able to ping your ESX hosts by FQDN and the VC server from the ESX hosts by FQDN?

[ctsadmin]

Yes, I can resolve the names fromthe VC and the ESX server.

The problem did not appear until the firewall was implemented. I got our team to open port 902 so VC can connect to the ESX server, but now migration and deployments from templates do not work to this server.

Does port 8000 need to be opened?