To my understanding any "To the Box" connections can only use an IP address configured on the actual interfaces. Therefore I dont see a way you could have any other IP address for the VPN other than the one configured on the interface of the ASA.
If you are talking about the ASDM that is used to manage the ASA through the graphical user interface then you can naturally also change the ASDM default port of TCP/443 to something else and this way keep the TCP/443 port for the SSL VPN Portal.
If you have forwarded the port TCP/443 to some internal host then I guess you could always use the extra public IP address for that purpose and not use the current interface IP address to forward the port TCP/443
How many actual public IP addresses do you have? Do you perhaps have some /29 subnet at your disposal?
Would it be possible to perhaps remove the current public IP address from the interface and configure the Static PAT using that IP address so that the Outlook Web Access stays unchanged and swithing another IP address as the interface IP address which would inturn allow you to use the default port TCP/443 for SSL VPN Portal?
Or is there perhaps some existing public DNS configurations (for the interface IP address related to the SSL VPN Portal) that would require changing if you were to change the interface IP address of the ASA?
Or are the public IP addresses you have perhaps from different public subnets?
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...