I am trying to set up a PIX501 so that an outside W2K mobile user can IPSEC/L2TP into the "inside". I'm using PSK.
It works perfectly without a NAT box in between, but when I have to cross NAT (using NAT-T), phase 2 negotiation fails. I have enabled NAT-T in the PIX and it is always enabled in MS. I also don't think that this is a port blocking or compatible policy issue.
I've found the most likely reason. During phase 2 negotiation, the Microsoft client adds a payload "ID_FQDN" which the PIX rejects ("unknown src id_type 2"). MS client keeps retrying but PIX keeps rejecting.
MS client does not send this when NAT-T is not required. It only sends it when a NAT device is detected in the path (through the NAT-D exchange).
This seems like a simple incompatibility between MS's interpretation of NAT-T RFCs and Cisco's.
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...