Static NAT with ISA 2004

Hello Everyone,

I need to do a static NAT for our mailserver. Right now it's going outbound with our general external NAT address, so it's failing on reverse lookups. I need to Static map it so that it goes out with a specific External IP all the time.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Can you explain your problem a little bit further? What reverse lookup you are talking about?
ISA can't Static NAT. Only Publish Rule.

On your mail server you need set up, that SMTP service tell ISA's host name.
Methodman85Author Commented:
Some recipients SPAM filters perform a reverse lookup on the source address that they recieve for our exchange server. So our exchange server ( leaves the network with a general NAT external address (, same as all other hosts on our network that access the internet.
When the end users spam filter does a reverse lookup on, they of course do not find the appropriate record.

Would adding a PRT record that points to our mailserver work? Does it make sense to have a PRT record for a general NAT address?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Methodman85Author Commented:
Hi Leonov,

Can you explain in more detail, or point me to an article, i'm not sure what you mean

There is my case:
1) My firewall xx.xx.xx.xx has FDQN and revers name
2) My Exchange 2007 behind fw has and FDQN

I go "Server Configuration" - "Hub transport" - "Receive coonectors" - "Default" - "Properties"
and set "Specify FDQN for EHLO and HELO" to

When Exchange connects to external SMTP throw NAT it gets xx.xx.xx.xx address, and say "EHLO"

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
you are right, you have to add PTR or rDNS record that is using your external IP address, your external FQDN mail server address (noramlly same as MX record) and you soulh have the same FQDN address in yout SMTP banner. rDNS record normally sets your ISP provider.
Methodman85Author Commented:
The problem is that I can't set the same address as the MX record. The MX record points to .60, but the server goes out at .70 when it's natted. So a reverse PRT needs to point to .70, but that's the general NAT address of every host that leaves the firewall, won't this cause problems?

Leonov: I'm trying to understand what you mean. You're saying that you're getting your exchange server to use your firewalls DNS name and external IP address? So you're tricking the reverse lookup?
MX records are pointed to FQDNs, not to IP addresses. If IP addresses are not the same it will not cause you troubles. To check if anything is configured correctly you can use site - SMTP test option.
The only thing that really needs to be the same is FQDN on rDNS and FQDN on SMTP banner.
No, I change External FDQN for mail server for SMTP purposes.

RDNS must say xx.xx.xx.xx PTR, before all operations starts. When I bought IP address xx.xx.xx.xx I said to ISP that it must resolve to
Keith AlabasterEnterprise ArchitectCommented:
It cannot be done - ISA does not support what you are trying to do.
Traffic will leave ISA with the main ip address set on the ISA external nic. Sorry.

ISA Forefront MVP
Methodman85Author Commented:
Hi Keith,
So if I set a PRT record for that external nic address pointing to the FQDN of my exchange server, should that work on reverse lookups? and would it cause any issues with anything else?
Yes. But if your Exchange use external FDQN in HELO/EHLO commands will be better.
Keith AlabasterEnterprise ArchitectCommented:
Yes - it should but bear in mind that the MX record also needs to be associated with the same fqdn. They all have to tie up.
No it will not cause any conflicts with anything else.
Methodman85Author Commented:
Thanks Everyone, I will give this a try on Saturday.
Since the PRT is the easier fix, I'll try that first, if I'm still getting connection refused errors based on failed reverse lookups, I will try leonov's method.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Anti-Virus Apps

From novice to tech pro — start learning today.