2. The Cable router is receiving an address from the ISP and performing NAT.
3. The Company router and PIX have external addresses.
4. The internal network is 192.168.1.x.
5. The PIX is performing NAT and PAT.
The problem is as follows:
I can connect the 4.0 VPN client to the PIX/VPN and authenticate and establish the tunnel. However, I am unable to access any resources. I am pretty sure that this problem arises because the client machine is looking locally for the address of our Exchange(i.e.192.168.1.14) server rather than going across the VPN.
If I change the Client side address to 192.168.2.x, I am able to connect to all resources.
Will using the "isakmp nat-traversal" command solve this problem? Changing the settings at home is no problem. However, on the road, most hotels, i.e Marriott, use private address of 192.168.1.x and this causes a lot of problems.
During NAT-T negotiations, both the IPSec peers negotiate the UDP ports and also determine if they are behind a NAT/PAT device. NAT-T autodetects any NAT devices, and only encapsulates IPSec traffic when necessary. This feature is used to addresses the known incompatibilities between NAT and IPSec. Using this should help in your case.
Unfortunately, this does not seem to be the answer.
I have checked the Transparent Tunneling box for "IPSec over UDP NAT/PAT" on the client's Transport Tab. This did not work either. I do not want to involve my consultants or Cisco, if I don't have to. Any ideas?
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...