Well put Rusty. The host simply isn't there anymore when you get "no route
to host"
That "route" is one of two things. One, an arp entry for a local subnet
host, broadcasting a "arp whois" query, and gets an "arp tell" if that host
responds. Two, an actual layer 3 route, either default or
You might consider initiating the rsync from the backup machines, and even
possibly on a cron job basis.
Also, I would have been surprised if the uninstall/reinstall of sshd would have
helped, as its clearly a network issue, not an ssh issue - at least the 'no
route to host' (which is an
Thanks Rusty, Michael, and all ...
But I think I need a different solution than
"if all else fails" ;)
I have more than a dozen devices on my network
including four "back-up" computers to which I have
been using rsync to copy all of my most important
files on a regular basis. rsync is still
If all else fails and if you have control over the range of addresses that DHCP
gives out (at least enough to tell it to leave a few un-assigned), you could
always force the server to be at a static IP address.
That is, either using network manager or whatever method you desire (including
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:
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
DHCP IP Address reservation or Assignments in your router will be a bit odd
looking in most home routers, but once you find it very simple. This will
still vary based on device but an example can be found here.
https://www.linksys.com/us/support-article?articleNum=135673
On Mon, Oct 29, 2018 at
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
On Fri, Oct 5, 2018 at 4:35 PM Joe Lowder 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
ssh: connect to host 192.168.0.4 port 22: No route to host
On 2018-10-06 16:02, Michael
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
If I can make a random guess. It's more than likely a firewall issue with
the router or said computer. -- I'm betting it's the router. Especially if
the computers you are attempting to rsync is on different wlan and lan.
Without knowing too much about your network setup, and what you tried so
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
12 matches
Mail list logo
