On Tue, 09 Aug 2005 07:34:22 +0100, Johannes Kilian <jok at vitronic.com>
wrote:
>Hi,
>>running CVSNT 2.5.02 (Servalan) Build 2048 on client side and CVSNT
>2.0.41 on server side (yea I know, quite old but I do not have to much
>influence on that ... :-() the following error occurs when talking to
>the the server:
>[80090303] Das angegebene Ziel ist unbekannt oder nicht erreichbar.
>("The denoted destination is unknown or not accessible")
>>This error occurs when trying to do any operation in my checkout module
>(diff, add, commit ....)
Adding to this I can report the following difference in the client
behaviour:
The versions are as follows:
cvs ver
Client: Concurrent Versions System (CVSNT) 2.0.51d (client/server)
Server: Concurrent Versions System (CVSNT) 2.0.38 (client/server)
In this case I can run 'everything' I need.
But using 2.5.02 build 2048 on the client side towards the exact same
server:
cvs status -q -- AGIAdmin.cfg (in directory
C:\Engineering\Projects\PC\AGIAdmin\)
[80090311] No authority could be contacted for authentication.
Finally if I switch to a server that is the 'newest' available (cvsnt
using pserver):
cvs ver
Client: Concurrent Versions System (CVSNT) 2.0.51d (client/server)
Server: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build
2054 (Release Candidate 2) (client/server)
and with the 2048 client:
cvs ver
Client: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build
2048 (Release Candidate 2) (client/server)
Server: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build
2054 (Release Candidate 2) (client/server)
Finally 2048 on both server and client and using :sspi: as in the
2.0.38 server case:
Server: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build
2048 (Release Candidate 2) (client/server)
Client: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build
2048 (Release Candidate 2) (client/server)
So there is definitely a problem with the 2048 towards older servers
using :sspi:.
What gives?
/Bo
(Bo Berglund, developer in Sweden)