Embedded VNC fails to start

Hello,

As I understand, your VNC sessions we're working 2 days ago and now they doesn't. Is this correct?

Do you have something relevant in Help -> Application Logs?

Best regards,

Yeap, 2 days ago was working fine. Nothing unusual in logs.

But i managed to find rather unexpected solution - if i switch interface language from Russian to English - no issues, switch back - not working again. It is reproducible on two separate machines with Win 7 Pro and Win 10.

Hi!
Same problema here, but as a new user on Win 10 64 Bits. VNC refuses to open sesión. I've tryied changing language but now success with that.
any other ideas?

Hello,

Thank you both for your feedback.

I will assign this thread to our QA department so that they can try to reproduce internally.

Best regards,

Hi again,
I have fresh updates on this issue. It's quit wierd, but i gonna explain my whole process just to see if we can work it out.
I' ve been using RDM-Free on my Win 7 32 bits. I've just installed Win 10 64 bits and RDM 4.6.0.0 64 bits to use same connections database that i already have. On that database there are several vnc connections stored with the "default" option on VNC application setting.
On this fresh installed computer i couldn't connect with that stored connections (as i stated before), so i tryed installing Ultravnc viewer 64bits (that was not installed on he new system).
Then the setting that was on "default" for VNC application, changed on all connections to UltraVnc, but connections still refused to open. Then i changed that value to Default and they started working.
It doesn't make much sense for me, but it was the only setting that was changed, as i already discarded AV (Bitdefender) issues.
So now it's working like a charm, maybe you could try to reproduce this steps and get a better explanation for this issue.
Hope this helps.
Regards,

Hello
Same problem here. I have over 20 machines configured for access with VNC, both sever and workstations with different Windows vesions.
All have UltraVNC installed and all worked until 2-3 days ago.
The workaround suggested by Later On works, fortunately (thanks). It seems to be an issue related to UltraVNC.
It should be desirable that RDM would work with UltraVNC again, however.

Hello
UltraVNC keeps not to work in RDM 5.0.3.0
VNC only works if used with default VNC. UltraVNC works only if run as external connection.
Hope that devs will look at this soon or later

Hello,
Is there a reason why you want to use UltraVNC if the default VNC works? This one is our own VNC and it's easier for us to add what is missing or fix issues.

Regards

Hello,
sorry for late reply, but I needed to test a little more for being sure of what I'm saying. And now I'm sure.

Internal VNC has these main lacks, that makes user experience very annoying, especially if you think that UltraVNC would work flawlessly (it does, outside RDM):

• If you leave a connection open for a quite long time keyboard is disabled when you come back to the window.

Whatever you press and digit produces nothing on the remote screen.


• In addition to the above issue, most of the times what you see after some minutes of inactivity on that machine is not the current content of the remote screen, but it's a fixed image of a previous state.
Basically, it looks like the connection is lost after a certain time that you don't interact with the remote computer.

• Caps locks doesn't work the most of times. Never, I'd say

I hope you can soon fix these issues, even if I'd prefer to have UltraVNC working

Currently UltraVNC does not start at all if set to run embedded in RDM.

Hello,

I have reproduced your issue some of your issue. Once the active window looses the focus I cannot get the keyboard focus to switch back into the sessions. So yeah from then. Although when keyboard is working in general I had no issue with Cap lock and numbers etc...

As for the other issue I was not able to reproduce them, If I use Embedded UltraVNC, It does work and also does not have keyboard issue after focus lost.

I have TightVNC running on the remote machine to connect Embedded UVNC. Maybe this is why it works for me.

If you get UVNC embedded to work, I would use this method as a work around for the time being to avoid the keyboard focus being lost.

I will report the Default VNC embedded focus issue to the engineering team.

Don't hesitate to reply if you have any questions or heads up to give us about this issue :).

Best regards,

Hello,

Concerning Internal VNC, I was able to reproduce and fix the keyboard and Caps/Num lock issues.
These fixes will be included in the next release available soon.

Regards

Hello Jonathan
Glad to hear this. Thank you