Just to make sure that the Stunnel binary and WinVNC server were not acting weird together, I established the tunnel on another workstation in my house and had the WinVNC server connect through that. Same result. > I verified this exact behavior on a completely deferent Windows > 98 machine. I also tried this on a Windows 2000 machine and in > that case the WinVNC server process locked up but the rest of > the machine seemed to be fine. > > ----- Original Message ----- > From: "Michael F. March" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, May 30, 2001 1:45 PM > Subject: VNCserver locks up when going over a uncompressed tunnel on Windows98se.. > > > > When using SSH or Stunnel to forward a outgoing server connection, the > > WinVNC server on my Windows box becomes unresponsive. This is using > > both stock VNC with Hextile and TridiaVNC with Tight encoding. If I > > happen to turn on compression for SSH however, things work smashingly > > well. Without compression on SSH (or stock Stunnel) only 1/4 of the > > screen gets sent before the server becomes unusable. > > > > > > > > Anyone have any ideas? > > > > Tight encoding doesn't require SSH zlib compression, right? > > > > <march> > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to [EMAIL PROTECTED] > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to [EMAIL PROTECTED] See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
