We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
Accept
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Campus Barracuda Campus
Barracuda NextGen Firewall X
Overview Documentation Materials

Back to Knowledgebase

Virtual Server IP is not pingable

  • Type: Knowledgebase
  • Date changed: 8 years ago
Solution #00005062
 
Scope:
This solution replies to:
- NG Firewall firmware versions 4.2.x, 5.0.x, 5.2.x
- netfence firmware versions 4.2.x

 
Symptoms:

A defined Virtual Server IP does not respond to ping requests even though the IP address was set to "Reply to ping" = "yes" in the server configuration.


 
Solution:

The specific Virutal Server IP has also been introduced as further network (e.g. when you have activated remote management). In the further network configuration, the IP address has been set to "Reply to ping" = "no".

 

Modify the further network configuration and there set the IP address to "Reply to ping" = "yes".

 

 

Link to This Page:
https://campus.barracuda.com/solution/50160000000IKXfAAO