Answered by:
ICMP Echo (Ping) blocked by Windows Firewall in Vail

Question
-
Hi,
I think it would be more useful if ICMP Echo (Ping) was allowed by default in the firewall settings for Vail. It makes it a lot easier to debug network setups when ping is working on machines.
Cheers,
Al
--Wednesday, April 28, 2010 3:58 PM
Answers
-
Weird. I thought this was the case. I went ahead and filed a bug for you on the product against our networking feature team. But feel free to also file it in Connect, which is the best thing to do if you really want something. I really want this, so I filed the bug. :)Thanks for testing Vail!SeanThis post is "AS IS" and confers no rights."Ken Warren" wrote in message news:35aba050-d7d3-4cc9-aa30-48bb588fb6e4...
This is standard in Windows Server 2008, I believe. You can change it in the firewall GUI or (from memory) you can run this command in an elevated command prompt:
netsh firewall set icmpsetting 8
I'm not on the WHS team, I just post a lot. :)- Marked as answer by Al West Thursday, April 29, 2010 10:12 AM
Thursday, April 29, 2010 3:21 AMModerator
All replies
-
This is standard in Windows Server 2008, I believe. You can change it in the firewall GUI or (from memory) you can run this command in an elevated command prompt:
netsh firewall set icmpsetting 8
I'm not on the WHS team, I just post a lot. :)- Proposed as answer by Jonas Svensson -FST- Wednesday, April 28, 2010 11:43 PM
- Unproposed as answer by Al West Thursday, April 29, 2010 10:12 AM
Wednesday, April 28, 2010 4:07 PMModerator -
Weird. I thought this was the case. I went ahead and filed a bug for you on the product against our networking feature team. But feel free to also file it in Connect, which is the best thing to do if you really want something. I really want this, so I filed the bug. :)Thanks for testing Vail!SeanThis post is "AS IS" and confers no rights."Ken Warren" wrote in message news:35aba050-d7d3-4cc9-aa30-48bb588fb6e4...
This is standard in Windows Server 2008, I believe. You can change it in the firewall GUI or (from memory) you can run this command in an elevated command prompt:
netsh firewall set icmpsetting 8
I'm not on the WHS team, I just post a lot. :)- Marked as answer by Al West Thursday, April 29, 2010 10:12 AM
Thursday, April 29, 2010 3:21 AMModerator -
Actually, after a little more digging, in theory PING for both IPv4 and IPv6 is already allowed on the local subnet, Sean (and Al). It's required for File and Printer Sharing.
I no longer have a clean Vail server for testing this further, and won't be reinstalling on my test/produciton Vail server until I get more storage sometime next week, but can someone who hasn't made any firewall changes please take a look and see what the rules for ICMPv4 and ICMPv6 look like, and see if ping -<servername> -4 and ping <servername> -6 return a response? I'm also asking some other folks (Windows Home Server MVPs) to test...
I'm not on the WHS team, I just post a lot. :)Thursday, April 29, 2010 2:09 PMModerator -
Mine pings fine with both
GreyThursday, April 29, 2010 3:43 PMModerator -
Al, at what point were you pinging your server? Had you completed setup yet? Shares visible on the network? There is a rule which is required for file and printer sharing to work which permits ICMP echo requests; I don't believe it's turned on until you complete setup and shares are visible.
I'm not on the WHS team, I just post a lot. :)Thursday, April 29, 2010 3:47 PMModerator -
Thanks, Grey. Someone else reported the same.
I'm not on the WHS team, I just post a lot. :)Thursday, April 29, 2010 3:48 PMModerator -
Ken has a good point. I just tested my server here (same one you have for the beta) and it worked just fine.This post is "AS IS" and confers no rights."Ken Warren" wrote in message news:c1b41c32-2a35-40bd-b5f5-b6cb5a75db2a...Al, at what point were you pinging your server? Had you completed setup yet? Shares visible on the network? There is a rule which is required for file and printer sharing to work which permits ICMP echo requests; I don't believe it's turned on until you complete setup and shares are visible.
I'm not on the WHS team, I just post a lot. :)Thursday, April 29, 2010 11:06 PMModerator -
I was pinging from another routed subnet - not the local subnet. Also I had not completed setup, however at this point is maybe where one would like to verify the server is available.
--Saturday, May 1, 2010 9:01 AM