asked on

Mapping a public IP and ports to inside address

I have what I think is a simple setup and problem. I have many internal servers, two of them are Lync and Exchange with private IP addresses on them. How does one setup the ASA (5512) to allow the communication for two things:
1 some internal private IPs use the same hosts - so the ASA fails when you tell it to forward the same ports?
2 with port forwarding how to handling something like Lync that has about 20,000 ports needed to map to its inside?

Currently I have things like OWA working by forwarding port 443 to the correct private IP. Obviously this a busy port and a issue. In some places you can reassign HTTPS to another port but there has got to be a better way.

much appreciate of any help/guidance....

ASKER CERTIFIED SOLUTION

Les Moore

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

EckoForce_1

ASKER

I was hoping there was a better way.....so I cant have overlapping IPs on my ASA via interfaces, subinterfaces or contexts.....so how do I setup all these public IPs (which I do have). Create static routes on the upstream router to point many public addresses to one? My other options is getting a ASA-5505 for each IP - but that seems wasteful.

EckoForce_1

ASKER

thanks for the guidance - I am going to use static NATs - 1 public to 1 private and then allow my ports with ACLs....much easier that trying to port map!