NetScaler: Monitor Proble Failure (SSL)


A classic gotcha in the world of ADC load blancing with SSL, manifests itself in two ways:

  1. LB Servers are added using FQDN. The monitor reponse reports: “domain name not resolved”.
  2. LB Servers are added using IP. The monitor response reports: “Failure -TCP connection successful, but application timed out”.

Domain name not resolved

Failure – TCP connection successful, but application timed out


Simply, turn of (untick) “Enabled Health Monitoring” or “AppFlow Logging”.


3 thoughts on “NetScaler: Monitor Proble Failure (SSL)

  1. woter Post author

    I do apologies if this information is incorrect. I faintly recall a discussion over this on an NS course a while back. Perhaps you may be able to share a more suitable solution. Thanks.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see

This site uses Akismet to reduce spam. Learn how your comment data is processed.