Troubleshooting using Ping - "destination host unreachable"?

which_doctor

Reputable
Aug 31, 2015
52
0
4,640
I'm using an Android device in my home automation setup. It has wifi connectivity (web surfing works, etc) but refuses to accept AutoRemote messages from my Windows 7 PC with Eventghost installed on it.

During my troubleshooting I decided to ping the device (a tablet). Again, I can use the internet on it, and the tablet is visible in my router's device list. However, when pinging, this is what happens:

1272681what_does_this_mean.png


Being pretty new to networking, I don't really know what this means. .104 is the Windows PC i'm pinging from (.102 is the android tablet).... why is it answering its' own ping request? Does this mean my router has been set up dodgily?

This goes up and down tho, because just now I was able to ping my tablet and it replied correctly.... so what could be the error?

Additional details:

  • Router: DLINK DWR 923
    Autoremote on Tablet is listening on port 1817
 

This message says "I don't know how to get there."

At first look, I'd say u are committing a common error many do, ur double-NATing.

U doing DHCP all around correct? No bad mask on statics?
 

which_doctor

Reputable
Aug 31, 2015
52
0
4,640


@The Paladin
@jsmithepa


Router is a 4G router so maybe there is double NATting going on.

Router config:
Subnet Mask: 255.255.255.0
DHCP Pool: 100 ~ 109

4G modem config (same device as the router):
Subnet Mask: 255.255.255.240

PC config:
IPv4 Address. . . . . . . . . . . : 192.168.0.104
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

I actually have two android tablets. one on .102 and one on .111. The 111 can be pinged occasionally, the 102 very seldomly.

I have confirmed that Tablet1 is .111 and Tablet2 is .102. The subnet mask on both tablets is indeed /24, and the gateway on both is set to 192.168.0.1.

Being that 111 is more than 109 it's weird that I was even able to assign the .111 IP to a device (?). Anyway I changed the DHCP pool span to 100-129 now, so we'll see how that goes.