[cvsnt] Stupid error message from CVSNT...
bo.berglund at telia.com
Sun Nov 7 19:47:27 GMT 2004
The error message "No connection could be made because the target
machine actively refused it." is really both misleading and stupid.
Could it not be changed to something more descriptive?
I did the following test today:
1) I did not open the VPN tunnel to the network where the CVSNT server
is located before ding an update. Thus the machine is not even
Result: Error with the message above.
Should have been: "CVS server not accessible, check network
2) I shut down the CVSNT service on a local CVSNT server and then
tried updating a sandbox from that server. In this case noone is
listening to port 2401 but the server is accessible.
Result: Error with the same message.
Should have been: "CVS service on <servername> at port 2401 not
accessible, check server state."
The message as sent by CVSNT causes unneeded confusion because users
tend to think that the server is running all right but for some reason
their access is rejected (actively), when in fact the client cannot
reach the server at all.
So they are looking in the wrong direction for a solution to their
I really take exception to the wording "actively refused" because
there isn NO activity at all from the server in this case! Why was
this wording chosen?
Please consider changing the message to something that makes sense to
(Bo Berglund, developer in Sweden)
More information about the cvsnt