Can't ping computer on network, but computer can get out to internet.

[TroyV]

I have a computer directly connected to my Meraki switch. This computer has gotten an IP address from the server and can reach out to the internet but I am unable to use the switch to ping 'its IP address nor can I ping with while on VPN. I can ping other devices from VPN that are in that same VLAN. 

I first had the device static, was able to get out but couldn't ping it. Made sure that the firewall settings allowed for ping on this Windows 10 computer. I then moved it to dynamic and it got a different address but am still unable to ping it. VLAN on port is correct along with port settings that match other locations that this is working at. I have tried opening routes but there is no change. I made some firewall adjustments but there is no change.I had it set to a reserved address in Meraki but it wasn't working so I removed it. Set the subnet mask in the IPv4 settings of the computer to /16 but then the computer was not able to get out to the internet. Restarted all devices. Can ping the device while connected to the same switch as device. I don't believe that this is network related as I am able to ping other devices within that VLAN.

I am unable to think of what else I can do at this point. Any suggestions would be much appreciated.

[alemabrahao · Accepted solution]

Have you tried disabling the Windows firewall? It can be the antivirus blocking.

[TroyV]

No, I can give this a try, thank you.

[TroyV]

Even though the rules were set to allow for the needed traffic to pass, disabling the firewall and antivirus was the key winner here. Thank you all for your responses.

[BlakeRichardson]

@TroyV  I wouldn't disable the firewall just to fix this issue, you need to allow inbound ICMP traffic. Doing that will allow you to ping said device while having it's firewall active. Just make sure you select the correct rule for your network type i.e. private, domain or public

[PhilipDAth]

I back @alemabrahao .  Either Windows firewall, or some third party antivirus software (such as antimalware).

My second guess would be a wrong netmask.  The client VPN and VLAN subnets should not overlap, and (in most cases) should be 255.255.255.0.