You decide which services we may enable for analytics, personalization, and external content.
We use cookies and similar technologies on our website to personalize content, embed external media, and better understand how individual areas are used.
Necessary cookies
These entries support essential functions such as security, stability, and form processing.
Optional sections
AnalyticsMarketingPersonalizationExternal media
Your data may be processed with your consent or on the basis of legitimate interests. In the cookie settings, you can reject or explicitly allow each optional category.
Some services process personal data in third countries. By consenting, you also agree to this transfer. You can find more information in our Privacy Policy.
You can reopen and change your selection at any time. · 1.0.2
Learn how to allow ICMPv4 Echo requests in the Windows Firewall so your server is correctly detected by monitoring systems → Find out more now
10 November 20262 min read1 Views0 helpful
Introduction
In some cases, a Windows server may appear as offline in the ZapX panel even though the system itself is running normally. This behavior is usually related to firewall settings that block ICMPv4 Echo requests. These requests are used by the well-known ping command and are standard for monitoring systems to check if a server or IP address is reachable.
If the Windows Firewall blocks ICMP Echo requests, the monitoring system cannot receive a response from the server. As a result, the ZapX panel shows the server or assigned IP addresses as offline, even though the server itself is running without issues.
FAQ
Frequently asked questions
This is usually due to firewall settings blocking ICMPv4 Echo requests (ping). Without a response to these requests, the monitoring system cannot detect the server's availability and mistakenly shows it as offline.
Connect via the Remote Management tab of your Dedicated Server using the HTML5 console, open Windows Defender Firewall with Advanced Security, and create a new inbound rule that allows ICMPv4 Echo requests.
Feedback
Was this article helpful?
Your feedback helps us prioritize and improve content.
0 of 0 Users found this article helpful.
Personal support
Need more help than the guide provides?
Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.
Zappy knows this guide and answers you right in the chat.
Navigation
Dedicated Server
Cause
The most common reason for this problem is a missing rule in the Windows Defender Firewall that allows incoming ICMPv4 Echo requests. Without this rule, the firewall blocks ping requests by default.
Monitoring systems rely on these responses to verify server availability. Therefore, the server may appear offline even though the services on the server continue to run normally.
Solution
To fix the problem, you need to create a firewall rule that allows ICMPv4 Echo requests. First, connect via the Remote Management tab of your Dedicated Server: start a session and log in through the HTML5 console in the remote console.
After logging in, open the Windows Defender Firewall with Advanced Security. Press Windows + R, enter the following command, and confirm with Enter:
Code
wf.msc
The advanced firewall configuration window will open. Select Inbound Rules from the left menu, as the server must accept incoming ICMP requests. On the right, click New Rule to create a new firewall rule.
In the rule wizard, select Custom as the rule type. In the next step, choose ICMPv4 as the protocol type. Then open the Customize settings and enable the option for Echo Request so the server can respond to ping requests.
Continue in the wizard and select Allow the connection as the action. In the profile step, you can usually enable the rule for all profiles so it works regardless of whether the server is on a public, private, or domain network.
Finally, give the rule a meaningful name, e.g., Allow ICMPv4 Echo Requests. After completing the wizard, the new rule immediately allows incoming ICMP Echo requests.
Verification
After creating the rule, you can test if the server responds to ping requests. From another system, run the following command:
Code
ping <YOUR_SERVER_IP>
If the server responds successfully, the monitoring system can detect it again. After a short time, the server status in the panel should change from offline to online.
Conclusion
Congratulations! By creating the ICMPv4 Echo rule in the Windows Firewall, you have successfully ensured that your Windows Dedicated Server responds to ping requests again.
This allows monitoring systems to correctly detect your server's availability and prevents it from being shown as offline in the ZapX panel.
If you have any further questions or need assistance, our support team is available daily to help! 🙂
Server hosting from €2.49 / month, online instantly, DDoS protection included.
Preferred source on Google
