Re: possible ssh problem
Hi,
On Fri, Aug 29, 2025 at 04:01:53PM -0700, Paul Scott wrote:
> As far as
>
> 1) Your dyndns.org entry is not pointing to the correct IP address.
>
> ping and looking at my account on dyndns.org, the IP is correct.
>
> 2) Your ISP is blocking incoming connections, either on port 22 or on
> all ports, before it hits your router/server.
>
> I'm not sure how to determine that.
You could tell us what the hostname is and what port you think SSH is
listening on, and we could tell you if we see something that looks like
SSH listening there. Assuming you haven't locked it down tightly with
firewall rules.
> 3) Your router is blocking incoming connections, either on port 22 or
> on all ports.
Someone trying from outside should be able to tell. If you have no
access to another computer outside your home network then the "someone"
could be us.
Just bear in mind that depending on how your network is set up, if you
try to connect to the real global IP of some machine that is on your
network from another thing that is also on your network, it is not
obvious what your router will do with that. This is because the packets
will come in from its LAN (or wifi) interface which may be treated
differently to packets that come in on its WAN interface (in from the
Internet).
> 4) You've forgotten to configure your router to forward incoming port 22
> to your internal host.
>
> 5) You've configured your router to forward incoming port 22, but to the
> wrong internal IP address.
>
> I haven't knowingly changed anything on my router.
It is a good idea to check even so.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Reply to: