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 firstname.lastname@example.org.
Andy, > Thanks for your help I finally narrowed it down to DNS (As you > mentioned). > > Using DHCP for the systems network configuration but exclude the DNS > settings it works. OK - getting closer then. From the traces it appears as though it is specifically the interaction with the lock server. Have you ensured that in the control panel autoconf publishing is off and the 'lock server listens locally' is set on? I suspect it means that localhost is not resolving but I've not come across it on windows before. > > This obviously does not solve my problem but at least I know where it > is. > > I can use nslookup to perform forward and reverse lookups successfully > but that is where my DNS skills end. What else does CVSNT do with DNS > that I should be looking at? I can't think of anything at all. What happens if you start 'cvslock.exe -test' and then in another window 'telnet localhost 2402' ? You should instantly connect to it and get 'Starting thread' followed by 'Lock Client #1(domain.name.local) opened' on the 'server' and 'CVSLock 2.2 Ready' in the telnet session. Regards, Arthur