can't reach part of the world...

[lesswire]

Hi all,

Let me thank you for running / contributing to this interesting forum.
I found it during a google search to solve my connection problem.

I want to connect from home to my working place via ssh. Attempts to connect simply
time out, and it is not a firewall issue.
I found threads on ssh port 22 blocking and the very good advice to try the ssh
setup using DUCTAPE which runs an ssh server.
It works, ie. I got a login prompt!The output of the traceroute command (I am on a Linux box) is:
====================snip========================== ========
1 192.168.0.1 (192.168.0.1) 1.759 ms 0.789 ms 0.896 ms
2 10.186.248.1 (10.186.248.1) 11.237 ms 12.941 ms 10.121 ms
3 80.235.128.33 (80.235.128.33) 10.725 ms 18.639 ms 14.521 ms
4 195.188.231.13 (195.188.231.13) 13.661 ms 16.289 ms 18.657 ms
5 gfd-bb-a-ge-210-0.network.virginmedia.net (195.182.178.129) 20.358 ms 12.786 ms 13.769 ms
6 213.152.245.49 (213.152.245.49) 27.348 ms 26.228 ms 22.945 ms
7 so-2-1-0.mpr1.lga5.us.above.net (64.125.27.185) 99.168 ms 100.424 ms 110.949 ms
8 so-0-0-0.mpr2.lga5.us.above.net (64.125.27.238) 114.122 ms 112.116 ms 105.565 ms
9 * * *
10 so-7-1-0-0.BB-RTR1.NY325.verizon-gni.net (130.81.17.128) 106.699 ms 102.769 ms 151.393 ms
11 130.81.19.111 (130.81.19.111) 110.116 ms 117.013 ms 113.868 ms
12 130.81.17.99 (130.81.17.99) 109.060 ms 108.199 ms 109.161 ms
13 130.81.19.78 (130.81.19.78) 146.033 ms 169.387 ms 165.738 ms
14 130.81.17.69 (130.81.17.69) 162.845 ms 155.148 ms 151.098 ms
15 P6-0.LCR-04.DLLSTX.verizon-gni.net (130.81.29.183) 154.446 ms 152.301 ms 153.955 ms
16 * ductape.net (71.164.213.163) 146.723 ms 145.224 ms
=================snip============================= =============
This tells me that ssh is working and there are no firewall issues pending.

The connection to the ssh server at work (which is basically 2 miles away) fails.
The traceroute shows that the packets don't reach the server at all:
==================snip============================ =
1 192.168.0.1 (192.168.0.1) 1.011 ms 0.772 ms 0.880 ms
2 10.186.248.1 (10.186.248.1) 8.089 ms 14.013 ms 12.329 ms
3 195.188.231.67 (195.188.231.67) 16.099 ms 14.100 ms 11.622 ms
4 195.188.231.21 (195.188.231.21) 14.095 ms 17.500 ms 15.015 ms
5 win-bb-b-ge-220-0.network.virginmedia.net (195.182.178.133) 16.405 ms 18.951 ms 17.018 ms
6 bre-bb-a-so-100-0.network.virginmedia.net (62.253.185.197) 15.148 ms 14.419 ms 16.201 ms
7 nth-bb-b-so-310-0.network.virginmedia.net (212.43.162.218) 21.198 ms 26.345 ms 20.700 ms
8 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 20.206 ms 18.555 ms 19.593 ms
9 212.250.14.34 (212.250.14.34) 22.648 ms 18.152 ms 15.094 ms
10 xe-5-1-1.lond-sbr4.ja.net (146.97.35.149) 23.180 ms 18.309 ms 16.626 ms
11 so-5-0-0.read-sbr1.ja.net (146.97.33.161) 22.682 ms 21.808 ms 19.322 ms
12 SWERN-B2.site.ja.net (146.97.42.186) 26.940 ms 27.686 ms 23.201 ms
13 ply-fren-ph.swern.net.uk (194.83.94.129) 26.017 ms 29.575 ms 27.183 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
===================snip=========================== ============

What should I make out of this?

I would be gratefule for any help!

Best regards,

lesswire

[caph]

Do you know for sure that port 22 is open inbound at your work and translated to the correct internal IP? Does anyone else use ssh successfully to your work? Possibly a firewall/port forwarding problem at your work's end?

[chickendippers]

The traces leaves the Virgin Media network, so clearly the problem doesn't lie there. Personally I have no issues connecting to SSH on my servers on port 22 using putty.

[lesswire]

Thank you for your replies.
The ssh sever at the destination certainly allows incoming ssh connections.
Good point: I agree that it has nothing to do with Virgin Media network. It must happen when the packets
enter the realm of the intranet at work. Thanks again.