vrmc console disconnected

[vmb01]

I've correctly installed the VRMC plugin on my I.E. 8 browser. When I try to open the console of a VM from the vcloud director 5.1 web gui, the browser opens a new windows , I see the VRMC console in the CONNECTING state but after a while it goes in DISCONNECTED state and I do not see the VM console.

[IamTHEvilONE]

vmb01,

So we are able to produce the console screen, which means the VMRC application is starting in the background.

Then we basically try to connect to the Console Proxy address as specified in the Public Addresses section of vCloud Director (System > Administration).

If we cannot resolve the hostname or communicate with the IP Address it would resolve to, then that's just a general failure to communicate.

If you are using 1 cell, try putting the IP address in the public addresses section instead of a hostname and ensure your desktop can access the IP on port 443.  if IP works, then it's name resolution from your system.

If you are using more than one cell and or a load balancer, can you bypass the load balancer and point to the console proxy IP of only one cell?  if we bypass and it works, it's either the load balancer causing problems or how the certificates were setup.

[vmb01]

Thanks IamTHEvilONE,

I'm using a single cell without any  firewall between my client and my vcloud server, they are in the same subnet.

My client has IP 172.16.0.10

My vcloud cell has 172.16.0.90 for https and 172.16.0.91 for the console.

In the public Addresses section of vCloud Director (System > Administration) I have:

VCD PUBLIC URL https://172.16.0.90/cloud

VCD PUBLIC CONSOLE PROXY ADDRESS 172.16.0.91

VCD PUBLIC REST API BASE URL https://172.16.0.90

When I try to open the console of a VM I have a black screen but the POWER OFF and RESET buttons are working.

Here a copy of the log file located in C:\Users\ADMINI~1\AppData\Local\Temp\2\vmware-Administrator:

2013-03-26T10:31:04.462+01:00| vmrc| I120: Log for VMware Remote Console pid=7916 version=e.x.p build=build-781747 option=Release

2013-03-26T10:31:04.462+01:00| vmrc| I120: The process is 32-bit.

2013-03-26T10:31:04.462+01:00| vmrc| I120: Host codepage=windows-1252 encoding=windows-1252

2013-03-26T10:31:04.462+01:00| vmrc| I120: Host is Windows Server 2008 R2 Standard Edition, 64-bit  (Build 7600)

2013-03-26T10:31:04.119+01:00| vmplayer| I120: VTHREAD initialize main thread 2 "vmplayer" host id 5404

2013-03-26T10:31:04.119+01:00| vmrc| I120: POLL Using the WSAPoll API Implementation for PollDefault

2013-03-26T10:31:04.119+01:00| vmrc| I120: Msg_Reset:

2013-03-26T10:31:04.119+01:00| vmrc| I120: [msg.dictionary.load.openFailed] Cannot open file "C:\ProgramData\VMware\VMware Remote Console\config.ini": The system cannot find the file specified.

2013-03-26T10:31:04.119+01:00| vmrc| I120: ----------------------------------------

2013-03-26T10:31:04.119+01:00| vmrc| I120: PREF Optional preferences file not found at C:\ProgramData\VMware\VMware Remote Console\config.ini. Using default values.

2013-03-26T10:31:04.119+01:00| vmrc| I120: Msg_Reset:

2013-03-26T10:31:04.119+01:00| vmrc| I120: [msg.dictionary.load.openFailed] Cannot open file "C:\ProgramData\VMware\VMware Remote Console\settings.ini": The system cannot find the file specified.

2013-03-26T10:31:04.119+01:00| vmrc| I120: ----------------------------------------

2013-03-26T10:31:04.119+01:00| vmrc| I120: PREF Optional preferences file not found at C:\ProgramData\VMware\VMware Remote Console\settings.ini. Using default values.

2013-03-26T10:31:04.119+01:00| vmrc| I120: Msg_Reset:

2013-03-26T10:31:04.119+01:00| vmrc| I120: [msg.dictionary.load.openFailed] Cannot open file "C:\ProgramData\VMware\VMware Remote Console\config.ini": The system cannot find the file specified.

2013-03-26T10:31:04.119+01:00| vmrc| I120: ----------------------------------------

2013-03-26T10:31:04.119+01:00| vmrc| I120: PREF Optional preferences file not found at C:\ProgramData\VMware\VMware Remote Console\config.ini. Using default values.

2013-03-26T10:31:04.119+01:00| vmrc| I120: Msg_Reset:

2013-03-26T10:31:04.119+01:00| vmrc| I120: [msg.dictionary.load.openFailed] Cannot open file "C:\Users\Administrator\AppData\Roaming\VMware\config.ini": The system cannot find the file specified.

2013-03-26T10:31:04.119+01:00| vmrc| I120: ----------------------------------------

2013-03-26T10:31:04.119+01:00| vmrc| I120: PREF Optional preferences file not found at C:\Users\Administrator\AppData\Roaming\VMware\config.ini. Using default values.

2013-03-26T10:31:04.119+01:00| vmrc| I120: FILE: FileLockDynaLink: Further process validation tools are: available

2013-03-26T10:31:04.119+01:00| vmrc| I120: Msg_Reset:

2013-03-26T10:31:04.119+01:00| vmrc| I120: [msg.dictionary.load.openFailed] Cannot open file "C:\Users\Administrator\AppData\Roaming\VMware\preferences.ini": The system cannot find the file specified.

2013-03-26T10:31:04.119+01:00| vmrc| I120: ----------------------------------------

2013-03-26T10:31:04.119+01:00| vmrc| I120: PREF Failed to load user preferences.

2013-03-26T10:31:04.119+01:00| vmrc| I120: LOCALE windows-1252 -> NULL User=410 System=410

2013-03-26T10:31:04.462+01:00| vmrc| I120: Hostinfo_OpenProcessBits: OpenProcess access bits are 1000.

2013-03-26T10:31:04.525+01:00| vmrc| I120: OBJLIB-LIB : Objlib initialized.

2013-03-26T10:31:04.556+01:00| vmrc| I120: Debug VMX "" not found.  Using standard VMX ""

2013-03-26T10:31:04.556+01:00| vmrc| I120: Stats VMX "" not found.  Using standard VMX ""

2013-03-26T10:31:04.556+01:00| vmrc| I120: vmxFilePath=""

2013-03-26T10:31:04.556+01:00| vmrc| I120: vmxFilePathDebug=""

2013-03-26T10:31:04.556+01:00| vmrc| I120: vmxFilePathStats=""

2013-03-26T10:31:04.634+01:00| vmrc| I120: Host OS: 'Windows Server 2008 R2 Standard Edition, 64-bit  (Build 7600) 6.1.7600', product type '3', suite mask '0x0110'.

2013-03-26T10:31:04.727+01:00| vmrc| I120: Foundry Init: setting up global state (1 poll threads, 0 worker threads).

2013-03-26T10:31:04.727+01:00| vmrc| I120: Vix_InitializeGlobalState: vixLogLevel = 0

2013-03-26T10:31:04.727+01:00| vmrc| I120: Vix_InitializeGlobalState: vixApiTraceLevel = 0

2013-03-26T10:31:04.727+01:00| vmrc| I120: Vix_InitializeGlobalState: vixDebugPanicOnVixAssert = 0

2013-03-26T10:31:04.727+01:00| vmrc| I120: Vix_InitializeGlobalState: vixLogRefcountOnFinalRelease = 0

2013-03-26T10:31:04.727+01:00| vmrc| I120: Vix_InitializeGlobalState: asyncOpWarningThreshold = 1000000

2013-03-26T10:31:04.727+01:00| vmrc| I120: Vix_InitializeGlobalState: enableSyncOpSelection = FALSE

2013-03-26T10:31:04.727+01:00| vmrc| I120: Vix_InitializeGlobalState: enableExternalThreadInterface = TRUE

2013-03-26T10:31:04.727+01:00| vmrc| I120: Vix_InitializeGlobalState: enableVigor = FALSE

2013-03-26T10:31:04.727+01:00| vmrc| I120: LOCALE windows-1252 -> NULL User=410 System=410

2013-03-26T10:31:04.727+01:00| vmrc| I120: VixHost_ConnectEx: version -1, hostType 3, hostName (null), hostPort 0, options 8707

2013-03-26T10:31:04.727+01:00| vmrc| I120: Enabling HTTPS tunnellingvmClientCore::RunEmbeddedVMRC: parent PID: 7236, instance ID: "vmrc-ax-t-{42E1DA42-C352-4560-9C05-E52AF3C8FE93}", modes: 2, messageMode: 2, features: 3

2013-03-26T10:31:04.743+01:00| vmrc| I120: vmClientCore::RunEmbeddedVMRC: eventName = "VMRC_EVENT_vmrc-ax-t-{42E1DA42-C352-4560-9C05-E52AF3C8FE93}", monikerName = "VMRC_MONIKER_vmrc-ax-t-{42E1DA42-C352-4560-9C05-E52AF3C8FE93}", monikerEvent = 37C

2013-03-26T10:31:04.743+01:00| vmrc| W110: IMonikerImpl::vmClientCore::MonikerImpl<class vmClientCore::InvokeMgrDisp>::GetTimeOfLastChange invoked

2013-03-26T10:31:04.743+01:00| vmrc| I120: HOSTINFO 6391030319828 @ 14318180Hz -> 0 @ 1000000000Hz

2013-03-26T10:31:04.743+01:00| vmrc| I120: HOSTINFO ((x * 2343484437) >> 25) + -446357729760171

2013-03-26T10:31:04.868+01:00| vmrc| I120: Setting proxy environment variable: "VMWARE_HTTPSPROXY="

2013-03-26T10:31:04.868+01:00| vmrc| I120: cui::vmrc::VMCnx::Connect: Connect to MOID "vm-68" on "172.16.0.91"

2013-03-26T10:31:04.868+01:00| vmrc| I120: Resolving IP address for hostname 172.16.0.91

2013-03-26T10:31:04.868+01:00| vmrc| I120: Resolved to 172.16.0.91

2013-03-26T10:31:04.930+01:00| vthread-3| I120: VTHREAD initialize thread 3 "vthread-3" host id 7376

2013-03-26T10:31:04.930+01:00| vmrc| W110: SSL_IsVerifyEnabled: failed to open the product registry key. Falling back to default behavior: verification on. LastError = 0

2013-03-26T10:31:19.953+01:00| vmrc| I120: CertificateCheck::CheckCertEmbedded: allowSSLErrors: true

2013-03-26T10:31:19.953+01:00| vmrc| I120: CertificateCheck::CheckCertEmbedded: Found the following errors for 172.16.0.91's SSL certificate: {

2013-03-26T10:31:19.953+01:00| vmrc| I120:   - 134217859

2013-03-26T10:31:19.953+01:00| vmrc| I120:   - The certificate is based on an untrusted root.

2013-03-26T10:31:19.953+01:00| vmrc| I120:   - A certificate in the host's chain is based on an untrusted root.

2013-03-26T10:31:19.953+01:00| vmrc| I120:   - The host name used for the connection does not match the subject name on the host certificate.

2013-03-26T10:31:19.953+01:00| vmrc| I120:   - The host's certificate is self-signed.

2013-03-26T10:31:19.953+01:00| vmrc| I120: }

2013-03-26T10:31:19.953+01:00| vmrc| I120: cui::CertificateCheck::CheckCertEmbedded - thumbprint for "172.16.0.91" OK

2013-03-26T10:31:19.953+01:00| vmrc| I120: cui::vmrc::VMCnx::OnConnectAborted: Connect failed for MOID "vm-68" on "172.16.0.91"

2013-03-26T10:31:19.953+01:00| vmrc| I120: cui::vmrc::VMCnxMgr::EmitConnectionStateSignal: Emitting "disconnected" signal (requested) for MOID "vm-68" on "172.16.0.91" - reason 'A secure connection to the server could not be established'

[vmb01]

Please, can somebody help me? I'm evaluating vcloud without using tha VM console....it's very hard.

[Gabrie1]

Your last log line reads:

A secure connection to the server could not be established

Could you try rebuilding the certificates you are using? And is port 443 available to both IP addresses?

Have you also tried this with firefox?

[vmb01]

Thanks Gabrie,

with ffox the problem (and the log file) is the same, port 443 is opened for both IP addresses, rebuilding the certificates the problem (and the log file) is the same. I really do not know how to solve this problem....

[--Norton--]

Do you have any AV software thats looking for web based malware etc?

I know we had a similar issue with the new version of Sophos blocking the content.

We had to disable the web element of the Sophos AV to get it to work.

[IamTHEvilONE]

is there some mild irony about having Norton in your username, but mentioning Sophos?

[vmb01]

I do not have any AV, any FIREWALL. Nothing.

[vmb01]

Nothing, no AV, no firewall, nothing.

it's a mistery...

[--Norton--]

hehehe nah no link there :smileysilly:

[--Norton--]

All of your machines all time synced with same NTP source??

[vmb01]

I do not have an NTP server in my lab and the VMs are not connected to internet but the vcloud server, the vcenter (that is also my vcloud client), the vcloud vapp VMs  and the esx are synced.

[vmb01]

Please consider that when I try to open the console of a VM I have a black screen but the POWER OFF and RESET buttons are working.

[--Norton--]

Is the screen resolution set too high on the vm???

[vmb01]

it's just 640 x 480

[--Norton--]

I am rapidly running out of answers here. Anyone else ??? lol

It does look like a cert thing from the log you uploaded.

Have you searched on cert based issues??

[--Norton--]

Have you looked at

http://communities.vmware.com/message/1754173

http://serverfault.com/questions/473450/vcloud-vmrc-connection-ssl-error

[vmb01]

Thanks Norton but the links you suggested are referring to a different problem.

Now I've regenerated the certificates, and following the install guide, When keytool asks for your first and last name, I've typed the fully-qualified domain name associated with the IP address you want to use for the console proxy service.

Doing it, from the log files is disappeared the line

The host name used for the connection does not match the subject name on the host certificate.

but the problem is not solved, the log always shows:

2013-04-03T16:42:36.092+02:00| vmrc| I120: CertificateCheck::CheckCertEmbedded: Found the following errors for vcloud-console.syslab.local's SSL certificate: {

2013-04-03T16:42:36.092+02:00| vmrc| I120:   - 134217857

2013-04-03T16:42:36.092+02:00| vmrc| I120:   - The certificate is based on an untrusted root.

2013-04-03T16:42:36.092+02:00| vmrc| I120:   - A certificate in the host's chain is based on an untrusted root.

2013-04-03T16:42:36.092+02:00| vmrc| I120:   - The host's certificate is self-signed.

2013-04-03T16:42:36.092+02:00| vmrc| I120: }

2013-04-03T16:42:36.092+02:00| vmrc| I120: cui::CertificateCheck::CheckCertEmbedded - thumbprint for "vcloud-console.syslab.local" OK

2013-04-03T16:42:36.142+02:00| vmrc| I120: cui::vmrc::VMCnx::OnConnectAborted: Connect failed for MOID "vm-133" on "vcloud-console.syslab.local"

2013-04-03T16:42:36.152+02:00| vmrc| I120: cui::vmrc::VMCnxMgr::EmitConnectionStateSignal: Emitting "disconnected" signal (requested) for MOID "vm-133" on "vcloud-console.syslab.local" - reason 'A secure connection to the server could not be established'

Please, can anybody that is using vcloud 5.1 with self signed certificates,  check if in the log file is present the lines

2013-04-03T16:42:36.092+02:00| vmrc| I120: CertificateCheck::CheckCertEmbedded: Found the following errors for vcloud-console.syslab.local's SSL certificate: {

2013-04-03T16:42:36.092+02:00| vmrc| I120:   - 134217857

The log file I'm referring is located in C:\Users\Administrator\AppData\Local\Temp\2\vmware-Administrator

Thanks

[--Norton--]

I'm not sure they are that different as they also contain the error string

VMCnx::OnConnectAborted: Connect failed for MOID and are Cert related.

It would seem that Certs can give a variety of issues especially with 2 x Cells Load Balanced.

Please make sure you post the fix when you find it as these Cert problems seem to consist of all sorts.

Norton