>> If I enable the ‘SSPIPackage Negotiate’ line (which I just added) then my >> Subversion 1.8 clients appear to authenticate correctly, but my neon based >> 1.7 clients fail with an even worse error that can’t be resolved by just >> typing the password. >> > > Seems like for me the SSPIPackage Negotiate is not working for 1.8 > client. Did not try with 1.7 client.
A status update: I can successfully authenticate against the server when I use "correct" name of server. i.e. I there are several name forms of server I can use: https:/svnserver/svn https://svnserver.domain1.com/svn https://svnserver.domain2.com/svn https://10.xx.yy.zz/svn When having SSPIPackage Negotiate, first two of name forms (https:/svnserver/svn and https://svnserver.domain1.com/svn) do not work, but last two ones work (https://svnserver.domain2.com/svn and ip-based access). So there's something wrong with our network setup. Server machine is joined to domain2.com, my machine and my user are in domain1.com. Svn 1.7 client works if serf http library is used, i.e. svn list https://svnserver.domain2.com/svn --config-option servers:global:http-library=serf So I have almost working solution, after network problem is fixed. I just have to persuade every team member either to upgrade or to change their servers configuration file. Gert
