My community is a straightforward subnet of 10.158.54.0/24 (or 255.255.255.Zero subnet masks). The first router is at 10.158.54.1, and the DHCP/DNS server is at 10.158.54.3. My Home windows system is configured to get its addresses via DHCP, and in reality it’s equipped 10.158.54.6, and the gateway and DNS data are correctly set.
Some servers, although, are “not reachable” by the PC and I can not determine why. These programs have the identical data returned by DHCP (besides IP deal with varies, after all) : the subnet, gateway, dns all are applicable. For instance, I’ve an issue with 10.158.54.23 in the intervening time.
From 10.158.54.23, if I ping 10.158.54.6, the ping responses are dependable and quick.
root@rpi-gw:/root> ping 10.158.54.6 PING 10.158.54.6 (10.158.54.6) 56(84) bytes of information. 64 bytes from 10.158.54.6: icmp_seq=1 ttl=128 time=0.245 ms 64 bytes from 10.158.54.6: icmp_seq=2 ttl=128 time=0.321 ms
If I ping 10.158.54.23 from 10.158.54.23, I obtain:
C:WINDOWSsystem32>ping 10.158.54.23 Pinging 10.158.54.23 with 32 bytes of information: Reply from 10.158.54.6: Vacation spot host unreachable. Reply from 10.158.54.6: Vacation spot host unreachable. Reply from 10.158.54.6: Vacation spot host unreachable. Reply from 10.158.54.6: Vacation spot host unreachable. Ping statistics for 10.158.54.23: Packets: Despatched = 4, Obtained = 4, Misplaced = 0 (0% loss),
Analysis reveals me that that is truly a deceptive Windoze message; it is simply saying that the server’s data isn’t discovered within the arp cache.
arp -a confirms, exhibiting some updates, however .23 (amongst others) is noteably lacking:
C:WINDOWSsystem32>arp -a Interface: 10.158.54.6 --- 0x1a Web Tackle Bodily Tackle Kind 10.158.54.1 c0-c5-22-f6-7c-e6 dynamic 10.158.54.3 dc-a6-32-47-16-c2 dynamic 10.158.54.5 10-60-4b-92-7b-3c dynamic 10.158.54.10 ac-1f-6b-17-f6-25 dynamic 10.158.54.124 fc-f8-ae-71-4a-b7 dynamic 10.158.54.126 ec-5c-68-79-ba-9a dynamic 10.158.54.162 88-de-a9-13-97-68 dynamic 10.158.54.255 ff-ff-ff-ff-ff-ff static 188.8.131.52 01-00-5e-00-00-02 static 184.108.40.206 01-00-5e-00-00-16 static 220.127.116.11 01-00-5e-00-00-fb static 18.104.22.168 01-00-5e-00-00-fc static 22.214.171.124 01-00-5e-7f-ff-fa static 255.255.255.255 ff-ff-ff-ff-ff-ff static
Any concepts why this is perhaps?
BTW: The DHCP data that units these servers’ IP deal with, subnet, gateway, DNS data is all set by a DNSMASQ server at .3. I believe that rounds out all of the vital stuff about this situation.
Thanks for any help.