Tracert going to the wrong place
Posted on 2008-11-10
We added a new Exchange email server to our network, and for the time being it is running alongside the old server. Internall I have no problems accessing both, through Outlook or Webmail.
However from the outside I can't seem to get to the new server. I have an ASA5510 which I have set up with the proper ACL and NAT info, (translations for the public IP 71.x.x.202 to internal 192.x.x.250 for ports 110, 25 and 80) but when I try to reach the new server via webmail it does not even seem to be connecting to the ASA, as nothing shows up on the log.
So I ran a tracert for the public IP address of the new server (which has MX and A records set up for the new email server) but for some reason the tracert ends up going to the public IP of the old email server and then stops there.
Any ideas as to why it's going to the old server IP?
The MX info is set up as follows:
10 oldmail.domain.com 71.x.x.205
20 newmail.domain.com 71.x.x.202