ajruiz
asked on
Delay 4.4.7 NDR
We recently started getting NDR Could not deliver the message in the time limit specified 4.4.7 messages from certain domains (ccf.org and eaton.com).
What has changed was we moved our Exchange 2003 Server to a new location, changed the IP/subnet address of our Exchange Server, changed IP address/subnet of WINS/DNS and our firewall remains same.
What has changed was we moved our Exchange 2003 Server to a new location, changed the IP/subnet address of our Exchange Server, changed IP address/subnet of WINS/DNS and our firewall remains same.
flyguybob
Out of curiosity, did you update your PTR record associated with the external IP address of your Exchange server(s). Some anti-spam software is throttling e-mail messages from domains without a PTR to 1 message an hour or 10 messages an hour, etc. This 4.4.7 sometimes appears in this case.
ASKER
Our PTR address remains the same and there was no need to update it.
So the address of the Exchange server changed, but the NAT did not change, correct?
ASKER
Correct.
So your exchange server is now talking to a different DNS server?
ASKER
It is the same DNS server just with a different IP Address.
So just to clarify...you moved the DNS server and the Exchange server to different subnets?
ASKER
Yes. We have two DNS servers, one at the new location and one at the old location.
This seems like a DNS problem to me. Was the Exchange server pointed to both DNS servers before or still just the one? Can you ping ccf.org and eaton.com from your Exchange server's subnet?
ASKER
We block ping from the firewall. I just noticed both mail ip addresses we are having issues with start with 192. We did a tracert and it isn't getting to the default gateway. It appears to be switch related but we can't figure it out.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ours do not start with 192. We are having Cisco look into it also.
Ok, yeah...this is looking less and less like a Windows problem...leaving my realm. hehe
ASKER
Okay, I figured it out. We are on a cluster, initially we configured per a KB article where the private heartbeat was set to 10.10.10.10 which worked fine at our old location. When we moved it to our new location we are using the 10 as the first octet so when it was first brought up e-mail would not go through. We changed it to 192.10.10.10 figuring 192 was reserved. You guessed it, e-mail was trying to go out the private heartbeat for e-mails going to the 192 range.
Aha! Interesting...well I'm glad you got it figured out. Clustering can be problematic at times.
I'm having the same problem but I'm not on a cluster.
We recently changed from one ISP to another with different DNS and IPs.
What check list can I do to go and find out what is wrong with our system?
We recently changed from one ISP to another with different DNS and IPs.
What check list can I do to go and find out what is wrong with our system?