Bug/Feature Request: Upgrade RFB Protocol from 3.16 to 3.6

[dburanen]

I think the RFB version is preventing my viewer from working correctly.

The latest stable, UltraVNC 1.02, supports RFB protocol 3.6. I can see this by clicking 'add new client' from the ultravnc server and connecting to my listening vncviewer. When I use SC, I see that it uses 3.16.

The whole prompt behind this is that right-clicking on UltraVNC server and adding a client works. SC tries to connect, but I never actually get a screen.

It used to work wonderfully for me, and I'm also writing a bug to the xvnc4viewer software folks to support old RFB versions, but I figured it would be real easy to use the new UltraVNC server engine to support the newer RFB version.

SC version: both RC23 and REL1.00 behave the same
xvnc4viewer version: VNC Viewer Free Edition 4.1.1 for X - built Jan 7 2007 17:30:38

[redge]

windows OS
UltraVNC server 1.0.3 RC6 protocol RFB 3.4
UltraVNCviewer 1.0.3 RC6 protocol RFB 3.4 unofficial connecting to real vnc server 4.1.2
real vncviewer 4.1.2 connect to UltraVNC server 1.0.3 RC6 = protocol RFB 3.3

[dburanen]

I posted this bug report on the viewer to see if they can support older RFB versions, but a new version of SC based on 1.02 or 1.03 would be real nice.

https://bugs.launchpad.net/ubuntu/+sour ... bug/123631

[dazwin]

I think this should be regarded as a bug in UltraVNC SC, rather than in the viewer.

The problem is that SC v20.3 (based on RC23) reports a version string of "RFB 003.016". Versions of vncviewer in Ubuntu 7.04 (feisty) and earlier support v3.3 of the RFB protocol. However, 7.10 (gutsy) changed implementations for a version that supports v3.8 (according to wikipedia, this is the latest version released). SC appears to be fine with v3.3 but not with v3.8. As the protocol version is negotiated to the lowest common denominator, this causes problems with gutsy (and probably any other VNC viewer that supports RFB v3.8 ).

[dburanen]

Is there anyway we can create a new SC that uses 3.3 or 3.8 version of vnc as the backend instead of the old version that SC uses?

Are we at the mercy of uvnc devs? I haven't heard any word and it looks like they're pushing pchelpware. Are we screwed? Is it time to look to another VNC app to provide this functionality?

[ro1234]

I'd be very interested in getting a newer RFB protocol for SC. tightvnc and realvnc viewers either don't work with SC or work very poorly with it. Any news on this front? It is a tremendous feature to decouple the viewer from the server.

[Rudi De Vos]

UPgrading the protocol require to implement all new features added in rfb 3.6 else the connection will not work.

This is a lot of work..

[dazwin]

Rudi - would it be possible to fix the SC generator so that it provides the correct protocol number?

I've just run into this problem again since upgrading to Ubunto 8.04. This time though, my workaround posted in an Ubuntu thread (http://ubuntuforums.org/showthread.php? ... ost3858988) requires an extra step, as the xvncviewer package has now been removed. You can still install the older v3.3.7 xvncviewer from Gutsy, but the workaround is becoming more difficult.

[dazwin]

Just for reference - there is still an active thread about this on the Ubuntu forums (http://ubuntuforums.org/showthread.php?t=299489&page=11)