I have a client with only a single IP address. SSL port 443 is used for a web server, so Anyconnect SSL is now listening on a different port.
When we changed the port and updated the client profile, the client now thinks there is a captive portal inbetween and requires the user to authenticate first via web. Doing so works fine but is now adding this additional step to the login process.
I don't understand why Anyconnect (knowing from the profile that the VPN client is on another port) is still obviously looking on 443.
Yes, we are already specifying the port in the profile, If you manually type it out with the port extension as you indicated, we still get the message about a captive portal. I'm thinking that evn though we specify the port, Anyconnect is checking the connectivity using the default 443 (which in our case would resolve to a web server with authentication)