so you want the users on the other lan (vpn users) to be able to connect to resources on the corporate lan (vpn destination)
Seems to me this is not a nat issue, but routing.
If the 2 pixes connect to eachother via the vpn, the routing table is altered so the 2 LAN's can communicate. If no ACL is applied on the inside interface of both pixes, the communication should be fine.
Be sure to use 2 different ip-segments for both LAN's otherwise routing is not possible (the pix will think the segment is local, and will not send it across the vpn)
Set the pix as the default gateway on both lan's and communication between the 2 LAN's should be possible.
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...