SSHD Configuration question

[Alvin]

On Wednesday 26 August 2009 17:28:08 Rob Wright wrote:
> Greetings,
>
> I'm trying to get SSHD working on my desktop here at the office so that I
> can access it remotely from home. I'm using Jaunty on both machines. SSHD
> is running, listening on an alternate port, and is accessible if I do "ssh
> localhost"
>
> My problem is that I cannot connect to this box from a remote computer not
> on the local network. If I try to ssh into this computer from another on
> the same subnet I have no problem connecting. The connection will just
> hang, eventually timing out; I never get a login prompt, nor do I get a
> denial of my login.  I can ssh into another computer on the local subnet
> and then leapfrog into my desktop, so I don't think it's a routing or
> firewall issue for SSH in general, and until I upgraded to Jaunty I was
> able to connect to this machine. Just for giggles, last week I installed
> SuSE and the SSH worked fine with the exact same setup.
>
> To clarify: (192.168.1.11 is the machine in question)
> ssh -p 2748 localhost   works
> from 192.168.1.2 ssh -p 2748 -l username 192.168.1.11 works
> from 192.168.2.2 ssh -p 2748 -l username 192.168.1.11 does not work
> from 192.168.2.2 ssh -p 2748 -l username 192.168.1.2 works
> from 10.1.1.1 ssh -p 2748 -l username 192.168.1.2 works
> from 10.1.1.1 ssh -p 2748 -l username 192.168.1.2 | ssh -p 2748 -l username
> 192.168.1.11 works
>
> /etc/hosts.allow
> # Allow SSH for me
> sshd : ALL
>
> sudo iptables --list
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
> It may still be some routing or fire issue, but I have access to that
> equipment and so far haven't been able to find anything; and like I said,
> with a different Linux flavor installed it works fine. Just wondering if
> there is any new config or hidden default in Jaunty that might be getting
> in my way.

Still sounds like a routing problem to me. Might be the gateway settings on 
your desktop.

Check with $ route -n
Use tracepath from both computers
Can you ping to your desktop?