FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 08-08-2012, 02:40 PM
"Bob Goodwin - Zuni, Virginia, USA"
 
Default F-17 SSH -

On 08/08/12 10:10, Ed Greshko types:

On 08/08/2012 10:01 PM, Bob Goodwin - Zuni, Virginia, USA wrote:

Replaced F-16/64 with F-17/64 on "box7" and see a problem I seem to
have every time I do this.

Presently box7 will ssh into box9 but box9 can not get into box7,

[root@box9 .ssh]# ssh bobg@192.168.1.7
ssh: connect to host 192.168.1.7 port 22: No route to host
root or user,

[bobg@box9 ~]$ ssh bobg@192.168.1.7
ssh: connect to host 192.168.1.7 port 22: No route to host

sshd is enabled and running on both, I've tried rm'ing "known_hosts"
and letting it regenerate, all to no avail.

I've seen this with several generations of Fedora [and different
equipment] and it's always the same, a few days or weeks later it
magically begins to work! All my computers in this room connect to a
gigabit switch, [even the switch has been replaced], and our
wireless LAN.

At times this is a serious inconvenience leading to typing errors, etc.

Any ideas what I have missed?


Assuming you've ssh'd to yourself on box7 and that works....sounds as if your firewall doesn't have port 22 open.




Ok,the firewall is the problem! I had run "setup" as I have done
many times and saw nothing out of the ordinary, looked the same [but
obviously something was different] so I dropped that idea.

Now I disabled the firewall and immediately got a connection from
box9, re-enabled the firewall, it still connects?

[bobg@box9 ~]$ ssh bobg@192.168.1.7
bobg@192.168.1.7's password:
Last login: Wed Aug 8 10:30:11 2012 from box9


I guess this makes me look even less competent than usual but I did
look at this earlier and saw no reason to suspect the firewall. Will
add that to my Linux notes ...

Thanks to all,

Bob


--
http://www.qrz.com/db/W2BOD


box9

--
users mailing list
users@lists.fedoraproject.org
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
 
Old 08-08-2012, 03:07 PM
"Bob Goodwin - Zuni, Virginia, USA"
 
Default F-17 SSH -

On 08/08/12 10:21, Bill Shirley types:

'No route to host' means the box is not there. Does ping work? Maybe it
moved to a different address.

# nmap -sP 192.168.1.0/24

should find it.

Bill


It was a firewall problem but "nmap" is a command/application I
needed to know about. It should help me to detect new devices that
appear on our LAN. Installed it on both computers. I usually rely on
the [dd-wrt] router dhcp clients list. Have made a note of that.

Thanks,

Bob



--
http://www.qrz.com/db/W2BOD

box9

--
users mailing list
users@lists.fedoraproject.org
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
 
Old 08-08-2012, 04:23 PM
Rick Stevens
 
Default F-17 SSH -

On 08/08/2012 07:01 AM, Bob Goodwin - Zuni, Virginia, USA issued this
missive::


Replaced F-16/64 with F-17/64 on "box7" and see a problem I seem to
have every time I do this.

Presently box7 will ssh into box9 but box9 can not get into box7,

[root@box9 .ssh]# ssh bobg@192.168.1.7
ssh: connect to host 192.168.1.7 port 22: No route to host
root or user,

[bobg@box9 ~]$ ssh bobg@192.168.1.7
ssh: connect to host 192.168.1.7 port 22: No route to host

sshd is enabled and running on both, I've tried rm'ing "known_hosts"
and letting it regenerate, all to no avail.

I've seen this with several generations of Fedora [and different
equipment] and it's always the same, a few days or weeks later it
magically begins to work! All my computers in this room connect to a
gigabit switch, [even the switch has been replaced], and our
wireless LAN.

At times this is a serious inconvenience leading to typing errors, etc.

Any ideas what I have missed?


"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.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- "Men occasionally stumble over the truth, but most of them pick" -
- themselves up and hurry off as if nothing had happened." -
- -- Winston Churchill -
----------------------------------------------------------------------
--
users mailing list
users@lists.fedoraproject.org
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
 

Thread Tools




All times are GMT. The time now is 11:20 AM.

VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org