Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello!
I am setting up a ASA in a new environment - well actually building out a new Datacenter for us to store our servers and equipment in.
So far I have been running into issues and have been able to resolve (like setting up a NAT for internet tr...
I apologize for delay - sometimes its a challenge to get away from the office to go onsite to test.
So I followed your instructions, removed all the NATs... I created a PAT for inside-subnet and Voice-network. I verified both subnets can ping to the...
I updated the ticket on Friday with the latest news but here is the updated show nat:
Keep in mind the DM_INLINE_NETWORK objects are the VPN site's created thru the Wizard. Here is the notes from the latest issues:
1) On the my office side of the VP...
Anyone else chime in?
On the my office side of the VPN (192.168.4.x), I cannot ping anything in the voice network (10.80.x).
However when I was onsite yesterday, from the 10.80.X network, I can ping to 192.168.4.x and get a reply.
Second, Onsite fr...
I made a little progress based on reading something else -
Essentially I created a Static nat for Voice to Inside - Original source, Original destination and it created the reverse nat for inside to voice - original source, original destination. Thi...
I assume the DM_INLINE_NETWORK was created that way via the VPN Site-to-Site Wizard. I wouldn't have named them that but that must be the way the ASA decided to call them. If I go to the NAT Rules Screen, those are basically what those are but no pla...
