the database has a odbc server on port 1603 and i have an access-list that allows access on this port from outside. when i try to access from microsoft access through the odbc driver the server from a ip outside of our network i can't. after i enabled debug on pix and retry i see that the client (from outside) connects to the server, the pix builds the translation and the server is accessed on port 1603, but after that i see that the server is trying to connect from source port 139 to a random port BUT on the public ip (which is mapped by the pix and translated) and the same thing is with port 135. the firewall looks at this packets and takes an action (depinding by the access-list because I was trying with many).
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...