All Topics » Pulse Desktop Clients



Issue: "Staus: Failed Details: Account has been disabled"


hovalle
Contributor (0)
May 16, 2016 8:55pm
I have a problem with many of our users getting the message above. We are using LDAP to authorize our users to connect. When we check their accounts in AD, the users are not locked or have any warning messages. What we do to "fix" it is to update something in their accounts and it works. I'm not sure why it keeps happening, and if we have something in AD configured that we need to change. We have two MAG's 2600 and only one of them is giving us this problem. The one that we haven't had any problems is running Windows Server 2008.


Details: 5.1 Windows Desktop Clients
MAG-2600
7.4R10 (build 30731)
AD- Windows Server 2012r2





mkbaskaran
Contributor (0)
May 18, 2016 1:53pm
Via TAC

Hi,

FYI ::https://kb.pulsesecure.net/articles/Pulse_Secure_Article/best-practice-recommendation-active-directory-windows-nt-authentication-server-which-authentication-protocol-kerberos-ntlmv2-and-ntlmv1-should-be-enabled-to-avoid-account-lock-out-issues/?q=Staus%3A+Failed+Details%3A+Account+has+been+disabled&l=en_US&fs=Search&pn=1&atype=

Since you have said that, the issue doesn't occur with Win 2008. This might end up as a supportability issue as Win 2012r2 is supported starting from 8.1 release and you can find the same from the supported platform list of 8.1

8.1R1 supported platform list link : https://www.pulsesecure.net/download/techpubs/current/48/pulse-connect-secure/pcs/8.1rx/ps-pcs-sslvpn-8.1r1-supportedplatforms.pdf