I have a 5505 with the base license. I have a dmz and an internal network. I chose to have the internal network to be blocked from initiating connections to the dmz. I only need dmz machines to initiate connections to the internal network. I can ssh from the dmz to the internal network successfully. But I cannot initiate any other tcp traffic from the dmz to the internal net. After reading various documents, it is my understanding that I should be able to have the dmz (as I've set it up) to initiate any connection to the internal net but not the other way around. I am new with the 5505 - if you need me the post the config, can you please explain how?
thanks for looking at the config. I made the change as you suggested and I still had the same problem. Looking further into it I discovered that iptables on the target host was turned on and blocking all non ssh acess. (This is a new server that the hosting company just setup) Turning off the responsible iptables rules on the linux box solved the problem.
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...