SMTP Server / Failed Connection Attempt
We're going to move to another ADSL line, which means another IP-address. After changing the DNS for our domain name to the new IP address, we have problems with our mail. We have two domain names (olddomain.com and newdomain.com). Olddomain.com is the domain name of our network. Newdomain.com is the domain name we use for our mail.
We first changed the DNS for mail.olddomain.com and mail.newdomain.com to the new IP address. Then mail failed to come in, and I decided to move them back immediately. First I forgot to move mail.olddomain.com, but even after I did this it still looks like mail is going to ISA2. Doing a traceroute it looks like the DNS for the mail is going to the old IP address. (NB: the DNS for the websites newdomain.com and olddomain.com are going to the new IP-address, and that works okay.)
We have two ISA servers (2004) currently, one at the old IP (ISA1), one at the new (ISA2). The new one has problems with the connection to the Exchange server (2003). What's puzzling me is that the configuration of ISA1 are backed up and then imported in ISA2. But for some reason they don't work. Should this be configured in Exchange? What is the problem here, Exchange or ISA?
We first changed the DNS for mail.olddomain.com and mail.newdomain.com to the new IP address. Then mail failed to come in, and I decided to move them back immediately. First I forgot to move mail.olddomain.com, but even after I did this it still looks like mail is going to ISA2. Doing a traceroute it looks like the DNS for the mail is going to the old IP address. (NB: the DNS for the websites newdomain.com and olddomain.com are going to the new IP-address, and that works okay.)
We have two ISA servers (2004) currently, one at the old IP (ISA1), one at the new (ISA2). The new one has problems with the connection to the Exchange server (2003). What's puzzling me is that the configuration of ISA1 are backed up and then imported in ISA2. But for some reason they don't work. Should this be configured in Exchange? What is the problem here, Exchange or ISA?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What is "long time"? Minutes, hours? You should enable Message Tracking on the Exchange server and search for the messages. That way you can establish if they indeed reach the mail server but is delayed internally.
http://www.computerperformance.co.uk/exchange2003/exchange2003_message_tracking.htm
http://www.computerperformance.co.uk/exchange2003/exchange2003_message_tracking.htm
ASKER
A long time is half an hour or longer for a mail that normally arrives in 20 seconds. I'll take a look at the message tracking.
ASKER
I've turned message tracking on. But the delays are not internal.
I think we located the problem between ISA and Exchange. On the new ISA server, if I ping to the machine name of the Exchange server (MAILSERVER), I get the external IP-address, not the internal one (like 192.168.1.x). This seems to have to do with routing and remote access. On the other hand, if I look at the ISA logging, it mentions 192.168.1.5 as "destination IP" of the Exchange server, not MAILSERVER.
I think we located the problem between ISA and Exchange. On the new ISA server, if I ping to the machine name of the Exchange server (MAILSERVER), I get the external IP-address, not the internal one (like 192.168.1.x). This seems to have to do with routing and remote access. On the other hand, if I look at the ISA logging, it mentions 192.168.1.5 as "destination IP" of the Exchange server, not MAILSERVER.
ASKER
@peakpeak
Can you confirm that what I did was right? I don't mind opening another question about RRAS.
Can you confirm that what I did was right? I don't mind opening another question about RRAS.
ASKER
I'll describe what I did, so you can look if it is done correct. The domain names are hosted by Network Solutions.
1) I added another A record: mail2.newdomain.com, which points to the other address
2) I added a MX record: mail2.newdomain.com, priority 20 (the original MX has priority 10)
This what I see as a result:
newdomain.com
mail.newdomain.com.(10)
mail2.newdomain.com.(20)
One of the domains has a subdomain listed in the MX list. It has priority 10, and it ends with a dot. The same name without ending dot is in the normal domain list.
mail.newdomain.com.
I deleted this (but made some screenshots in case I need to set it back).