For those who don't know German, this is the translation from Babelfish:
No connection could be made, since the goal computer refused the connection.
I know that VPNs will block ports that they don't want people to use.
It is very possible that your VPN is not allowing traffic on port
3690. Try telnetting to port 3690 on your Subversion server: You
should get something like this:
$ telnet svn-server 3690
Connected to svn-server.
Escape character is '^]'.
( success ( 2 2 ( ) ( edit-pipeline svndiff1 absent-entries
commit-revprops depth log-revprops partial-replay ) ) )
If you don't get that, you have several choices:
1). Try to convince your system admins to allow traffic on port 3690.
2). Try svnserve on another port
3). Use tunneling to get around this problem.
for more information about tunneling. You may have to use ssh to do
the tunneling for you.
One more choice is to do Subversion over HTTP. However, this will
really involve your System Administrators (since they probably control
which machines can run webservers) and may mean you have to make
changes in your repository. Plus, all users might have to do a "svn
switch" since the URL of their chcekouts changed.
On Wed, Mar 18, 2009 at 8:59 AM, Merlin Morgenstern
> Hi there,
> I am trying to get svn running over a vpn tunnel. Unvortunatelly there seems
> to be something I am missing. The tunnel is up an running, ping works.
> Subversion is set up and running as stand alone version.
> After I do a checkout:
> Subversion answers:
> Checkout from svn://10.8.0.6/test, revision HEAD, Fully recursive, Externals
> included Can't connect to host '10.8.0.6': Es konnte keine Verbindung
> werden, da der Zielcomputer die Verbindung verweigerte.
> Do I have to configure subversion somehow to listen to that port 1149 of vpn
> and the ip adress?
> Thank you for any help!!
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-18 15:35:27 CET