[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Auth works for all client PCs, except one

From: Jody Shumaker <jody.shumaker_at_gmail.com>
Date: 2006-01-03 22:18:28 CET

On 1/3/06, Stefan Küng <tortoisesvn@gmail.com> wrote:
>
> Jody Shumaker wrote:
>
> > This is the issue, apache log shows it as user Guest. Can TortoiseSVN
> > be changed so it prompts the user if the current credentials fail? This
> > all worked fine before, but now anyone trying to access the server
> > outside the office will likely have this problem.
>
> Very unlikely. Users outside your office won't be part of the same
> domain, so SSPI won't work at all and then it should work as before.

I've increased the retry limit in revision 5339 (also backported to 1.3.x).
> Can you please try the next nightly build (the 1.3.x folder).

Unfortunately, this is exactly where I ran into the problem. If they aren't
part of the same domain and the Guest user is enabled, it uses that. I
confirmed that disabling the Guest user changed the behavior, but not for
the best. I'm not sure increasing the retry limit would be a good thing?
With the Guest account disabled, a checkout never resulted in an error
dialog. Instead it started listing over 240mb transferred at greater than
11,000kbyte/s. It kept going up so I cancelled it and checked the apache
logs. It had repeatedly been getting a 401 errors 5-20/second.

> Oh yes, please do! In that case, you should write directly to the
> Subversion dev list, not the user list.

Ok thanks, I'll retry everything with the svn command line and report my
problems there, thanks for your time.

> This looks good. Maybe you can try once with the
> SSPIOfferBasic On
> changed to
> SSPIOfferBasic Off
> and check the apache log if that makes any difference.

I'll give this a try later when people won't send death threats for
restarting apache.

Thanks,
Jody
Received on Tue Jan 3 22:35:40 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.