I ran into a situation where one interface on an ASA was linked to another partners router via a public IP in order to service a web portal application. The LAN side interface of the ASA is connected to a private address space, and the entire address space was static natted to the one public interface IP connected to the partner network. This is how it was set up. I assume there was a reason to do it this way, and not PAT the public interface as is most times the case.
In other words 192.168.0.0 /16 ---->>>Static NAT--->>2.2.2.2(ASA-public) ----->2.2.2.1(next-hop router) ---->>>routed to----->>>3.3.3.3 (portal app)
Is it safe to assume that only one private IP connection at a time would be able to access the portal? Because I attempted connections from 2 machines on the private side, and was able to access to portal login page. Also ran simultaneous continues pings to the portal IP..... and no issues. It was translating both. I had always assumed this would not work, and you would need to PAT for this. ......????
Any clarification or sharing of similar experiences is appreciated ..... Dennis
