7 May
2013
7 May
'13
8:23 p.m.
I am in Spain at the moment and am unable to log into my Bitfolk vm.
I could log in with no problem from England so can a friend in Florida
and it works from Brazil. The people I am staying with could log in
from an internet cafe so I think the problem is the ISP who is ya.com
part of Orange.
This is what happens (using a Mac)
zaphod$ ssh -vvv -p 2222 swalk(a)swalk.eu
OpenSSH_5.2p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to swalk.eu [85.119.82.47] port 2222.
debug1: Connection established.
debug1: identity file /Users/zaphod/.ssh/identity type -1
debug1: identity file /Users/zaphod/.ssh/id_rsa type -1
debug1: identity file /Users/zaphod/.ssh/id_dsa type -1
ssh_exchange_identification: Connection closed by remote host
Can anyone advise me on what the problem is, why an ISP might do
whatever it does to stop the connection or suggest some sort of work
around.
Steve
PS I know I should be using SSH with authentication key instead of
password but I have been a bit lazy getting around to it.
7 May
7 May
8:33 p.m.
Hello,
On Tue, May 07, 2013 at 09:23:44PM +0100, Steven Walker wrote:
This is what happens (using a Mac)
zaphod$ ssh -vvv -p 2222 swalk(a)swalk.eu
OpenSSH_5.2p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to swalk.eu [85.119.82.47] port 2222.
debug1: Connection established.
debug1: identity file /Users/zaphod/.ssh/identity type -1
debug1: identity file /Users/zaphod/.ssh/id_rsa type -1
debug1: identity file /Users/zaphod/.ssh/id_dsa type -1
ssh_exchange_identification: Connection closed by remote host
What does "tcptraceroute 85.119.82.47 2222" look like? Here's what
it looks like from Zen DSL:
$ sudo tcptraceroute 85.119.82.47 2222
Selected device eth0, address 192.168.0.8, port 42248 for outgoing packets
Tracing the path to 85.119.82.47 on TCP port 2222, 30 hops max
1 192.168.0.7 0.539 ms 0.456 ms 0.459 ms
2 192.168.1.1 1.271 ms 1.118 ms 1.151 ms
3 losubs.subs.dsl1.th-lon.zen.net.uk (62.3.84.17) 20.372 ms 20.937 ms 21.221 ms
4 ge-2-1-0-127.cr2.th-lon.zen.net.uk (62.3.84.237) 21.579 ms 20.602 ms 21.884 ms
5 195.66.224.34 21.450 ms 22.067 ms 22.186 ms
6 kwak.bitfolk.com (85.119.80.6) 21.823 ms 21.810 ms 21.224 ms
7 swalk.eu (85.119.82.47) [open] 22.171 ms 21.821 ms 21.212 ms
Can anyone advise me on what the problem is,
Probably something in the middle is injecting a TCP reset or
otherwise blocking the connection. The tcptraceroute may help to see
where.
why an ISP might do whatever it does to stop the
connection
I can't really speculate as to why they might not want you to use
port 2222. Maybe the number 2222 is against the law there.
or suggest some sort of work around.
Does port 22 work?
PS I know I should be using SSH with authentication
key instead of
password but I have been a bit lazy getting around to it.
The problem here seems more fundamental.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
16 May
16 May
9:09 a.m.
On Tue, May 07, 2013 at 09:23:44PM +0100, Steven Walker wrote:
ssh_exchange_identification: Connection closed by
remote host
After chatting to Steven off-list I understand this was tracked down
to a denyhosts issue.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
4237
days inactive
4246
days old
2 comments
2 participants
participants (2)
-
Andy Smith -
Steven Walker