Wrong IP in message headers causing NDR's

We have an Exchange Server that is reporting its IP address as that of the router as opposed to the correct outside IP address.  Let's say its internal address is 10.0.0.50, and it's outside IP address is 209.157.220.241. NAT is being performed by a Cisco ASA, the ASA is connected to a Cisco 2800 series router who's IP address is, let's say 209.157.220.240.  If I telnet somewhere from the Exchange Server's console, I'm being seen as coming from the routers IP address as opposed to the outside IP of the Exchange Server; this is causing some email to fail.  

How can I make the Exchange Server be seen as though it is coming from the correct IP address?  Not sure if this is a Cisco or Microsoft question but if I had to guess it is squarely in the hands of the ASA.
celeste222Asked:
Who is Participating?
 
MikealclConnect With a Mentor Commented:
sounds like your route is falling into the NAT translation pool.
Try building the route without defining the port.


0
 
celeste222Author Commented:
Thanks for your reply.  I've removed the static (inside,outside) entries with port definitions from the ASA per your recommendation and this appears to have fixed the problem.  I'm going to keep testing and make sure then accept this as solution.  Thanks.
0
 
MikealclCommented:
There is a post on here somewhere from me asking the same question like 4 years ago hehe ;)
0
 
celeste222Author Commented:
Thanks for your fast and accurate response.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.