Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.security.ssh > #252
| From | pk <pk@pk.invalid> |
|---|---|
| Newsgroups | comp.security.ssh |
| Subject | Re: Using a local proxy with putty fails immediately |
| Date | 2012-01-27 13:28 +0100 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <jfu58g$36a$1@speranza.aioe.org> (permalink) |
| References | <jfrecn$tbc$1@speranza.aioe.org> <4Bn*VqkYt@news.chiark.greenend.org.uk> |
On 27 Jan 2012 11:55:40 +0000 (GMT), Jacob Nevins
<jacobn@chiark.greenend.org.uk> wrote:
> pk <pk@pk.invalid> writes:
> >Following all the docs I could find, I'm doing:
> >
> >in the main window: user@internalpc, port 22, protocol SSH
> >
> >in the proxy config panel: local proxy, and local proxy command is
> >
> >plink.exe -i privatekey.ppk user@externalpc -nc %host:%port
> >
> >This is running under Windows 7. However, when I try to connect, I
> >immediately get an error "server unexpectedly closed network connection".
>
> What version of PuTTY?
0.62, downloaded from the official page.
> Have you tried specifying the full path to plink.exe and to your .ppk
> file in the "Telnet command, or local proxy command" field?
>
> I quickly tried this with PuTTY 0.62 on Windows XP with the full path
> (but without the -i); it worked for me.
I hadn't, now I did, and it fails in the same way :-(
I tried both using single backslashes (eg c:\windows\system32\plink.exe,
same for ppk file) and double backslashes (eg
c:\\windows\\system32\\plink.exe, same for ppk file). Just in case, I
tried with forward slashes as well...same failure.
In the meanwhile, I learned about plink -load option, so I tried creating
and saving a putty session for user@externalpc using public key
authentication (which works fine), and then using "plink -load
externalsession -nc %host:%port" as the internal proxy command, but
unfortunately again no joy.
It's instantaneous: I click "connect", and immediately putty's black
window appears, with the error message's white box on top of it ("server
unexpectedly closed network connection"). Just out of curiosity, I tried
running wireshark while I was clicking "connect", it looks like no traffic
at all is produced, I don't even see a SYN packet towards any host!
For what it's worth, this is a 64-bit windows 7 running in a KVM virtual
machine. Are there known issues with some of that?
Thanks!
Back to comp.security.ssh | Previous | Next — Previous in thread | Next in thread | Find similar
Using a local proxy with putty fails immediately pk <pk@pk.invalid> - 2012-01-26 12:45 +0100
Re: Using a local proxy with putty fails immediately Jacob Nevins <jacobn@chiark.greenend.org.uk> - 2012-01-27 11:55 +0000
Re: Using a local proxy with putty fails immediately pk <pk@pk.invalid> - 2012-01-27 13:28 +0100
Re: Using a local proxy with putty fails immediately Jacob Nevins <jacobn@chiark.greenend.org.uk> - 2012-01-27 13:43 +0000
Re: Using a local proxy with putty fails immediately pk <pk@pk.invalid> - 2012-01-27 16:18 +0100
Re: Using a local proxy with putty fails immediately Jacob Nevins <jacobn@chiark.greenend.org.uk> - 2012-01-30 11:51 +0000
Re: Using a local proxy with putty fails immediately pk <pk@pk.invalid> - 2012-01-30 13:13 +0100
Re: Using a local proxy with putty fails immediately Owen Dunn <owend@chiark.greenend.org.uk> - 2012-01-28 11:00 +0000
csiph-web