Felipe Monteiro de Carvalho wrote:
> On Tue, Apr 15, 2008 at 1:21 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>> Only what I said before: I suspect some virus scanner interferring. You
>> said that you deactivated it - but most scanners can't be deactivated that
>> easy: even if you 'quit' them, they still keep running (usually as a service
>> or their hooks in other apps).
> I uninstalled it, but it had no effect. My Windows Firewall is also disabled.
>> Another possibility would be a router/switch/proxy which could cause these
> Maybe. I'm not directly connected to the internet, I'm behind a
> router. What surprises me is that it works on Linux ... Maybe the
> subversion client requires the use of a special port, and my Linux
> installation somehow communicates with the router and frees it, but
> the windows client doesn't do that.
> I know that with my internet accessing http servers with ports other
> then 80 or 8080 fails.
> Any ideas what kind of ports should I free for use by subversion, and
> what kind of configuration would the router need? A big problem is
> that I don't own the router, so I have to contact the internet
> provider for any changes on it.
It has nothing to do with ports. Otherwise you couldn't use your linux
client either and also a checkout wouldn't work. All commands use the
The only thing that's different for a linux client and a windows one is
the authentication that can be used: a windows svn client also tries
authenticating with sspi, and some routers/proxies 'know' that protocol.
If your windows machine is part of a windows domain, try detaching from
that domain and then try again. If that doesn't work, try an 1.5 svn
client (e.g., TSVN-1.5-beta1) and deactivate the sspi authentication in
the Subversion servers config file.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-04-17 17:24:41 CEST