[cvsnt] SSPI Problems
bob at aesirsoft.com
Fri Dec 30 01:42:54 GMT 2005
We upgraded from 2.0.58d to 2.5.01 with no problem. Now we just upgraded to
2.5.03 (Scorpio) and the problem started.
From: Arthur Barrett [mailto:arthur.barrett at march-hare.com]
Sent: Thursday, December 29, 2005 9:08 PM
To: Bob Provencher; cvsnt at cvsnt.org
Subject: RE: [cvsnt] SSPI Problems
If the server is not a part of a domain then how can it authenticate the
user? I don't think a server not in a domain can have a trust
relationship with the an authenticating domain?
Please see this FAQ about questions (and the information to supply):
Without the old and new version numbers including build numbers there is
very little we can understand of your problem, traces of the old and new
versions may also help, as would the cvsdiag dump of the server.
The correct syntax for sspi CVSROOT is:
Note: no password.
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Bob Provencher
Sent: 30 December 2005 00:45
To: cvsnt at cvsnt.org
Subject: [cvsnt] SSPI Problems
Is anyone else having problems with SSPI?
We recently upgraded and now can not login to the server.
We use the :sspi:username:password at host form of the cvsroot, using a
username and password on the server. When we do this the user is locked
out after three tries (so we know we are getting to the correct
We're logging onto a server that is not part of a domain, from a client
that is. The username and password on the client are the same as that
on the domain.
We've also tried :sspi:servermachinename\username:password at host with no
cvsnt mailing list
cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
More information about the cvsnt