On 08/08/12 12:23, Rick Stevens types:
"No route to host" is almost certainly a network issue. It means that
box9 has no network route to 192.168.1.7. Make certain that box9 has
its IP address and netmask set properly. If box9 is on a different
network than 192.168.1.7, make sure that the gateway is also set.
"traceroute 192.168.1.7" would also be your friend.
-------------------
Yes, that works now! Apparently when you disable/re-enable the
firewall it is reconfigured? That's all I did to "fix" the problem
and probably explains the past episodes where the ssh problem would
clear, I probably messed with firewall "on/off" for some other
reason ....
[bobg@box9 ~]$ traceroute 192.168.1.7
traceroute to 192.168.1.7 (192.168.1.7), 30 hops max, 60 byte
packets
1 box7 (192.168.1.7) 0.193 ms !X 0.109 ms !X 0.103 ms !X
Thanks for the suggestions,
Bob
--
http://www.qrz.com/db/W2BOD
box9
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
