Note that there are some explanatory texts on larger screens.

plurals
  1. POConnecting to SVN server behind corporate firewall from home
    text
    copied!<h2>How can I configure TortoiseSVN to connect to a SVN server behind a corporate firewall from home?</h2> <p>This is the question I'm having a hard time finding an answer to. Here's what I <strong>DON'T</strong> have:</p> <ol> <li><em>Official</em> VPN access to the corporate intranet.</li> <li>Control over the SVN server.</li> <li>Any control over the intranet.</li> <li>Cooperation from the IT department.</li> </ol> <p>Here's what I <strong>DO</strong> have:</p> <ol> <li>Full control over my computer at my desk at the office.</li> <li>Willpower</li> </ol> <p>This is a shot at what I tried, and seem to be unsuccessful at (names of people and places and machines have been changed to protect the innocent):</p> <p><a href="http://i48.tinypic.com/or1a3b.png" rel="noreferrer">Sweet network diagram of fail http://i48.tinypic.com/or1a3b.png</a></p> <ol> <li>I am using <a href="http://www.wippien.com/" rel="noreferrer">Wippien</a> to set up a zero configuration VPN from my home computer (NG-ATHOME) to my work computer at my desk. This works, I have total network access to and from both machines.</li> <li>I have <a href="http://sshwindows.sourceforge.net/" rel="noreferrer">OpenSSH for Windows</a> running on NG-WORKBOX.</li> <li>I have PuTTY on NG-ATHOME connecting to NG-WORKBOX to tunnel dynamically over port 1080. The SOCKS proxy is working, as I can verify that with any web browser. I can confidently say that this is not the problem in the scenario.</li> <li>I am using TortoiseSVN on NG-ATHOME configured to use a proxy on 127.0.0.1:1080. When I try to hit "svn://NG-SOURCE/PonyRepository", I get <em>error: cannot connect to host</em>. I can ping NG-SOURCE fine.</li> </ol> <p>Why doesn't SVN work?</p> <p>Hmm, I have a suspicion that SVN does not like SOCKS. Anyone have a suggestion?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload