On 31.07.2009 15:30, Purple Streak wrote:
> 2009/7/23 Stefan Küng<tortoisesvn_at_gmail.com>:
>> If it's the initial connection that takes much longer than in the svn
>> command line client, then it's most likely an issue with SSPI
>> authentication. The command line client doesn't have SSPI compiled in,
>> so it won't have an issue with that at all.
>>
>> Make sure that your pc is properly joined to the domain server and that
>> your IP address is properly set up and recognized in your DNS server. If
>> one or both are not correct, SSPI takes a long time to find out that
>> this kind of auth works/doesn't work.
>
> Hi Stefen
> I've not been able to find anything wrong. It works fine from another
> machine, so it's something on my current one. I've been tracking down
> another issue with authentication and using cURL
> (http://curl.haxx.se/) which can use sspi and that works instantly.
>
> Is there any way to get some logging out of TortoiseProc to see where
> it's getting messages or should I get a debug build going to try it?
you could try switching to serf instead of neon and see if that makes
any difference. Other than that, there's no logging for such issues.
Neon does have some logging, but that has to be compiled in and only
works in a debug build. So if you really require that kind of logging,
you'd have to build TSVN yourself and tweak the build scripts for neon
to include that logging.
To switch to serf, add the line
http-library = serf
in the svn servers config file (%APPDATA%\Subversion\servers)
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2378586
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-02 10:07:11 CEST