How to fix 'no route to host' problem

[Joe Lowder]

ping 192.168.0.11 works okay:
PING 192.168.0.11 (192.168.0.11) 56(84) bytes of data.
64 bytes from 192.168.0.11: icmp_seq=1 ttl=64 time=4.07 ms
64 bytes from 192.168.0.11: icmp_seq=2 ttl=64 time=123 ms
64 bytes from 192.168.0.11: icmp_seq=3 ttl=64 time=3.88 ms

nmap -sP 192.168.0.11 returned this:

Starting Nmap 6.40 ( http://nmap.org ) at 2018-10-30 15:44 MST
Nmap scan report for joe-dell-Inspiron-3542.domain (192.168.0.11)
Host is up (0.0045s latency).
Nmap done: 1 IP address (1 host up) scanned in 0.01 seconds

ssh joe at 192.168.0.11 returned this:

ssh: connect to host 192.168.0.11 port 22: Connection refused


------------------
On Tue, October 30, 2018 2:14 pm, Michael Butash wrote:
> If you can't ping it, see no arp on your local network, or "no route to
> host", it's not there on that ip any more.  Doesn't mean it didn't get
> another ip address different as recommended above to static your dhcp,
> but it's not on that IP any longer.
>
> I like to do "nmap -sP 192.168.1.0/24" or whatever your subnet is there,
> and see what comes back for what lives there, if name resolution is
> present, or mdns capable, you should see names.  It probably just got a
> new lease.


-----------------
>> On Mon, Oct 29, 2018 at 8:21 PM Joe Lowder <joe at actionline.com> wrote:
>>
>>> I still need help to solve this problem:
>>>
>>> I recently wrote this:
>>>
>>>> For many months, I have been using rsync to copy files
>>>> from one of my computers to two others, and it has worked
>>>> flawlessly.
>>>> But today, it quit working and I cannot figure out why and how
>>>> to correct the problem. Below is the error message I now see:
>>>>
>>>> ssh: connect to host 192.168.0.4 port 22: No route to host
>>>> rsync: connection unexpectedly closed (0 bytes received so far)
>>>> [sender]
>>>> rsync error: unexplained error (code 255) at io.c(226)
>>>> [sender=3.1.0]
>>>>
>>>> What do I need to do to correct this problem?