You are absolutely correct. NAT-T is not a concept that pertains to WebVPN. I believe that the statement is worded poorly and should be interpreted as follows:
"When using WebVPN on the same box where NAT-T is employed, do not set the NAT-T port to 443...."
If you are using 443 for NAT-T with your IPSec client connections, this will affect your WebVPN sessions.
I wasn't able to open the link you sent but found the same reference in the 4.7.2 release notes. Appears that this was listed under the "WebVPN Considerations" section. And potential interference with IPSec/NAT-T users is certainly a viable consideration.
Thanks for the insight, but how about the fact that NAT-T occurs over a fixed port (UDP 4500)? I see no place to change it on a VPN Concentrator or even a PIX. Maybe they meant the "proprietary" IPsec over UDP when mentioning NAT-T?
BTW, sorry for the broken url. Here it is for the record:
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...