Troubleshooting Tip: Window 10 computer does not reply to ping

[mle2802]

Description	This article describes a possible reason why a ping does not get a response from a Windows machine.
Scope	FortiGate, Windows 10.
Solution	In some cases, a ping gains no response from a Windows machine, even when the Windows machine can reach the Internet or a FortiGate IP as a gateway. This happens when Windows is on a public network. For Windows machines to reply a ping, it should be in private network. To check this option, follow these steps: On the right side of the taskbar, select the network icon. Under the name of the network connected to, select Properties. Under Network profile, select Public or Private. Try to ping again to see if the ping is replied to now. If the issue persists, enable 'File and Printer Sharing (Echo Request – ICMPv4 – In)' and add the subnet where the ping comes from to the 'Remote IP address' section. To change this option, follow these steps: Search for 'Window Defender Firewall' on the Windows machine, select 'Advanced settings' and then 'Inbound rules'. Press the F key until ‘File and Printer Sharing (Echo Request – ICMPv4 – In)’ is found. Select it once, then press Enable Rule in the right sidebar to allow pinging in Windows 10. With the rule enabled, double-click ‘File and Printer Sharing (Echo Request – ICMPv4 – In)’ to open the properties window. Select the ‘Scope’ tab and add the source subnet of the ping under 'Remote IP addresses'. Try to ping again and see if the machine replies: