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.
> From: [...] Ananda Rabi Dhar > Please help me in the following settings: > > In client machine I need both CVSNT and WinCVS (assumed that > I need the graphical front end). The CVSNT in client machine > is running both CVS Server and LockServer. I'm confused. Do you have one machine involved in CVS, or two? Here you mention a client running the CVSNT Server (and lock server)... > I have configured > rightly for the server machine and tested pserver protocol > for check-out and other cvs operations. I do have a feeling > that the port 2401 where pserver is trying to connect is > locked and the server is not responding for basic commands > like login. I have logged out from server machine and trying > for another user to login. I am getting error like server > timed out...login aborted... ... Whereas here you mention a separate CVSNT Server machine. > Please tell me specifically whether I need to install and > start the CVSNT services on the client, or I just need to use > WinCVS there. You only need to install and start the CVSNT services on the CVSNT server. At least the most recent version of WinCVS is available with a CVSNT client. On the client machine, you only need to install that combination of WinCVS and CVSNT client. > I gain mention that I have successfully used pserver protocol > for a virtual client on the server machine and been able to > use CVS commands. Is there any particular setting change > required for that in either server side or client side or > both. Not that I'm aware of, as long as you use your server's hostname in your CVSROOT. > I have gone through the tutorials and it has shown > example of using client and server on a same machine. Yes. You can do that, but you don't have to do that. Incidentally, are all the machines running Windows 2000 or higher (but not XP Home), and are they all in a Windows domain? If so, you may wish to use the SSPI protocol rather than pserver - it's much simpler to configure and manage. - Peter