cancel
Showing results for 
Search instead for 
Did you mean: 

Host checker fails with reason: "" (Thus no reason) !

SOLVED
Ruud_
Contributor

Host checker fails with reason: "" (Thus no reason) !

Hi,

I have now two customers where the host checker policy fails with no reason at all !!!

When I disable the host checker, they can authenticate, but it always fails when I enable it.

I am also 100% sure that they meet the requirements. (Virusscan and firewall)

This is the message I receive in the log: Host Checker policy 'GENERAL' failed on host xxx.xxx.xxx.xxx . Reason: ''.

Some additional information:

- When I remove all rules in the host checker, it still fails ! (how can it fails, if nothing needs to be checked)

- When no host checker is assigned, it works.

This issue is really annoying and need to be solved asap...

Any help is welcome.

Thanks in advance,

Ruud.

Message Edited by Ruud on 12-17-2008 02:38 AM
Message Edited by Ruud on 12-17-2008 02:53 AM
1 ACCEPTED SOLUTION

Accepted Solutions
Ruud_
Contributor

Re: Host checker fails with reason: "" (Thus no reason) !

I found the solution myself troubleshooting this issue.

Seems that this was conflicted by ESAP file version 1.4.3. Because when I did a roll back to 1.4.2 the issue did not occur.

Later I installed version 1.4.4 and there the issue didn't occur either.

View solution in original post

3 REPLIES 3
Ruud_
Contributor

Re: Host checker fails with reason: "" (Thus no reason) !

I found the solution myself troubleshooting this issue.

Seems that this was conflicted by ESAP file version 1.4.3. Because when I did a roll back to 1.4.2 the issue did not occur.

Later I installed version 1.4.4 and there the issue didn't occur either.

kyler_
Not applicable

Re: Host checker fails with reason: "" (Thus no reason) !

Can you tell me what version of the SSL VPN IVE software you are running, we are experiencing the same thing on 6.3R1 even after upgrading to ESAP 1.4.4?
Ruud_
Contributor

Re: Host checker fails with reason: "" (Thus no reason) !

Version: 6.2R1 (build 13255)

Going to ESAP 1.4.4 solved the issue for the two customers who experienced the problem.