I know some VMware, but have admittedly never tried to do what you're doing here, but I do have a thought to share with you.
If I'm not mistaken, your physical ESX host (192.168.20.2) is trying to place a file onto your VM (target_vm). Since that communication is happening over port 443
Client-Peer: 192.168.20.2:443
I'm guessing that the VMware certificates that are perhaps on your VM do not match the domain that those VM's have been added to (or they are not added to a domain). The certificates look to be from 'localhost.localdom':
CN=localhost.localdom
If you don't have a certificate authority in your domain already, perhaps you can quickly create a self-signed certificate for your domain and place it in the appropriate certificate store. You also might want to try some of those other API calls like:
--listds | -S
Maybe they won't require SSL to connect since it's not going over HTTPS? That might validate that the certificates are, indeed, causing your problem?