views:

1440

answers:

2

Heres the current setup.

Home PC ---/ Internet /---> Work Proxy Server --/ LAN /--> SVN server

  • Home PC running Windows XP.
  • Work Proxy server running fedora-core (to which I can connect through ssh).
  • SVN server is inside the Office LAN running Windows XP.

I want to connect to the work svn server commit changes, update and checkout from the home PC.

I can tunnel to my Work SVN PC (not the service) with no problems, which I currently use with VNC (using PuTTY).

Currently using Tortoisesvn for a client.

Thanks for any help!

+2  A: 

You need to configure a tunnel port in PuTTY so that you'll connect to localhost:someport on your home PC, and PuTTY will tunnel all traffic between the two.

Depending on the SVN server setup you'll want to use either port 80 (http:), 443 (https:) or 3690 (svn:).

This tutorial is slightly outdated, but still applies here.

Ben S
Thanks Ben, I can tunnel just fine. How do I use the client to commit changes to the server?
saint
Instead of using the URL you use at work, connect to localhost:3690 (or whatever port you forwarded). This will connect locally to the PuTTY tunnel.
Ben S
+1  A: 

Assuming your work proxy machine has access to the SVN server, you would set up a tunnel like this with regular SSH: ssh -L localport:svnserver:svnport username@proxyserver. You'll need to figure out the equivalent options for PuTTY, perhaps by using that link Ben S provided. Once you've set up the tunnel, all your SVN operations will be going through localport on your local computer, so you'll need to set up Tortoise to treat your local machine on that port as the SVN server (using either a new checkout or an svn switch --relocate on an existing working copy.

rmeador
how do I access the repo after that? svn://localhost/svnrepos
saint
you would access it exactly the same as you normally would, except replace the SVN server's hostname with "localhost". The URL you gave in your comment could very well be the correct one.
rmeador
The host actively refused the connection. Thats what I get, but it works on the server. Oh well, will try find away :) thanks for the help
saint
I never got around to make it work with svn://* but its working fine with VisualSvn HTTP
saint