Re: possible ssh problem
On Thu, 28 Aug 2025 14:53:24 -0700
Paul Scott <waterhorsemusic@aol.com> wrote:
> I can ping my desktop from my laptop with its dyndns.org address. The
> address is maintained by ddclient.
>
> From several months ago ssh to that same address times out. (This
> worked for years before that.)
>
> I don't know how to diagnose this.
The first thing I would do is ping the desktop (from outside your home
network). While pinging, verify that the name resolution is correct.
Once you are sure that is working, I would ssh -v and see what that
says. Try adding vs to get more detail. (See the man page.) If nothing
jumps out at you, feel free to share the results with us (after
suitable redacting).
If you have telnet on the laptop, try telnetting in to the desktop using
the appropriate port. The standard port for SSH is 22. You should see
something like this:
charles@hawk:~$ telnet peregrine 22
Trying 192.168.100.47...
Connected to peregrine.
Escape character is '^]'.
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u7
^]
telnet> quit
Connection closed.
charles@hawk:~$
It is possible that your ISP has decided to block port 22 to protect
you. You might try a high port.
Do you have an entry in the laptop's ~/.ssh/config? E.g. I have for the
purpose:
host remotehawk
port 1772
Protocol 2
hostname example.org
ForwardX11 yes
ForwardX11Trusted yes
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: