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.
Tomas Vala wrote: > this makes no difference, since 'sspi' and 'ntserver' does not require > explicit specification of login name. It operates with login of current > Windows user, in contrast to for example 'pserver' (as i understand). No, you are close but not completely there. sspi and ntserver use the underlying NTLM authentication, which means the client and server machine must have a trust relationship of some sort (same domain) before the authentication will work. Additionally, the client and server must be talking the same auth methods (see below). > unsuccessful attemp via sspi > ------------------------------------------ > set cvsroot=:sspi:myserver:/TEST > cvs login > ... > cvs [login aborted]: Can't authenticate - server and client cannot agree on > an authentication scheme > That error message seems pretty clear to me. I think your problem is here: > environment > ----------------- > Server: cvsnt 2.0.1.1 / 2.1.1 @ Windows2000 Server / Windows XP SP1 > Client : cvs 1.11.1.3 console / WinCVS 1.3 @ Windows XP SP1 > Situation: 1) both server and client on the same machine (Windows XP SP1), > 2) server on Windows 2000, client on Windows XP XP has the annoying default behavior of always encrypting authentication packets regardless of whether the server will understand them. Try following the instructions found here: http://forums.devshed.com/t75558/sda531038daac1180768aa1b20e1e0c21.html to make XP behave. In the case of Samba, only the first of the two changes is mandatory I've found. HTH John