Also, these are the default settings for a separate install of PuTTY
(along with Pageant which I use to avoid recurrent password prompts
when using svn+ssh). I didn't realize that it would influence the
behavior of TortoiseSVN. I guess they use the same configuration files
or registry entries?
On Tue, Nov 18, 2008 at 1:07 PM, Stephen Dewey
<stepheneliotdewey_at_gmail.com> wrote:
> On Tue, Nov 18, 2008 at 11:36 AM, Kurt Pruenner <leak_at_gmx.at> wrote:
>> Stephen Dewey wrote:
>>> On Tue, Nov 18, 2008 at 10:25 AM, Stephen Dewey
>>> > I am still getting the "connection closed unexpectedly" error. I do
>>> > not have problems logging in with this user using PuTTY, and once I
>>> > have logged in with PuTTY, I can easily check out a copy of the
>>> > repository from the same server. But using TortoiseSVN, I am unable
>>> > to do the same thing via svn+ssh.
>>>
>>> FYI, downgrading TortoiseSVN from 1.5.5. to 1.4.8 solved the
>>> "connection closed unexpectedly" error for me.
>>
>> Do you have a host name stored for PuTTY's "Default Settings" session?
>> That will override any and all host names passed to PLink (or rather,
>> TortoisePLink) on the command line...
>>
>
>
> You're right - when I remove the host from the default settings so
> that it is blank instead (I could not remove the port 22 so I kept
> it), TortoiseSVN 1.5.5 does work. I also removed my default login name
> from the default settings.
> The weird thing, though, is that the host for my default settings in
> PuTTY is the same host that I was connecting to anyway - the same IP
> address - so it is hard to see why this would cause an error. I would
> also like to keep the default settings so that I can use PuTTY more
> easily. But it is good to know that this is the problem.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-11-18 19:09:54 CET