[SWLUG] using ssh to talk to a server?

[Daniel Morris]

On Fri, May 02, 2008 at 11:22:28AM +0100, Pete Prior wrote:
> Sounds like a network routing problem not an ssh one :|
> 
> what happens if you run
> 
> (on 192.168.1.2): route add default gw 192.168.1.2
> (on 192.168.1.3): route add default gw 192.168.1.3
> 
> then try again

If the routing is correct, has sshd on the server definitely been 
restarted/sent a SIGHUP after making your changes to the config file
on the server?

'ssh -v -p 9876 192.168.1.2'

from the client will give you lots of useful info too, including showing
where it found key information (in case you have a stale entry in
your ~/.ssh/config).

 Daniel

> Mark Summerfield wrote:
> > On 2008-05-02, you wrote:
> >> (on 192.168.1.3)
> >>
> >> ssh -p 9876 192.168.1.2
> > 
> > I did that and got:
> > 
> > ssh: connect to host 192.168.1.2 port 9876: No route to host
> > 
> > (I tried as user mark and as root and got the same message both times.)
> > 
> > But on the same machine when I do ssh 192.168.1.2 it asks for my
> > password (for the other machine) and when I give it I get logged in with
> > no problem. (And doing ssh 192.168.1.3 on the other machine also works
> > fine.)
> > 
> >> Pete
> >>
> >> Mark Summerfield wrote:
> >>> Hi,
> >>>
> >>> I'm trying to do this:
> >>>
> >>> Machine 192.168.1.2 (Fedora 8)
> >>>     run a server on port 9876
> >>>
> >>> Machine 192.168.1.3 (Kubuntu 8)
> >>>     talk to machine 192.168.1.2's server on port 9876.
> >>>
> >>> Both machines are running sshd.
> >>>
> >>> I've tried using ssh -R and -L but I can't get it to work and I just
> >>> don't understand the ssh man page. Surely this is easy to do?
> >>>
> >>> Thanks!
> > 
> _______________________________________________
> SWLUG Discussion List - Discuss at swlug.org
> http://swlug.org/mailman/listinfo/discuss
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________