up vote 0 down vote favorite
share [g+] share [fb]

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 192.168.0.9 65.121.x.x

Any ideas?

link|improve this question
78% accept rate
3  
You're sure your Exchange server is sending e-mail from 192.168.0.9? 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
feedback

1 Answer

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?

link|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
feedback

Your Answer

 
or
required, but never shown
discard

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