8 May
2013
8 May
'13
1:30 p.m.
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
Thanks. It is getting more complicated :( I am in an internet cafe
using Windows and cannot run that command. When I arrive where I am
staying I will have access to a bash command line. A few minutes ago I
successfully logged into the box using putty. I looked at
/var/log/security and the previous attempts to log in were recorded. I
guess that means that the initial ssh request was received.
Unfotunately putty then crashed and I am unable to access it at all
now. There is no response to a ping. Maybe it is a temporary blip or
the server has crashed (the centos installation can be a bit flaky and
does stop responding every ferw months)
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.
4245
days inactive
4245
days old
0 comments
1 participants
participants (1)
-
Steven Walker