Hi Philip, Sorry to hear that. The difference you've highlighted is that the "target" machine is on Wi-Fi, not cable, which can cause issues. You might also check, for instance, what the target computer thinks the MTU of the Wi-Fi network is, and compare that to what it really is - if it's smaller than the server thinks it is then the connection is likely to stall as soon as a significant amount of data gets transferred.
Regards, -- Wez @ RealVNC Ltd > -----Original Message----- > From: vnc-list-boun...@realvnc.com [mailto:vnc-list- > boun...@realvnc.com] On Behalf Of Philip Herlihy > Sent: 14 May 2009 17:09 > To: vnc-list@realvnc.com > Subject: RE: Indirect connection works better > > Thanks, Wez - however, in response to guidance you gave me once before > I > already have that setting enabled. > > What puzzles me is that either route is using the same links, so it's > hard > to understand what the difference might be. > > > Philip Herlihy > > > > -----Original Message----- > From: vnc-list-boun...@realvnc.com [mailto:vnc-list- > boun...@realvnc.com] On > Behalf Of James Weatherall > Sent: 14 May 2009 16:21 > To: 'Philip Herlihy'; vnc-list@realvnc.com > Subject: RE: Indirect connection works better > > Hi Philip, > > Some Wi-Fi routers have trouble handling large numbers of small network > packets, such as are produced when moving the mouse around in the VNC > session, and that in turn can upset the Windows TCP stack and lead to > the > sort of behaviour you're seeing. > > You can enable the "Pointer event rate-limiting" feature in the VNC > Viewer > to work around this problem. > > Cheers, > > -- > Wez @ RealVNC Ltd > > > > -----Original Message----- > > From: vnc-list-boun...@realvnc.com [mailto:vnc-list- > > boun...@realvnc.com] On Behalf Of Philip Herlihy > > Sent: 14 May 2009 15:34 > > To: vnc-list@realvnc.com > > Subject: Indirect connection works better > > > > Recent came across a situation again which has puzzled me in the > past. > > I'm > > trying to connect to a machine running VNC Free edition in an office. > > I can > > make the connection (having set up port forwarding on the router) but > > it > > hangs, with only the top third of the screen visible after several > > minutes. > > Further attempts produced the same result. > > > > That office has a workstation used as a simple workstation. Unlike > the > > "target" machine, which is wirelessly connected, this one is > connected > > to > > the router by cable. I can connect reliably to the fileserver PC. I > > found > > that within my remote session I could start a new session from the > > fileserver PC to the target PC, and this worked well. > > > > Now that's using the same links, but in two jumps instead of one. > > What's > > going on? > > > > Phil, London > > _______________________________________________ > > VNC-List mailing list > > VNC-List@realvnc.com > > To remove yourself from the list visit: > > http://www.realvnc.com/mailman/listinfo/vnc-list > > > _______________________________________________ > VNC-List mailing list > VNC-List@realvnc.com > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list > > > _______________________________________________ > VNC-List mailing list > VNC-List@realvnc.com > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list