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?

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

On Wed, 2012-08-08 at 10:01 -0400, 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?
>
> Bob
> .
>
>
> --
> http://www.qrz.com/db/W2BOD
>
> box9
>

Sounds as if one machine doesn't have sshd running on it. That is
presuming that all the machines are on the same subnet and there is no
IP routing that has to be considered.

--
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

On Wed, 08 Aug 2012 16:01:01 +0200 Bob Goodwin - Zuni, Virginia, USA
<bobgoodwin@wildblue.net> 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?

Bob
.


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

box9



I think it's in the network configuration - does box7 really have the
specified IP address? DHCP could have changed it.

--
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

On 8/8/2012 10:05, Martin Briza wrote:
> On Wed, 08 Aug 2012 16:01:01 +0200 Bob Goodwin - Zuni, Virginia, USA
> <bobgoodwin@wildblue.net> 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,
>>
...
>>
>
> I think it's in the network configuration - does box7 really have the
> specified IP address? DHCP could have changed it.

I've had a similar problem, specifically with wirelessly-connected
machines. I know that sshd is running on the target machines, and these
machines report the expected IP address. Generally when this happens,
however, running something like nmap does not find the machine at all.
Once the machine shows up on the network again I can reach it remotely.

-Don
--
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

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.


--
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled
--
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

'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


On 8/8/2012 10:01 AM, 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?

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