The purpose of this article is to provide initial troubleshooting steps when a health check is failing.
The first thing we want to do when we have a failing health check is try to force a health check manually while capturing traffic in a packet capture so that we can see what happened during the connection attempt. This can be done as follows:
For an Authentication realm health check: "port 53 or port 88 or port 389"
For an ICAP or Forwarding host health check: "host 22.214.171.124" (126.96.36.199 being the ICAP or forwarding server's IP)
For DRTR health checks: "host webpulse.es.bluecoat.com"
For DNS Server health check: 'port 53' (by default it tries to resolve IP address for www.bluecoat.com but this can be changed in health check configuration)
-Go to Maintenance > Service Information > Send Information > Send Service Information tab
-Enter the case number
-Check the Packet Capture, Sysinfo and Event Log before clicking Send.