After more 2 000 000 (two million) views on forum for 1.5.0.x development versions... and 1.6.1.0, 1.6.3.0-dev versions A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095 Feedback is always welcome
2025-12-03: Could you please complete our poll/survey? Renaming UltraVNC files and service to be more clear: https://forum.uvnc.com/viewtopic.php?t=38128 There was a problem to vote, it is solved now! Thanks in advance!
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127 Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
Tue Apr 11 11:53:17 2006
CConn: Accepted connection from 192.168.10.4::2420
CConnection: Server supports RFB protocol version 3.16
CConnection: Using RFB protocol version 3.8
Nothing pops up on my screen however.
Is this a protocol mis-match problem? Is there any way to make RealVNC work as a listener with UVNC SC?
[mod=494,1149124808]moved from VNC related product to SC[/mod]
Last edited by rayvd on 2006-06-01 01:20, edited 1 time in total.
I'm not sure that is actually the reason. I have the same problem, but I have a working Linux realvnc listener too.
Old system: Gentoo Linux with RealVNC 3.3.7 - been working with VNC SC since June 2005 - still works with latest releases of SC (RC23 and REL1.00)
New system: Gentoo Linux with RealVNC 4.0.0 - same symptoms as described above - connection comes in but nothing displayed
For the record, on the working old system (RealVNC 3.3.7) I get this amongst the connection text:
--------------
VNC server supports protocol version 3.16 (viewer 3.3)
No authentication needed
Desktop name "WinVNC"
Connected to VNC server, using protocol version 3.3
Well I got VNC SC connecting to a Linux listening viewer, but I had to give up on RealVNC 4.0.0. Instead I used TightVNC 1.2.9.
I hadn't tried that till now because on my original system I had first tried to build it with TightVNC, which wouldn't work with VNC SC and I had to use RealVNC - go figure!
right click over systray realvnc free edition 4.1.2
Default Options...
[v] Only use protocol 3.3
Now it's work ! should be a little bug, normally don't need to force this option for work with older software.
I don't know who is responsible of this code source error
UltraVNC 1.0.9.6.1 (built 20110518)
Windows OS: XP Home + Vista Business + 7 Home
Only experienced user, [u]not[/u] developer