Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Fri, 27 Oct 2006 12:37:13 +0100, Tony Hoyle <tony.hoyle at march-hare.com> wrote: >Bo Berglund wrote: >> Why this happens is beyond me and it sure looks like a networking >> problem. The status commands produce the start of a display, sometimes >> only the leading ==================== line and sometimes a few lines >> more, but then it invariably stops. >> This always happens with cvs status -v file1 file2, and sometimes also >> with only one file mentioned. >> But never with cvs status -q .... >> >> Why is there a difference? >> >Those symptoms look like packet loss of large packets - normally caused >by misconfigured MTU across tunnels and/or broken PMTU discovery. Other >possibilities are a broken network card or switch. > >Compression would make this worse since it builds up a chunk of data >before sending it, rather than sending line by line. > >Tony Interesting, I had a possibly related problem a year or so back when I failed to connect to the remote desktop of a PC on a remote network accessed via Microsoft PPTP VPN tunnel. The remote desktop was drawn up on my PC as a frame and then everything stopped. After googling and asking on a microsoft NG I got the advice to change the networking parameter: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NdisWan\Parameters\Protocols\0 value ProtocolMTU Advice was that the value should be lowered until working. I now have it set to 1300 (don't remember what it was before) and then the remote desktop started to work properly again. Is this the same thing, then I would like to know where to change it. The above fix was connected to the VPN tunnel traffic. Any hints? HTH /Bo (Bo Berglund, developer in Sweden)