Here's what I do to copy a VM between one ESX servers local storage to another. You can also just shut it down and do a cold Migrate in Virtual Center which is easier (see Chapter 14 in Admin guide http://www.vmware.com/pdf/vi3_admin_guide.pdf )

- Create subdirectory for new server

login as: root
root@ServerA's password:
[root@ServerA root]# cd /vmfs/volumes/ServerA-Local
[root@ServerA SerervA-Local]# mkdir VM-04

- Use scp to copy files from source server to destination server.

login as: root
root@ServerB's password:

[root@ServerB root]# cd /vmfs/volumes/ServerB-Local/VM-04
[root@ServerB VM-04]# scp *.* root@ServerA:/vmfs/volumes/ServerA-Local/VM-04/
root@ServerA's password:
VM-04-flat.vmdk 100% 18GB 15.8MB/s 19:24
VM-04.nvram 100% 8664 5.0MB/s 00:00
VM-04.vmdk 100% 338 85.1KB/s 00:00
VM-04.vmsd 100% 0 0.0KB/s --:-- ETA
VM-04.vmx 100% 1372 711.9KB/s 00:00
VM-04.vmxf 100% 250 148.4KB/s 00:00
vmware-1.log 100% 37KB 11.4MB/s 00:00
vmware.log 100% 18KB 5.8MB/s 00:00
[root@ServerB VM-04]#

- Delete the sub-directory that you moved to the destination server

It also lets you resize partitions inside a VMDK when required.

FastSCP is OK, but I don't really find it any faster than normal SCP. However, it works and is easy to use, and doesn't require you to go to the command-line. I used VMware converter, and it was fine for moving VM's.

I'd stay with VMConvertor. Yes, it copies, which can be a huge asset, but you also have the option to make tweaks such as changing the name, and etc..

That should be adequate, you might have a duplex/speed mismatch that would cause that. Make sure your host NIC and the physical switch are set the same.

If you are using SCP or cold migration it uses the Service Console NIC.