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.
I have a server inside my network that I want users to be able to access from the outside. To this end, I have setup a static nat between my internal address for this server (10.7.64.27) and one of the public ip addresses I have available (public2)....
Here's my setup
3 Networks across 3 switches (3x C3650)
10.7.64.1.x/24 (Vlan 7)
10.10.10.x/24 (Vlan 20)
192.168.1.x/24 (Vlan 15)
The switches are all connected to each other, with Switch one have a connection to an ASA and the outside world. My go...
Well, my appliance can now ping out, which is positive. When I go to Public 2 on port 443, I get a tomcat webserver page. I'm wondering if there is a configuration problem on the appliance side now. I'll have to check with my coworker who set thi...
Sounds like you have it. Public 1 and Public 2 are on the same subnet. So... should be as simple as putting the correct ACL in place in the right location. I'll give that a try and see what happens.
In our ASA, the default route points all traffic to public 1. However, for the appliance inside the network users will be accessing it via public 2. I have created a static nat between the appliance private address and public 2.
You are saying tha...
Our ASA uses 8.25.
The default route in the box points to public1, that is why I feel I need a route to ensure that appliance box I have will send traffic to public2, which is the ip the users would go to to use this appliance.
As to the ACL I can ...
