If no route to host in a local subnet, the remote device isn't arping in
the local device cache, which is the most basic networking possible.  Using
"ip neighbor" or old "arp -an" works to see this, but usually means your
remote host isn't getting on the network enough ro even layer 2 arp.

Can you ping it?  If not, check cabling and such to its switch, or reboot
the device as it's networking is hozed.  I'm thinking no ping, which means
one or the other isn't really online.

-mb

On Fri, Oct 5, 2018 at 4:35 PM Joe Lowder <joe@actionline.com> wrote:

> 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?
>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss