A couple people have emailed me privately wondering if I ever solved the following problem, so I thought I'd send a follow-up for posterity.
> I'm having a problem where everything works fine for about 20 seconds, > then the viewer closes with the message: "Error while waiting for server > message". I've tried using different compression protocols, and numeric > IP instead of domain name, but neither helped. > > Setup: > - Client: TightVNC 1.2.4 on Windows XP Pro > - Server: TightVNC 1.2.4-1 (3.3.3r2) on Redhat Linux 7.2 > > The strange thing is that it was working before, and I don't think I've > changed anything. (Well, I upgraded from 1.2.3 to 1.2.4 when I first > noticed it.) > > The server is running in a VMWare host, with direct networking between > the XP host and Linux guest. I think it may be a problem with the network sporadically going out, or maybe with clocks being out of sync. I recently upgraded to VMWare 4.0 beta and Redhat 8.0, and have not had problems yet. Basically, I run the server on the virtual linux machine, and connect from Windows. One problem I had was that VMWare's network was dying from time to time--I think because the virtual machine's clock runs slower than the host's. The new version of VMWare includes a Linux daemon to keep the clock in sync with the host. Since the upgrade, I have noticed a more stable network, and the error described above hasn't occurred since then. In fact, I leave a VNC running full screen on another virtual desktop, and the connection survives even a suspend or hibernation of the laptop. Plus, if I do lose the connection, my X session does not close. Nirvana! David _____________________________________________________________________ David Coppit [EMAIL PROTECTED] The College of William and Mary http://coppit.org/ One thing the blues ain't... is funny. Stephen Stills, "Black Queen" _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
