Correct way to debug SVN + SSH verification through VPN failure? How to compare with a working installation?

Briefly

Given the setup, when checking SVN + SSH over VPN does not work and the other where it works, what is the correct procedure to find out what is the difference between the two systems?

More details

I am using a 64-bit system running Windows 7. I have 64-bit Open VPN and Tortoise SVN installed.

The repository is on the remote system and we are connecting to the VPN.

Continuing my previous question Checking SVN + SSH over VPN using SVN Turtle, Smartsvn Fails

One new teammate (working specifically with the system, with 64-bit Windows 7 starts, just like me) successfully passed the test from a remote server (connected via Open VPN). We both followed the same steps -

  • Added some open source Open VPN configuration files in the config folder of the Open VPN installation path. These files were taken from the working settings of other team members.
  • Initiated opening of a VPN connection using a user.
  • launched Putty Pageant.exe, selected the .ppk file and entered the passphrase.

After its verification was successful, I did a new software installation (OpenVPN, tortoiseSVN) using the exact ones that it used, but still getting the following error when trying to check or use the repository browser.

enter image description here

Reading Error -

To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
Network connection closed unexpectedly

-q. SVN + SSH VPN SVN, Smartsvn, , .

, Windows , . - . -

enter image description here

. , Open VPN, . , .

, ?

+3

All Articles