Mike Lovell wrote: > Joshua Lutes wrote: >> Sorry. I thought that I had and then right after I sent the last >> message I doubted but didn't check. >> >> ssh -v 192.168.2.3 >> OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007 >> debug1: Reading configuration data /etc/ssh/ssh_config >> debug1: Applying options for * >> debug1: Connecting to 192.168.2.3 [192.168.2.3] port 22. >> debug1: connect to address 192.168.2.3 port 22: No route to host >> ssh: connect to host 192.168.2.3 port 22: No route to host >> > So it looks like the one box can't find a route to get to the other.
Not necessarily. This is often the result of iptables on that box rejecting connections. Can you ping the box? If so, the routing is fine, and ought to be on a local LAN since everything is within the broadcast domain. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
