UltraVNC Viewer unable to connect to the host: Password requested

[ValeriiVozniuk]

Hi,

I have an issue with UltraVNC Viewer being unable to connect to the oVirt VM. After providing server:port in the UI, and pressing Connect, Viewer tries to connect, in main window I see "Status: Password requested", and then I'm getting an error window with message:
"Handshake cannot be completed. The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context (0x90320)".
There was no prompt to enter the password, and I don't see anything related in UI to enter password beforehand.
I don't have the control over server, so cannot change the parameters on it, and connect address/credentials are generated by oVirt engine on the fly.
Any ideas, what is wrong here, and how I can connect to the VNC on a VM there?
I'm using the latest 1.5.0.4-dev build.

[sandeepshenoyh]

We had same issue, try to rest the local password and try again.

[ValeriiVozniuk]

Local password of what?

[sandeepshenoyh]

yes, the local password

[jose94752]

May be it's an SSL Error. Try to disable encryption on client machine and check if this that and test it on server on your LAN (you disable encryption on server for the test). Repair your encryption configuration after that if it's the problem.

[wqweto]

@ValeriiVozniuk Can you get a log file of the failed connection?

[ValeriiVozniuk]

@ValeriiVozniuk Can you get a log file of the failed connection?

Here it is with loglevel 10, unfortunately nothing new there

Started and Winsock (v 2) initialised
bufsize expanded to 4352
Registered connection with app
Saving to C:\Soft\UltraVNC\options.vnc
DPI 96
Connected to OVIRTSERVER.LOCAL port 5904
DSMPlugin not enabled
RFB server supports protocol version 3.8
Connected to RFB server, using protocol version 3.8
AuthVeNCrypt: Handshake cannot be completed. The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context (0x90320)
Deregistered connection from app
Exiting
VNC viewer closing down

[wqweto]

. . . unfortunately nothing new there

Of course there is new info here, e.g. you didn't mention AuthVeNCrypt was involved.

0x90320 is SEC_I_INCOMPLETE_CREDENTIALS while this line in ClientConnectionTLS.cpp logs the error. It appears TLS server requires authentication which is unexpected, error is logged because no client certificate is provided.

Not sure if VeNCrypt supports authenticated TLS at all so this must be some kind of protocol extension, clearly UltraVNC has no explicit provision for this.

It might be possible to add a client certificate to Personal\Certificates in certmgr.msc but for this to be considered automatically we'll have to remove SCH_CRED_MANUAL_CRED_VALIDATION and SCH_CRED_NO_DEFAULT_CREDS flags in call to AcquireCredentialsHandle which is a good idea in principle.

Do you have a client certificate for this oVirt VM? Can you check in certmgr.msc if you have a suitable client certificate already added?

[wqweto]

Btw, reading noVNC console on ovirt.org it looks you are trying to connect with UltraVNC to a WebSocket port which is only supported by noVNC javascript client.

On ovirt's Console Options screen

. . . try selecting Native client option.

[ValeriiVozniuk]

Of course there is new info here, e.g. you didn't mention AuthVeNCrypt was involved.

Because I have no idea about it? :)

Do you have a client certificate for this oVirt VM?

There is no client certificate there, only CA certificate

Can you check in certmgr.msc if you have a suitable client certificate already added?

Yes, I've added that CA certificate to system trusted root, and rebooted system, that didn't help unfortunately.

. . . try selecting Native client option.

It is with Native client :). noVNC is working in browser (after adding CA to browser trusting list), but I'm trying to make native mode working. With native client I'm receiving .vv file for connection, from where I'm taking host/password to connect.
It was working before with Virt Viewer, but after issues on oVirt server, which team responsible for it "fixed", connection is not working, and I'm trying alternative VNC clients to see if it will work.

[Neustradamus]

@RudiDeVos: Have you seen this ticket?