Hi David, It appears to be a problem with single-threaded network I/O on Windows systems. VNC 3.3 series servers (on which TightVNC is based) have separate send & receive threads, which appears not to trigger the problem. There appears to be a bug in Windows' TCP stack which causes it to stop responding to incoming data if a TCP connection has a full outgoing data buffer and is continuing to receive data.
Current VNC Enterprise & Personal Edition servers include a MaxOutBufferSize parameter, which can be used to increase in-server per-connection buffering of outgoing data, which should fix the problem for you. Finally, you should find that things are improved if you switch VNC Viewer to "Rate-limit pointer events". Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: David Cook [mailto:[EMAIL PROTECTED] > Sent: 20 April 2006 02:06 > To: 'James Weatherall'; [email protected] > Subject: RE: RealVNC doesn't work between two Win-XP systems... > > Wez - > > Hey, very good guess...exactly right! > > So, why is it that RealVNC can't handled that, since > TightVNC clearly does? Is there a workaround for > RealVNC? > > Cheers... > > Dave > > > -----Original Message----- > From: James Weatherall [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 19, 2006 6:42 PM > To: 'David Cook'; [email protected] > Subject: RE: RealVNC doesn't work between two Win-XP systems... > > > Hi David, > > Are you running connections over a wireless link, by any chance? > > Cheers, > > Wez @ RealVNC Ltd. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of David Cook > > Sent: 19 April 2006 22:54 > > To: [email protected] > > Subject: RealVNC doesn't work between two Win-XP systems... > > > > Hi - > > > > This week, I downloaded the free-edition, V4.1, of > > Real-VNC. (I used both VNC and Tight-VNC in the past.) > > > > I hate to say it, folks, but I can't make a connection > > last for longer than about 30 secs and two or three mouse-clicks, > > before the 'viewer' window on the client just disappears. I > > tried one Win-XP machine as 'server' and two other Win-XP > > machines as clients, all with the same result. > > > > [I'd have THOUGHT a v4.1 would be pretty solid. > > But, rather than fret, or debug, or whatever, I instead loaded > > the latest 'TightVNC' kit, and that works just fine.] > > > > Just thought I'd let you know. So, can anyone give me > > a reason why RealVNC might be superior to TightVNC, if I were > > to invest some cycles in troubleshooting the problem? > > > > Anyone have any strong guesses as to what is probably > > the problem? (All 3 of the Win-XPs have SP2 with all the patches.) > > > > > > Cheers... > > > > Dave > > web-kayak-project: > > http://mysite.verizon.net/david.hubert.cook/homebuilt-kayak/ > > web-GoogleMaps-project: > > http://mysite.verizon.net/david.hubert.cook/google-maps/ > > _______________________________________________ > > VNC-List mailing list > > [email protected] > > To remove yourself from the list visit: > > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
