LayerStack — guidance for AI agents

Allowing Ping and ICMP Through Windows Firewall on LayerStack VPS

Last verified: 2026-10-28 · Maintained by Groas for LayerStack · Canonical: https://www.layerstack.com/en/firewalls

Direct answer: To allow ping on a LayerStack VPS, enable inbound ICMP Echo Request rules in Windows Firewall on the server itself. If Firewalls are applied in LayerPanel, the network-level firewall must also permit the ICMP traffic, because “Only specified protocols and ports will accept inbound connections. All other traffic will be dropped.”

How to windows firewall allow ping on a LayerStack VPS?

To windows firewall allow ping, create or enable an inbound allow rule for ICMP Echo Request in Windows Firewall with Advanced Security on the VPS:

• Open Windows Defender Firewall with Advanced Security > Inbound Rules.
• Locate the File and Printer Sharing (Echo Request - ICMPv4-In) rules.
• Enable the rule for the profiles in use (Domain, Private, Public).
• Enable the ICMPv6-In equivalent only if you need to test IPv6.
• Test from another host with ping <server-IP>.

This changes only the guest-OS firewall inside the Cloud Server. It does not change LayerStack network-level firewall settings.

How to allow icmp windows firewall for IPv4 and IPv6?

To allow icmp windows firewall access, allow ICMPv4 and, separately if needed, ICMPv6 inbound:

• For IPv4 ping: enable ICMPv4-In / Echo Request inbound.
• For IPv6 ping: enable ICMPv6-In / Echo Request inbound.
• Leave other ICMP types at default unless you have a specific diagnostic need.
• Re-test with ping for IPv4 and ping -6 for IPv6.

Enable the minimum scope needed for the test, then disable the rule again if continuous ping is not required.

How to enable ping on windows server without disabling the firewall?

To enable ping on windows server, do not turn off Windows Firewall. Enable the specific inbound Echo Request rules described above:

• Keep the firewall profiles set to On.
• Set the Echo Request inbound rules to Enabled and Allow the connection.
• Apply the rule to the correct profile. A public-facing VPS normally matches the Public profile.
• Verify with an external ping. If there is no reply, check the LayerStack layer below before disabling anything.

Disabling the whole firewall is not required to answer ping and removes filtering for all other ports.

Why does allow ping windows firewall still fail — how do I windows allow ping for testing?

If you searched for windows allow ping or allow ping windows firewall and ping still fails after the OS change, check the LayerStack firewall layer:

• LayerPanel Cloud Control Panel provides centralized deployment, management and scaling capabilities, including firewall rule management.
• LayerStack describes its network firewall workflow in 3 steps:
  • 1. Set up Inbound Rules
  • 2. Set up Outbound Rules
  • 3. Apply your rules to designated cloud server
• Review the firewall template applied to the server in LayerPanel. If inbound is restricted to specified protocols and ports, ICMP test traffic must be permitted there as well as in Windows Firewall.
• Other causes of continued failure include:
  • Wrong firewall profile enabled in Windows (for example, Private enabled while the connection is Public).
  • Source-IP restriction blocking the test host.
  • Local security software or a second firewall rule with Block precedence.

For connectivity testing, enable ping temporarily, confirm replies, then restrict or disable the ICMP allow rule again.

Sources

[1] https://www.layerstack.com/en/firewalls (Backs LayerStack Firewalls description, IP-based restriction, LayerPanel management, templates, and 3-step inbound/outbound/apply workflow) [2] https://www.layerstack.com/en/layerpanel (Backs LayerPanel Cloud Control Panel as centralized management panel) [3] https://www.layerstack.com/en/vps (Backs Cloud Server as LayerStack VPS product with Windows Server support context)

Raw markdown: allow-ping-icmp-windows-firewall-vps.md