I have an issue that I know is simple enough that has to do with NATting. I have pasted below the config that is pertinent to this question.
We have two public IPs from our ISP, one is assigned to the Outside interface while the second one we want to be forwarded (port 5721) to an internal server.
If I point the default gateway to this firewall everything works great with the config listed below. I however want to point the server to our core as we have several internal networks that need to access this server.
Every time I attempt to do this though it fails miserably. I can no longer ping the external IP of .147.
I almost think that my NAT is simply configured wrong and the only reason it works when the server is pointing directly to the firewall is because it's using the default PAT configured and not the Static NAT I created.
One other thing,
When I attempt to create an access group Inside_access_in in interface Inside all my tunnels fail because the implicit rule to permit all traffic to less secure networks is replaced.....
At this point I am just grasping at straws here....
ip address 64.xxx.xxx.146 255.255.255.240
object-group service DM_INLINE_SERVICE_1
service-object icmp echo-reply
service-object icmp echo
object-group service Kaseya_External_Management tcp-udp
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...