How to fix 'no route to host' problem

[Michael Butash]

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.

-mb

On Tue, Oct 30, 2018 at 7:17 AM Stephen Partington <cryptworks at gmail.com>
wrote:

> 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 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?
>>
>> One reply said, "Can you ping it?"
>>
>> Yes, I can, ping the device ip address. Also did these 2 commands:
>> d: arp -an
>> ? (192.168.0.19) at c4:1c:ff:30:c5:9c [ether] on wlan0
>> ? (192.168.0.7) at 10:0b:a9:9a:99:a8 [ether] on wlan0
>> ? (192.168.0.1) at 52:b9:e5:c9:b9:cc [ether] on wlan0
>> d: ip neighbor
>> 192.168.0.19 dev wlan0 lladdr c4:1c:ff:30:c5:9c REACHABLE
>> 192.168.0.7 dev wlan0 lladdr 10:0b:a9:9a:99:a8 STALE
>> 192.168.0.1 dev wlan0 lladdr 52:b9:e5:c9:b9:cc DELAY
>>
>> But I don't know what to do with the results.
>>
>> Another reply suggested:
>> > So: Go to the target machine and find out what its
>> > IP and MAC are--"/sbin/ifconfig" from the command line
>> > will show that info. Then set up your router such that
>> > it will always give out 192.168.0.4 to that MAC.
>>
>> But I don't know how to set my router so that it will
>> always give out 192.168.0.4 to that MAC.
>>
>>
>>
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
>
>
> --
> A mouse trap, placed on top of your alarm clock, will prevent you from
> rolling over and going back to sleep after you hit the snooze button.
>
> Stephen
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20181030/1e09f55b/attachment.html>