A clientless SSLVPN solution is built for 10 employees on a newly installed Cisco ASA. After a couple of days in production, it has been observed that only the first two users to log in each day are able to connect successfully. The remaining users encounter the message "Login failed". Which action resolves this issue?

Question

Accepted Answer

A. Allocate additional Cisco AnyConnect Premium licenses to the ASA. The Cisco ASA base license includes only 2 simultaneous SSL VPN (AnyConnect Premium) sessions by default. Once that licensed session count is exhausted, any additional users receive a login failure. Allocating additional AnyConnect Premium licenses raises the concurrent session ceiling to accommodate the full user base.

Answer

B. Increase the vpn-simultaneous-logins parameter to a value of more than 2. The vpn-simultaneous-logins group policy attribute controls per-user login limits but cannot exceed the platform's licensed SSL VPN session count, so increasing it alone would not resolve the issue.

Answer

C. Increase the number or IP addresses available in the VPN pool. An IP address pool applies to full-tunnel AnyConnect connections that require an assigned IP address, not to clientless SSL VPN sessions which do not consume pool addresses.

Answer

D. Verify that the users that cannot log in are in the correct AD group with VPN permissions. AD group membership issues would cause authentication failures for specific users regardless of login order, not a pattern where only the first two logins each day succeed.

A clientless SSLVPN solution is built for 10 employees on a newly installed Cisco ASA. After a couple of days in production, it has been observed that only the first two users to log in each day are a

Question

Options

How the community answered

Why each option

Topics

Community Discussion