[ubuntu-za] Advice troubleshooting ssh over the net

chesedo pehshelchesed at gmail.com
Tue Aug 1 08:36:41 UTC 2017


Are you trying to connect (test) to the WAN's IP from within the network 
(while from external, ie Anton, is successful)?

Pieter


On 31/07/2017 16:03, Wesley Werner wrote:
> On Afrihost ADSL Wayne. Anton has helped prove that the port is indeed 
> open and outward facing. In fact he was able to initiate a connection 
> to my server's ssh port. Since I can't connect through the WAN IP, I 
> will have to poke around some more.
>
> On Mon, Jul 31, 2017 at 3:33 PM, Wayne Abroue <plettpc at gmail.com 
> <mailto:plettpc at gmail.com>> wrote:
>
>     Who are you using as ISP?
>     Cell companies block incoming by default.
>
>     Wayne A
>
>     On Mon, Jul 31, 2017 at 2:32 PM, Anton May <antonmay at gmail.com
>     <mailto:antonmay at gmail.com>> wrote:
>
>         Sent you a google hangouts request. Going to be easier
>
>         On 31 July 2017 at 14:29, Wesley Werner
>         <wesley.werner at gmail.com <mailto:wesley.werner at gmail.com>> wrote:
>
>             Thanks Anton, Yes I am using the WAN IP address.
>
>
>             On Mon, Jul 31, 2017 at 2:21 PM, Anton May
>             <antonmay at gmail.com <mailto:antonmay at gmail.com>> wrote:
>
>                 Hi Wesley
>
>                 Although you have stated that you have done the port
>                 forwarding, I suspect somewhere is a misconfig. Let's
>                 first eliminate DNS, have you tried to ssh via the WAN
>                 IP address?
>
>                 Anton
>
>                 On 31 July 2017 at 14:13, Wesley Werner
>                 <wesley.werner at gmail.com
>                 <mailto:wesley.werner at gmail.com>> wrote:
>
>                     Hi folks. Is everyone good?
>
>                     I am traveling outside the country for business
>                     soon and thought it nice to remotely administer my
>                     headless server at home. I only need ssh access.
>
>                     I have:
>
>                     1) Ubuntu 16.04 that gets assigned a static IP on
>                     my LAN
>                     2) set up SSH access using public key
>                     authentication (no password access)
>                     3) set up the no-ip dynamic dns service
>
>                     I can confirm:
>
>                     1) ssh to the server from two other machines on my
>                     LAN works
>                     2) the no-ip service runs and updates my IP. I can
>                     see syslog indicate the IP update, and verify this
>                     on the no-ip website dashboard, which reflects my
>                     router's IP
>
>                     I cannot ssh into the server using the no-ip
>                     domain name or my external IP address. I figured
>                     since ssh works on the LAN I can rule out the
>                     Ubuntu firewall, so I focused my attention to the
>                     router NAT:
>                     I added a port forward setting on my router for
>                     ssh port 22, pointing it to my server's static IP
>                     on the LAN (this guide provided the steps for my
>                     router model [1]). This did not change anything, I
>                     still cannot ssh to my server. I used a couple
>                     online port checkers that say port 22 is open.
>
>                     The message I get is: ssh: connect to host port
>                     22: Connection timed out
>
>                     any tips in the right direction will be appreciated :)
>
>                     Wes
>
>
>                     [1]: https://portforward.com/huawei/hg532f/
>                     <https://portforward.com/huawei/hg532f/>
>
>
>
>                     --
>                     ubuntu-za mailing list
>                     ubuntu-za at lists.ubuntu.com
>                     <mailto:ubuntu-za at lists.ubuntu.com>
>                     https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>                     <https://lists.ubuntu.com/mailman/listinfo/ubuntu-za>
>
>
>
>
>                 -- 
>                 Regards,
>                 Anton May
>
>                 --
>                 ubuntu-za mailing list
>                 ubuntu-za at lists.ubuntu.com
>                 <mailto:ubuntu-za at lists.ubuntu.com>
>                 https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>                 <https://lists.ubuntu.com/mailman/listinfo/ubuntu-za>
>
>
>
>             --
>             ubuntu-za mailing list
>             ubuntu-za at lists.ubuntu.com <mailto:ubuntu-za at lists.ubuntu.com>
>             https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>             <https://lists.ubuntu.com/mailman/listinfo/ubuntu-za>
>
>
>
>
>         -- 
>         Regards,
>         Anton May
>
>         --
>         ubuntu-za mailing list
>         ubuntu-za at lists.ubuntu.com <mailto:ubuntu-za at lists.ubuntu.com>
>         https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>         <https://lists.ubuntu.com/mailman/listinfo/ubuntu-za>
>
>
>
>     --
>     ubuntu-za mailing list
>     ubuntu-za at lists.ubuntu.com <mailto:ubuntu-za at lists.ubuntu.com>
>     https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>     <https://lists.ubuntu.com/mailman/listinfo/ubuntu-za>
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-za/attachments/20170801/18bf293d/attachment-0001.html>


More information about the ubuntu-za mailing list