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.
THanks, Tony, I now updated my etc\hosts files on all systems and this improved response time dramatically (now 1 second). I'm not using a local DNS, only the ISP's DNS when my dial-up router is open. I'll try later if it makes sense to bring up a local DNS on the NT Server. Joost "Tony Hoyle" <tmh at nodomain.org> wrote in message news:6290nvcts3o3vj1ishcd6jdjn7vo503r4n at 4ax.com... > On Tue, 23 Sep 2003 11:37:22 +0200, "Joost van der Plas" > <joost.cvsnt at musigma.nl> wrote: > > >A fresh install of CVSNT 2.0.9 on a 800MHz Win2000 notebook. The repository > >root and temp are on a local NTFS partition. Only a small TEST repository > >(20 files) > >Trying to access this from remote Win NT4 machines on the LAN (400MHz, > >256MB), using :sspi: protocol. > >Response is extremely slow! 20 seconds for a simple "cvs ls" command. While > >waiting I monitor the task manager on the server and the client and keep an > >eye on the LAN switch (100Mb ethernet): no CPU load, no harddisk thrashing, > >not out of memory, no LAN traffic. If I keep repeating the ls command > >SOMEtimes the response comes within 4 seconds, but most of the time 16-20 > >seconds. > >On the local machine, using sspi protocol the response is almost > >instantaneous. > > > Your Reverse DNS is probably broken. Try checking 'Don't resolve > client names' on the control panel and see if that fixes it > temporarily, then have a word with your admin about getting the > Reverse DNS fixed properly. > > Tony >