FINALLY

I believe I solved this issue at least for me.

It all came down to two things

1. FQDN
a. I used FQDN’s for everything. The target server and I used my virtual center server for the Source machine. From there I selected my ESX server group/server
b. Make sure that your esx server have a A record in your DNS, as well as your Virtual Center and Converter. For me they are the same box. I took it a step further and I added the servers to the respective host files ( not the ESX server) Physical box got the VC server (FQDN) and the other way around
2. PORTS ( The fix)
a. This was basically my stumbling block for me
i. Make sure you have the following ports open both ways for the IP for your Converter, VC, ESX and the machine your trying to clone.
ii. IP for Converter to IP for remote machine (Physical) port 455 – 139
iii. IP for Converter to IP for Virtual Center – port 902 (Note: For me this wasn’t an issue since I installed Converter on my VC server.)
iv. IP for Converter to IP for ESX Server – port 902 (Note: For me this wasn’t an issue since I installed Converter on my VC server.)
v. IP for Physical to IP for VC & Converter – port 902
vi. IP for Physical to IP for ESX server – port 902 – This is what fixed it for me. I had everything setup except for this one. Once I got this one put in it worked.

Hope this helps. Three days of head knocking, bone crushing, hair pulling fun just to get to the point!!!!!

Later

This doesn't help me either. I have used FQDN and IP addresses instead of names. I have all services shut down except the basic ones necessary for network communication. I have no firewall blocking issues on any ports. I wish the logs at least hinted at the problem.

I am having a problem like this. It looks like the same problem. I am trying to import my old Toshiba laptop which is running Windows XP Pro onto my server which is running Windows Server 2003. I have the simple file sharing turned off. There is no anti virus or firewall software running on the laptop or the server. The only firewall on the network is where the Internet comes into the network.

The files are being created in the network share and it does show that the files are of the size I've specified, but this could just be VMware Converter on the server telling the files to be that size, at least that's what I'm guessing.

I got to thinking a moment ago that maybe if I ran VMware Converter under the server's administrator account instead of my account which has Administrator privileges it might work, but it didn't.

I installed VMware Converter onto the laptop to see if I could simply create the image on there, but, got the same error message. I first tried to save the files onto the local hard drive of the laptop and I tried to have them put onto the network share. Either way, it still failed when it got to 97%.

Hello everybody,

we have the same problem.

Source system is a windows 2003 server.

VMWare Converter is installed on a virtual machine.

We had the following settings:

Target: VMWare Server
VMWare Converter installed on an additional machine.
Hot cloning
resize the disks
growable
we used FQDNs whereever possible.

We now try it with VMWare Converter installed on the source hardware itself.

Regards,

Rigas