On Friday 21 March 2008 12:22:34 pm Néstor wrote: > On Fri, Mar 21, 2008 at 12:19 PM, Néstor <[EMAIL PROTECTED]> wrote: > > On Fri, Mar 21, 2008 at 12:07 PM, Karl Cunningham <[EMAIL PROTECTED]> > > > > wrote: > > > On 3/21/2008 12:01 PM, Néstor wrote: > > > > I am trying to ssh to one of my systems and I get > > > > -------- > > > > ssh wahoo > > > > ssh: connect to host wahoo port 22: No route to host > > > > ----- > > > > > > > > I can ssh to wahoo5 with no problem > > > > I can ssh from wahoo to other systems without a problem. > > > > > > > > I check the /etc/host/ and /etc/resolv.conf on wahoo and compare with > > > > the files on wahoo5 and the are identical. > > > > > > > > I even stop the selinux and firewall (internal system only) on wahoo > > > > but I am still not able to ssh. > > > > > > > > Any ideas? > > > > > > Can you ping both ways? Is there a router or firewall in the path? > > > > > > Karl > > > > > > > > > I can not ping wahoo but wahoo can ping everything > > When I do this command wahoo > nmap -sS -F wahoo: > > Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2008-03-21 12:20 > PST Note: Host seems down. If it is really up, but blocking our ping > probes, try -P0 > Nmap run completed -- 1 IP address (0 hosts up) scanned in 2.053 seconds
ssh by ip address. Eliminate bad host / dns entry. if you successfully reach the machine, check your entries again. If you don't check for static route issues, blocked ports, firewall, static 1-1 nat rules. if you can get out, it's not down, so it's got to be one of these. C. -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
