3 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Holger Isenberg commented  ·  May 4, 2011 10:37 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I fell into this user trap just this minute when one of our LDAP service crashed while the host itself was happily responding to ICMP echo requests. Result was: no authentication on webadmin any more as the next entry in the Active Directory Availability Group wasn't tried. Of course you can add every LDAP server and RADIUS server as singular entry now with V8, so that's a sufficient workaround, but you should warn the user in the manual about that trap.

• Matthias Nees commented  ·  May 7, 2009 8:25 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  To check the availability with more complex methodes than an ICMP Ping is very important. For a first step a check of TCP or UDP Port is enough. Later this check could be improved. I need a check of a UDP/1812 RADIUS Port!!

• Elmar Haag commented  ·  May 7, 2009 7:58 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Required feature is: allow to configure the mechanism how to check the availability of the members inside an avalability group network object.
  In v7.4, the check of the available servers is only by using ICMP (ping). This means it is not detected, if an application on these servers has died, but the server itself still responds to the ping requests.
  It would ba fine to have a mechanism (like in the "server load balancing") that allows to detection of unavailable servers not only by ping but by any other protocol.