Tight Vnc 2.8.59 issue

[jasminmizic@gmail.com]

Hi,

I am using ASG tool for quite a while now.


On most of my pcs I have version Tight VNC 2.8.27
And this version works fine, I use option, right click and connect with protocol - VNC
and then get request for password

but now I want to update VNC and with new TightVNC I get this error: Your Connection has been rejected

If I set up to use VNC protocol and define VNC password everything is fine but , most of my connection is RDP and then I got right click use protocol VNC and enter password manually. On older version of VNC this is ok but on new one I get this reject.

File with screenshot is attached

[Michael Scholz]

Hi,

I just rechecked that by installing TightVNC server 2.8.59 for a test. Added a new connection in ASG-RD with role "VNC" enabled and verified usage of the same port on server and in Connection properties. Connection works well.  

Am I correct that you mostly use RDP connections but occasionally you use them to connect via VNC also by using the context menu and that worked with an older version ?  I could verify the effect with the latest version... but seems an older version is not available any more to verify; We check internally if we can find something that might go wrong here. 
best regards,
Michael

[jasminmizic@gmail.com]

Hi,

I just rechecked that by installing TightVNC server 2.8.59 for a test. Added a new connection in ASG-RD with role "VNC" enabled and verified usage of the same port on server and in Connection properties. Connection works well.  

Am I correct that you mostly use RDP connections but occasionally you use them to connect via VNC also by using the context menu and that worked with an older version ?  I could verify the effect with the latest version... but seems an older version is not available any more to verify; We check internally if we can find something that might go wrong here. 
best regards,
Michael

Hi Mike,

In my connection property I have defined role RDP and VNC and Credentials. RDP is primary and credentials are for RDP and most of connection are set that use RDP protocol. When I want to use VNC I go right click and use VNC and then I get pop up to enter VNC password since in connection is defined RDP credentials.

Problem is with new version that somehow ASG doesn't forward question for VNC password.

When I change primary role to VNC and set credentials to VNC Credentials, all is ok, but this is not option for me since I use mostly RDP but also I need to use VNC.

Version of TightVNC that works is attached in first post.

[Michael Scholz]

Hi Jasmin,
After rechecking I also found that the effect is given through the credential settings: if those differ between RDP and VNC then - if passwords are needed for VNC - you will be rejected because of using the RDP credentials. Because we only exchange the used protocol - credentials stay the same. Technically it's correct behavior. If you want to use both options you can use "connect with multiple options" There you also have the option to define multiple "one-click" profiles with different passwords already set by storing them in profiles. I also rechecked my "main" VNC server on linux "X11 VNC" and that works excatly like you want: if using a wrong password it will prompt you and don't reject the session. So I assume thats what changed in the latest Tight VNC versions: there is no prompt after using a wrong password. So Tight VNC changed it's behaviour - that's why it worked before.
Probably there is a configuration setting allowing TightVNC old behaviour - but that's not in our hands. Hope that helps ;-)
Best regards,
Michael

[jasminmizic@gmail.com]

Hi Jasmin,
After rechecking I also found that the effect is given through the credential settings:  if those differ between RDP and VNC then - if passwords are needed for VNC - you will be rejected because of using the RDP credentials. Because we only exchange the used protocol - credentials stay the same. Technically it's correct behavior. If you want to use both options you can use "connect with multiple options" There you also have the option to define multiple "one-click" profiles with different passwords already set by storing them in profiles. I also rechecked my "main" VNC server on linux "X11 VNC" and that works excatly like you want: if using a wrong password it will prompt you and don't reject the session. So I assume thats what changed in the latest Tight VNC versions:  there is no prompt after using a wrong password. So Tight VNC changed it's behaviour - that's why it worked before.
Probably there is a configuration setting allowing TightVNC old behaviour - but that's not in our hands. Hope that helps ;-)
Best regards,
Michael

Hi Michael, 
I checked VNC Server for options, all options are same like in previous version. Would this be possible to fix from your side. I know for option "connect with multiple options" but it is much easier to enter password then to click multiple times.

[lemmy1]

Hi Jasmin,

I don't think that a "fix" from our side makes sense since we don't know when features or behaviour from the 3party product will change again. Then we would have to change again and this possibly would effect people using older versions. Also it would possibly affect other versions of VNC negatively - for example X11 VNC. The problem is there are different versions that behave different. So we should not trick the behaviour of one special version.
If you think its a important feature to add possibility to dont send a passwort if using "connect using protocol" then please add it as a feature request - thats the only option we can think about.
Regarding "connect with multiple options": It's only 2 clicks if the VNC password "profile" has been stored. Thats the same as "click with protocol" but withoud the need to type in the password. Only one time to save the profile. Thats not a bad deal I think ;-)

[jasminmizic@gmail.com]

Hi Jasmin,

I don't think that a "fix" from our side makes sense since we don't know when features or behaviour from the 3party product will change again. Then we would have to change again and this possibly would effect people using older versions. Also it would possibly affect other versions of VNC negatively - for example X11 VNC. The problem is there are different versions that behave different. So we should not trick the behaviour of one special version.
If you think its a important feature to add possibility to dont send a passwort if using "connect using protocol" then please add it as a feature request - thats the only option we can think about.
Regarding "connect with multiple options":  It's only 2 clicks if the VNC password "profile" has been stored. Thats the same as "click with protocol" but withoud the need to type in the password. Only one time to save the profile. Thats not a bad deal I think ;-)

Hi,

ok, I will go back for older version now let see how next new version will behave.