Suddenly (for what appears to be no reason, at least as far as the Windows Server team in our satellite office can tell me), VPN users are no longer able to log into the clientless vpn portal (only used for installation of the anyconnect client).
The ASA is authing to a local RADIUS (Windows 2012 R2 NPS) server, and every login is showing as an Audit Success in the Security log of Event Viewer. I've double and triple checked both the ASA and the NPS config, neither seem to be at fault, indeed it's the same (bar IPs) as the config in a sister satellite office which is operating fine.
Users are attempting to log into the portal (to install the client) and are either receiving "Login Failed", or are just simply being returned to the login screen, with no error message at all. For each of these events there is a corresponding Audit Success on the NPS server.
It gets even stranger when I realised that logging into the Anyconnect Client software works fine, using the same credentials. The problem is localised to the Clientless VPN portal page on the ASA itself.
Halp!
The ASA is authing to a local RADIUS (Windows 2012 R2 NPS) server, and every login is showing as an Audit Success in the Security log of Event Viewer. I've double and triple checked both the ASA and the NPS config, neither seem to be at fault, indeed it's the same (bar IPs) as the config in a sister satellite office which is operating fine.
Users are attempting to log into the portal (to install the client) and are either receiving "Login Failed", or are just simply being returned to the login screen, with no error message at all. For each of these events there is a corresponding Audit Success on the NPS server.
It gets even stranger when I realised that logging into the Anyconnect Client software works fine, using the same credentials. The problem is localised to the Clientless VPN portal page on the ASA itself.
Halp!
