[cvsnt] CVSNT+WINCVS

Peter Crowther Peter.Crowther at melandra.com
Fri Sep 9 11:19:42 BST 2005


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
> I am using all machines with Windows XP

- Home or Professional?

- Domain or workgroup environemnt (I assume workgroup)?

- Which service pack?

- Is any anti-virus software installed?  If so, is real-time scanning of
the CVS repository and temp space turned off?

- Is any firewall software installed (including XP SP2)?  If so, is port
2401 open?

> server is configured say on Machnie1.
> I install a combination of WinCVs and CVSNT in Machine2 which 
> is a client.

If you use WinCVS 2 as the client (I'd suggest it rather than 1.2), you
do not need to install any part of CVSNT on Machine2 other than what
WinCVS comes with.

> I do not have to set anything in CVSNT Control Panel in the 
> client, I guess; do I ?

No.  You should not even have the CVSNT server installed on Machine2.

> I see both services CVS.exe and CVSlock.exe are running on 
> the client. There is no repository created on the client 
> through CVSNT Control Panel (as I did for the server successfully)

Irrelevant - I'd actually uninstall CVSNT server from Machine2.

> Now I use any CVS command on Machine2 (client) with CVSROOT 
> as server as host and user name (say john) as a system user 
> in Machine1(server), say login (cvs login). If I enter 
> password it is displaying that the party connected did not 
> respond for some amount of time  (error- connection timed 
> out).

Ah!  Right, you didn't say that in the original posting.

If you run 'telnet localhost 2401' on Machine*1*, do you connect or do
you time out?

If you run 'telnet Machine1 2401' on Machine*2*, do you connect or do
you time out?

If the first one works and the second one fails, I think you have a
firewallthat is blocking CVS.  Open port 2401 on Machine1, and keep
testing until the telnet tests work.  Then try a CVS login again.

> (I login (system login) in Machine2 with diiferent 
> login name other than "john")
> I think now the problem is well understood.

Better, certainly.

		- Peter



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook