Cisco AnyConnect: Login Denied Default

[FV11422]

I'm looking to get some information regarding this error.

I'm a tech at my organization's service desk who runs into this error far to often, and have to run down a whole slew of possible causes because of the vagueness of this error. I believe the vagueness is due to some one not bothering to program in proper error messages but I looking to confirm this and to know if these errors would be generated via the Client application, the VPN appliance, or a mix of both. I've tried to get this addressed several times, now I would like to at lease tell my boss who he needs to put pressure on to get this resolved.

I'm the top tech here, the one that all the other techs come to for advice but am by no means a VPN or AnyConnect expert so long form in stead of acronyms would be helpful if providing any technical details. Not looking for an A to Z explanation of error trapping but any info would be greatly appreciated.

Thanks in advance.

[mmoulson1]

If you are as you say seeing this error often, what do you do to fix it? Is it all users that are affected or just a single user?

What device are you using to terminate the AnyConnect connections? What code version is it running?

I had a look for "Login Denied Default" as an error but it did not return anything useful. There are other errors like:

"Login Denied. Your environment does not meet the access criteria" and
"Login Denied, unauthorized connection mechanism"

Can you confirm specifically the error you are getting?

In terms of putting pressure on someone to resolve it, do you have Cisco support for the device? If so you could raise a TAC case.

[FV11422]

Hi,

Thanks for your reply.

"Login Denied. Default" is the exact error.

Affect many users

It comes up if the system fails the needed health checks.

- verify apps are running and at a minimum version

- verify antivirus definition files are up to date

- other stuff that I'm leaving out for security

I don't have details on the endpoint, just that its VPN appliance. The endpoint is managed by our vendor.

IT in my organization is siloed into many groups who guard their turf, and often refuse to accept the problem is on their end for as long as possible and the vendor isn't any better.

In terms of applying pressure I was hopping to find out the problem was definitely in the software package so we could pressure the desktop engineering team, or with the vendor managing the VPN appliance so can lean into them

I understand that the lack of info regarding the appliance, and the apparent uniqueness of the error may make it impossible

to get an an answer.