windows - Pinging *.5 and replies from *.4

This may belong on SF, migrate if it does!

Pinging 192.168.1.5 with 32 bytes of data:
Reply from 192.168.1.4: Destination host unreachable.
Reply from 192.168.1.4: Destination host unreachable.
Reply from 192.168.1.4: Destination host unreachable.
Reply from 192.168.1.4: Destination host unreachable.

Pinging a windows machine on my home network with the IP 192.168.1.5, Windows is trying to get replies from 192.168.1.4. The machine I am pinging has an automatically obtained IP and it can access the internet fine. The machine I'm pinging from is able to ping any other machine on the network just fine.

I've never encountered anything like this before.

Can anyone shed some light? Why would this be happening?

Things I haven't tried yet:

• Rebooting router


• Rebooting my machine


• Rebooting target machine (or renewing target IP)

Edit: Pinging any "unassigned" IP on the network will try to get replies from my own IP (192.168.1.1 will try to get replies from my own IP) - thanks to regan's answer for pointing me that way. I'm 100% sure this machine is connected to the same network and there is no firewall active.

Answer

To shed some light:

• When you can't ping the IP of a machine, your own IP says it is unreachable.

Things to try:

1. Try the things you haven't tried yet to clean out possible clutter in an easy way.


2. Try to ping the target machine from another machine to see if the target machine is the problem, if the other machine succeeds them the problem is more likely on your machine than on the target machine.


3. In the case that the target machine is the problem, you might want to run the following command as an administrator to enable pings: netsh firewall set icmpsetting all enable


4. If the case that your machine is the problem then it is a weird case, for some reason it doesn't see the target machine but still sees the other machines, but that is a case that normally isn't so common.

Please let us know if this helped or if you have more details. For more information and other possible less general causes, see this on Google: "Destination Unreachable" site:microsoft.com