Tip of the Week: How to enable ping on Windows Server 2012

Blog Post created by ken_foster on May 16, 2015

Now that Xpedition flow is supported on Windows Server 2012 you may be considering that platform for your Remote Server Configuration Manager and/or xPCB Team Server host. If so, be aware of a new system default setting in Server 2012 that prevents the system from responding to a ‘ping’ from a remote computer. Not being able to ping the server it makes troubleshooting a bit more difficult if you have problems connecting to it.


You should verify your IT policy first, and then if you determine that the default setting is more security than you need and your IT policy allows you to enable a ping response, you could use one of the methods below to enable it.


The first thing you need to know is that this policy is enforced through a firewall rule, and to change the behavior you’ll need to modify the rule. Of course if you plan on completely disabling the Windows firewall anyway, then you’re already done.  Once you turn the firewall off there is no need to do any of the steps below.


Method 1: Windows Power Shell


If you have Windows Power Shell installed you can enable the rule from the shell window with the following commands:


PS C:\> Import-Module NetSecurity

PS C:\> Set-NetFirewallRule -DisplayName “File and Printer Sharing (Echo Request – ICMPv4-In)” -enabled True


Note: To use this method the rule must already exist. If you need IPv6 ping, then you must also enable the rule called ‘Echo Request – ICMPv6-In’.


Method 2: Graphical Interface


To use the graphical interface to change the rules follow these steps:

  1. Open the Control Panel and select System and Security
  2. Select Windows Firewall
  3. Select Advanced Settings
  4. Under Windows Firewall with Advanced Security, select Inbound Rules
  5. Locate the rule called File and Printer Sharing (Echo Request – ICMPv4-In)
  6. Right click on the rule and select Enable Rule
  7. Verify that a green check mark appears next to it when you look at the Inbound Rules


Done! There is no need to reboot the system. It should respond to a ping from a remote system now.  This works for Windows Server 2012 and Windows Server 2012R2.

Note: If you need IPv6 ping, you can use the same procedure to enable that rule.