:) ...
In the IT world it takes time to analyze a problem well !!
Congrats ...
Happy Easter !!
On 4 April 2015 at 13:06, Mike wrote:
> Thank you for the suggestions Gary. I realized that my problem is caused
> by the router firmware. Basically, they introduced loopback blocking and
> I couldn
Why are you testing a NATED address from the same server ( client and
server ) ?
Do you get the same problem when connecting via the NATED address from the
outside network ... using a different client machine from outside ?
On 20 February 2015 at 20:43, Gary Salisbury
wrote:
> Did this u
flow I described is for problem
> isolation only. Putty cannot connect either.
>
> On Fri Feb 20 2015 at 18:31:15 Gary Salisbury <708...@bugs.launchpad.net>
> wrote:
>
> > Use dbclient ...
> >
> > On 20 February 2015 at 19:07, Mike wrote:
> >
> > &
Use dbclient ...
On 20 February 2015 at 19:07, Mike wrote:
> Hello,
> Not sure it is the same problem here, but I cannot connect to my machine
> if go through NAT.
> If I connect directly from LAN everything works, but if I use the external
> IP, then I get connection reset after debug1: SSH2_MS
It's not really an answer, this bug has been around in ssh for a year or so
already ...
dropbear doesn't have this issue or older versions of ssh ... they don't
crash , it should have been fixed by now.
On 21 December 2012 18:44, Andrew Schulman
wrote:
> Multiple commenters (#19, #43) have posted
Use dropbear
On 21 December 2012 15:27, Nicolas Michel
wrote:
> I have the same problem here. Only on one remote host:
>
> sylock@sylock-vmware:~$ ssh -vvv XX
> OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012
> debug1: Reading configuration data /home/sylock/.ssh/config
> deb
