<div>
I tried that, but the Exchange server did not have any internet access. I did not include the dns re-write and I did not clear xlate. I will try again and let you know.<br />
<br />
Thanks.
</div>


I tried that, but the Exchange server did not have any internet access. I did not include the dns re-write and I did not clear xlate. I will try again and let you know.

Thanks.

<div>
ya, you need to do a clear xlate or the translations can still be wrong causing unexpected behavior.
</div>


ya, you need to do a clear xlate or the translations can still be wrong causing unexpected behavior.

<div>
I realized that I also couldn't map the entire inner and outer becasue there was another pat for that IP. We will move to another public IP in their pool and test. Thanks again.
</div>


I realized that I also couldn't map the entire inner and outer becasue there was another pat for that IP. We will move to another public IP in their pool and test. Thanks again.

<div>
Thanks again for your help.
</div>


<div>
<div class="content wysiwyg-content">
I have a client with an ASA 5510 and a pool of public IP numbers. His MX record points to an IP (155) that is not the static IP for the outside interface on the ASA (153). He has static nat configured for https and smtp on the IP (155) for Exchange. There is a dynamic nat for all outgoing traffic to use the interface IP. Some emails are being rejected since the reverse lookup does not match the MX record. Is it possible to configure nat so that outgoing traffic for the exchange server is a static IP (155) instead of the interface IP (153)?<br />
<br />
Thanks.
</div>
</div>


I have a client with an ASA 5510 and a pool of public IP numbers. His MX record points to an IP (155) that is not the static IP for the outside interface on the ASA (153). He has static nat configured for https and smtp on the IP (155) for Exchange. There is a dynamic nat for all outgoing traffic to use the interface IP. Some emails are being rejected since the reverse lookup does not match the MX record. Is it possible to configure nat so that outgoing traffic for the exchange server is a static IP (155) instead of the interface IP (153)?

Thanks.

Alternative NAT for host behind ASA 5510

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.