Quantcast
Channel: Exchange Server 2013 - Mail Flow and Secure Messaging forum
Viewing all articles
Browse latest Browse all 1480

Exchange Server error: Client host rejected: cannot find your reverse hostname [Public IP]

$
0
0

Hello folks,

We moved our datacenter over the weekend and our public IPs.  We have a destination NAT rule that translates our assigned public IP for mail to (for example) 96.68.102.139 to our internal Exchange server IP.

However, when our server initiates communication, it is seen on the internet as coming from our firewall IP: 96.68.102.140.

Our MX record matches the .139, but our TXT (SPF) record is set to .140.  Like I said the source IP from exchange initating to the internet is .140.

Do we need a source NAT rule for exchange to match its .139 assignment and also our TXT record?

Thanks


Viewing all articles
Browse latest Browse all 1480

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>