This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSL VPN single mistyped password causes AD lockout

We have SSL VPN connected to our Active Directory domain controllers.  We found that after configuring the VPN our users were routinely locking out their AD accounts.  This is happening after a single mistype of a password on the SSL VPN.  I have researched the issue and other posts seem to indicate that having multiple domain controllers configured in "Authentication > Servers" is the cause.  Possibly that a single mistype of a password tries to authenticate against DC1, then after failure it moves to DC2, 3, and so on until it gets to lockout threshold or gets a correct password. 

Is this really what is happening? If so, is there anything I can do to make it so that this doesn't happen?  Shouldn't an incorrect password come back and not try to move on to the next domain controller?  Does this happen to anyone else and if so what did you do to remedy it?



This thread was automatically locked due to age.
Parents
  • XG tries always multiple AD Server, if there are different Domain per AD Server selected. 

    For example AD Server1: .local  AD Server : .com 
    So XG will try to map your user against .local and .com. This causes two authentication requests against the AD forest, in your case. 

Reply
  • XG tries always multiple AD Server, if there are different Domain per AD Server selected. 

    For example AD Server1: .local  AD Server : .com 
    So XG will try to map your user against .local and .com. This causes two authentication requests against the AD forest, in your case. 

Children