Here is the error you are getting:
2012-07-30T10:15:25.278+02:00 [07388 warning 'Default'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Failed to connect to server 192.168.0.101:902 2012-07-30T10:15:25.278+02:00 [07388 info 'Default'] [,0] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338) 2012-07-30T10:15:25.278+02:00 [07388 info 'Default'] [,0] Error 2338 opening disk ha-nfcssl://[NAS01-vms01] UCBB01WS01/UCBB01WS01.firstname.lastname@example.org:902!52 15 94 be f7 e3 d5 1a-b3 14 01 36 9b df 1f 98.
In general it means there is no network connectivity between the physical source server and the target ESX host. In most cases it means either a DNS problem (not able to resolve the ESX name, which is not your case since you are using an IP address) or a firewall does not allow connections from the source machine to port 902 on the target ESX host.
Converter still needs direct access to ESX host for actual data transfer. You can pick vCenter in the wizard and select the appropriate host/cluster, resource pool and so on, but in the end when it comes to data traffic Converter Agent (on the source) is trying to connect directly to the target ESX host. Otherwise it would burden the VC server too much to act as a proxy for the data channels.
Im not very sure about having direct acces.. but i strongly feel that if you enable port for P2V it should work like a charm, follow the below link FYI