Here are some steps that we need to do to confirm connection between the source and destination machine.
Check basic network:
· ping from source system to VC host
· ping from VC to ESX target system
· ping from source system to ESX target system
· ping from ESX target system to VC host
· ping from ESX target to source system
Check the port usage (use telnet to verify):
· Converter application to remote physical machine - 445 and 139
· Converter application to VirtualCenter Server - 443
· Converter application to ESX Server 3.x - 443
· Physical machine to VirtualCenter Server - 443
· Physical machine to ESX Server 3.x - 443 and 902
Check credentials and privileges:
· Ensure that each username can login to all systems (you may want to create one admin account on all systems to simply the testing)
· Ensure the user has permission to create a VM on the target system
· Ensure the user has access to LUNs on the target system
· Ensure the user has write privilege on target system storage devices
· Verify that the user can create a new VM on each target system from VirtualCenter
Verify space requirements:
· Check available file space on all systems (Depending on your method you will either need space equal to the selected drive or to the space used on the source drive.)
· Verify that the Target VMname does not exist on target system
· Optionally, turn firewall off on 3.0.1 ESX servers
Try the following steps:
1) Log onto the source machine using local admin privileges
2) Install VMware Converter on the source machine
3) Run VMware Converter
Make sure you do not have any software mirror or software raid on your disks.
If it still fails, please provide the following information by attaching the documents (please do not paste them):
1) What percentage did it fail at?
2) Logs - File - Export Log (from within converter)
3) Screen shot of the disk management screen