Windows 10: How to allow Pings (ICMP Echo requests) through Windows Firewall

​

By default, the Windows Firewall with Advanced Security blocks ICMP Echo Requests (Pings) from the network. In this post, we will show you how to allow Pings (ICMP Echo requests) through your Windows Firewall using Command Prompt or via the Windows Firewall with Advanced Security UI. Should I enable ICMP? For many network administrators, they […]

This article How to allow Pings (ICMP Echo requests) through Windows Firewall first appeared on TheWindowsClub.com.

read more...

 

Windows 10 > Fire Wall > Traffic Rules >Block ICMP (Ping) In/Out

I vpn to a unix machine and ping my IP and

10:11pm {~} =>ping 74.125.165.431

PING 74.125.165.431 (74.125.165.431) 56(84) bytes of data

64 bytes from 74.125.165.431 icmp_seq=1 ttl=49 time=41.8 ms

64 bytes from 74.125.165.431 icmp_seq=1 ttl=49 time=36.8 ms

64 bytes from 74.125.165.431 icmp_seq=1 ttl=49 time=39.2 ms

64 bytes from 74.125.165.431 icmp_seq=1 ttl=49 time=41.2 ms

.......<Ctrl> C

Your system REPLIED to our Ping (ICMP Echo) requests, making it visible on the Internet. Most personal firewalls can be configured to block, drop, and ignore such ping requests in order to better hide
systems from hackers. This is highly recommended since "Ping" is among the oldest and most common methods used to locate systems prior to further exploitation.

How do I block the ICMP requests with the Windows 10 Firewall? I am using Norton Security and have traffic rules set to Block all ICMP (Ping); Direction: In/Out, Computer: Any, Communications: Specific, Protocol: ICMP

I went through a chat session with Norton Security and they tried to get the block working, but in the end they could not get it to block the ping requests and they suggested the problem was with my ISP (Time Warner Cable) and I should contact them to resolve
problem.

 

Strange behavior Windows 10 firewall

It could be MTU/MSS negotiation, for some odd reason by default the windows firewall doesnt allow the necessary ICMP packets through.

You need to allow the following in and out on windows firewall.

ICMPv6
Destination Unreachable
Packet too big
Time exceeded
Parameter problem
Echo request
Type 129

Not all of those are absolutely necessary but a good idea to make diagnosing problems easier.

ICMPv4
Packet too big
Destination Unreachable
Echo request
Time exceeded
Paramater problem

What I think is happening the ICMP packets are failing, then its falling back to TCP based negotiation so things still work but are delayed.

If you want it quick and simple just allow ICMP fully in/out, you still probably wont notice any ill affects of that.

 

Tracert or ping not working, general failure

Hi, seems the URLs in my previous post were somehow combined so clicking on this one didn't work:
traceroute - What could cause a ping to fail if I am able to load the sites homepage in a browser? - Stack Overflow
- I've modifed that post (cutting and pasting the text worked).

E.g.

- so browsing might work, but not ping- different protocol. That should give you a direction for investigation.