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 gatewa
On 08/08/2012 10:21 PM, Bill Shirley wrote:
> # nmap -sP 192.168.1.0/24
>
> should find it.
I am glad you said "should".
Running this on my network failed to find my Android tablet the 1st, 2nd, and
3rd time around.
Also, I have 7 systems on one subnet. Sometimes this command finds all
7
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.1
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 h
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
'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
hav
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
>
On 8/8/2012 10:05, Martin Briza wrote:
> On Wed, 08 Aug 2012 16:01:01 +0200 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
On Wed, 08 Aug 2012 16:01:01 +0200 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.1
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.
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
roo
11 matches
Mail list logo
