ryanmnly
asked on
Microsoft Exchange 2003 Server won't receive e-mails after internal IP change.
We have an Exchange server (running on Windows 2003) that we changed the IP address on and moved to a new subnet. It no longer receives external e-mails. It can send just fine and it has no problem accessing internal resources or the internet. But for whatever reason, it will not receive. We didn't make any changes to the external IP nor the ASA firewall rules. I don't even know where to begin troubleshooting on this one. Can anyone help me?
MidnightOne
Does the ASA firewall allow SMTP traffic only to the old IP address.
What is the MX record shows at ISP did you change that to the new one ??
Also if there is Firewall settings to send mail to server at xyz IP then chnage that too
Also if there is Firewall settings to send mail to server at xyz IP then chnage that too
ASKER
That's what I thought, but the rules weren't changed, only the IP address of that device. So as far as I can tell, the ASA appears correct.
ASKER
The public IP didn't change, only the internal one. So the MX record is the same. There might be something on the Exchange server, but I'm not completely sure where to look. I'll check that right now.
I'm still thinking the ASA was doing port forwarding for port 25 connections to the old IP address.
ASKER
Ok, so I checked out the ASA routing and was able to telnet to port 25 going through the ASA and our router. So it appears that routing is not causing the issue. Is there some sort of setting in Exchange that may dictate who it receives SMTP data from? Also, the firewall is not enabled.
ASKER
Also do you know where I could watch this happen in real-time? Or are there log files? I need to narrow this down in a methodical way. If I can see whether it is even hitting the server or not, then I could get a much better idea of whether it is network related or not.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just an added thought.
In addition to pointing the clients to the right IP, make sure the HOST A record is registered in DNS.
In addition to pointing the clients to the right IP, make sure the HOST A record is registered in DNS.