Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Alright, so we have an external IP block for our mail server and a few other machines, and we have a WAN interface ip.

Previously, our mail server traffic would be routed out of its own IP address to the internet. All of a sudden, our mail server traffic is instead being routed out of our WAN ip which has no reverse DNS. This is causing me major headaches getting mail through to AOL, Comcast, and a few other domains. I haven't altered the configuration of our cisco 2811 router/firewall in months and I'm not sure what would be causing this change. The nat statement for our mail server is such:

ip nat inside source static 65.121.x.x

Any ideas?

share|improve this question
You're sure your Exchange server is sending e-mail from You can check the bindings in the Exchange System Admin, under the server, find protocols, SMTP and check it's properties. – Chris S Jul 14 '10 at 18:15
up vote 0 down vote accepted

Never would the source IP appear as the internal from outside the network. Did the mail server NAT through a different external IP than it is now using?

share|improve this answer
Some yoyo appears to have un-teamed my two nics, one of them grabbed a different internal IP via dhcp and it chose to use that one to communicate. Re-teamed the cards and told exchange to always use its .9 internal address. – wooz Jul 16 '10 at 12:56

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.