IPSEC VPN Works in NAT'ed enviroment, not inPAT'ed
We have a 3000 VPN concentrator that we
use to connect remote users to our internal network. It works fine when users originate the connection from behind a device that does NAT. If the users are behind a PAT device they can connect to us (using the Cisco VPN client) and I can
see the TX and RX counters increase on our side but on the client side they typically see the TX counter increment but not the RX counter. On the Concentrator I enabled "IPSEC over NAT-T" and then none could connect. Any ideas?
Re: IPSEC VPN Works in NAT'ed enviroment, not inPAT'ed
If IPSec over NAT-T is enabled on the VPN Concentrator, then the VPN Concentrator/VPN Client uses NAT-T mode of UDP encapsulation. NAT-T works by auto-detecting any NAT device between the VPN Client and VPN Concentrator during IKE negotiation. You must ensure that UDP port 4500 is not blocked between the VPN Concentrator/VPN Client for NAT-T to work. Also, if you are using a previous IPSec/UDP configuration that is already using that port, you must reconfigure that earlier IPSec/UDP configuration to use a different UDP port. Since NAT-T is an IETF draft, it helps when using multivendor devices if the other vendor implements this standard.
NAT-T works with both VPN Client connections and LAN-to-LAN connections unlike IPSec over UDP/TCP. Also, Cisco IOSÂ® routers and the PIX firewall devices support NAT-T.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...