As chunter already indicated it has something to do with SSL
2013-04-11T09:26:45.495+02:00| vmrc| W110: SSL_IsVerifyEnabled: failed to open the product registry key. Falling back to default behavior: verification on. LastError = 0
2013-04-11T09:26:57.448+02:00| vmrc| I120: CertificateCheck::CheckCertEmbedded: allowSSLErrors: true
2013-04-11T09:26:57.448+02:00| vmrc| I120: CertificateCheck::CheckCertEmbedded: Found the following errors for 10.0.49.151's SSL certificate: {
2013-04-11T09:26:57.448+02:00| vmrc| I120: - 134217859
2013-04-11T09:26:57.448+02:00| vmrc| I120: - The certificate is based on an untrusted root.
2013-04-11T09:26:57.448+02:00| vmrc| I120: - A certificate in the host's chain is based on an untrusted root.
2013-04-11T09:26:57.448+02:00| vmrc| I120: - The host name used for the connection does not match the subject name on the host certificate.
2013-04-11T09:26:57.448+02:00| vmrc| I120: - The host's certificate is self-signed.
2013-04-11T09:26:57.448+02:00| vmrc| I120: }
2013-04-11T09:26:57.448+02:00| vmrc| I120: cui::CertificateCheck::CheckCertEmbedded - thumbprint for "10.0.49.151" OK
2013-04-11T09:26:57.510+02:00| vmrc| I120: cui::vmrc::VMCnx::OnConnectAborted: Connect failed for MOID "vm-708" on "10.0.49.151"
2013-04-11T09:26:57.510+02:00| vmrc| I120: cui::vmrc::VMCnxMgr::EmitConnectionStateSignal: Emitting "disconnected" signal (requested) for MOID "vm-708" on "10.0.49.151" - reason 'A secure connection to the server could not be established'
You have to use a trusted certificate for the console proxy. Buy one, or make your system trust the certificate authority. I would give it a try and import the Root-CA to the Trusted Root CA on the client computer.
For a production/public cloud solution a official certificate is must.