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 email@example.com.
For the sspi format you have used you can do the following on a command prompt on the client: set CVSROOT=:sspi:garyl at cvs-server:/CVS-Repository cva logout cvs login (Now enter the password) This will update the cached password if successful and sspi will work afterwards. The only reasons to use your version of the connect string (with the user explicitly entered) are: 1) If you are logged on to the client computer as another user than the one you want to use for communicating with the CVS server 2) If the client PC is not part of the domain the cvs server is connected to 3) If the cvs server is not part of the domain the client PC is connected to 4) If you are connected via VPN or similar with difficulty getting AD authentication running Concerning the -d option to CVS This is not something you should ever do inside an existing sandbox! I am surprised that it even overrides the CVS/Root files that exist in the sandbox, it shouldn't! You use this typically on the command line if you are executing CVS commands in a folder that is not a sandbox, for example in order to create a sandbox by checking out a module from the server. Apart from that I see no valid use of that syntax. Either you are working inside the sandbox and then the Root files show where the files came from and where any operation should be directed, or you are outside a sandbox, when the -d option or CVSROOt env variable can be used. If the server has changed name then you need to modify all Root files accordingly, in WinCvs there is a macro to handle this for you. Best regards, Bo Berglund -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Garyl Erickson Sent: den 21 november 2007 04:29 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] SSPI stopped working -- how to troubleshoot I'm using CVSNT 2.5.03 (Scorpio) Build 2151 on a Window 2000 server, accessing it from a Windows XP client running 2.5.03 (Scorpio) Build 2382. I was using :sspi:garyl at cvs-server:/CVS-Repository. It just stopped working and I now get authorization failed messages for any and all commands. For example: > cvs stat cvs [status aborted]: authorization failed: server cvs-server rejected access to /CVS-Repository for user garyl I do not know of anything that changed on the client or cvs-server and I've rebooted both. I found I can use pserver ok. My account on the domain, local to the XP client and local to the cvs-server all have the same password. What else should I look for to troubleshoot this? I also find my garyl account is getting locked out of the domain and/or the cvs-server (which isn't in the domain, but in a workgroup) after a few tries at executing CVS commands. By the way, I can only use pserver if I use the -d :pserver:cvs-server:/CVS-Repository switch. Changing the env var CVSROOT to the :pserver: location doesn't override the :sspi: location in the CVS\Root file. Is this normal? Do I have to change all the Root files in my working copy if I change protocols? I was hoping a checkout or update with the -d would update the Root files in my working copy, but no such luck. Thanks for any help you can offer, Garyl _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs