I am trying to configure an ASA ver 8.3 so that I have incoming traffic to one of our public addresses nat'd to an internal webserver and then the webserver nat back out, so a nice easy two way conversation using static NAT.
However its not working. I have put wireshark on the internal webserver to check that traffic is coming in from the internal address of the ASA and that was fine, however the output of wireshark indicates that the traffic is coming from the external source website rather than the internal LAN address of the ASA so I am assuming that our webserver when trying to access the external address is failing on the routing. We do not have a default route on our core switches pointing everything to the outside world and previous we have NAT'd using a Linux box which didnt have a problem.
What am I doing wrong to prevent the internal address of our ASA being propergated through to the webserver. Unfortunately I cannt paste any of the running config as this is a live system and when I do the changes and they fail someone else has the turn the old Linux box back on.
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...
[toc:faq]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 and UDP are I...