[quote=“JonathanOSX”]Vine Server is definitely set to support multiple simultaneous connections to the same desktop. I just ran a test where 4 machines were connected and watching at once.
[list]Two Mac OS 10.4 machines running Vine Viewer
One WindowsXP machine running TightVNC 1.2.9 (native, not java)
One WindowsXP machine running RealVNC 4.1.2[/list:u]
I would like to track down whatever incompatibility we are looking at so let me ask some questions to the people experiencing this problem.
What Hardware(PPC/Intel?) and Vine Server Version is the server running?
Under Vine Server->Sharing how is Server Sharing set?
Have you checked that the VNC clients are “allowing a shared connection” as opposed to exclusive access. This is usually a connection option within the client?
For the VNC Client(s) what OS, client, and client version you are running?
I heard some discussion of running the TightVNC JAVA client. Since most people only run the JAVA client when connecting on port 5800 (which Vine Server doesn’t internally support) can you describe that configuration in greater detail?[/quote]
Here is the hardware/software config that I use to reproduce the problem. . .
One Vine Server (latest version) running on a Mac OS X 10.4.7 (Tiger) box.
Two Tight VNC Java clients (v 1.2.9, binary class file distribution, downloaded from http://www.tightvnc.com), each running on a Windows 2000 SP4 box connecting to the Mac OS X box.
When the first viewer connects, the images are fine. When the SECOND viewer connects, the images on one or both are garbled and/or one of the viewers crashes with a “Corrupt JPEG data” or “End of SOF” error message. Same results with more than 2 TightVNC Java viewers and/or Java viewers running on XP or Mac OS X.
This same behavior is NOT noticed when the Java viewers connect to a TightVNC server running on Windows 2000 or XP, i. e. with this server, mutiple TightVNC Java clients connect and display images with no problem, regardless of what platform the Java clients run on.
ALSO, I noticed this problem GOES AWAY when the Java viewers are re-compiled with the “Hextile” encoding (as opposed to the “Tight” encoding which comes with the distribution). With the Hextile encoding mechanism, multiple Java viewers can connect to the Vine Server and view the OS X desktop with no problem.
You can try this yourself as follows. . .download the Java TightVNC viewer source (tightvnc-1.2.9_javasrc.zip from http://www.tightvnc.com/) and in the file OptionsFrame.java, change the line of code
Recompile the Java code and within the vnc_javasrc directory, run as
java VncViewer HOST (IP addr. of PC running Vine Server) PORT 5900
on two or more PCs (Mac or Win), and everything works fine. The pre-compiled version of the code (tightvnc-1.2.9_javabin.zip) however, has this option set to “Tight”.
Similar behavior occurs with the executable distribution of TightVNC (vncviewer.exe). On Windows, once this is installed, if you go to Start->Programs->TightVNC->Fast Comression on two or more Windows 2000/XP machines connecting to the Vine Server, the rendering/images are OK.
However, if you go to Start->Programs->TightVNC->Best Compression on two or more Windows 2000/XP machines connecting to the Vine Server, the images on one or more are garbled and/or one or more of the viewers crashes with some imaging error.
It appears, based on this experiment, that OSXvnc has a problem with two or more simultaneous connections when the viewers are using “Tight encoding”.