[cvsnt] speed issues and timeouts with a bad latency connection

[Bo Berglund]

Why not try the sspi protocol instead?
Since it does not use named pipes it might help in your case. SSPI
runs exclusively over port 2401 using TCP/IP, so there is no longer a
need for a WINS server resolution or NetBios or all that other crap
that can't even be routed.

And SSPI can use the current workstation login or alternatively use
the :sspi:user at server: setting that allows you to use cvs login to
establish the connection.

/Bo

On Sun, 16 Mar 2003 09:31:28 -0800, Anand Arvind
<anand.arvind at click2learn.com> wrote:

>We have been on CVSNT for more than 3 years now for our engineering group
>and if we work from our US offices things work well. We have this setup with
>NT auth (a recent build, will find exact number if required) using named
>pipes, the same as it is in the US. Now from our India offices, when using
>cvs we find it is very slow in syncing up, doing diff's and other operations
>in general and even though there is enough network bandwidth, we find that
>the latency is sometimes close to 500 to 1000 ms unlike here where it is
>around 10 ms. Most common errors we get are named pipe errors and I can send
>exact details if needed.
> 
>I need some advice on how to figure out what can be done to make the
>experience better as this and how to go about figuring this out.
> 
>Thanks
>Anand


/Bo
(Bo Berglund, developer in Sweden)