SMTP / DNS Configuration Issues

[rko9h]

I am trying to migrate from Exchange 2000 (Ex2k) on a Windows 2000 member server to Exchange 2003 (Ex2k3) on a Windows 2003 member server. Ex2k3 is installed and part of the domain but I can not send e-mails from one Exchange server to the other. I am not confident in our network SMTP and DNS settings since we are unable to send mail to hotmail.com and a few other domains from the Ex2k server. However, test accounts on the Ex2k3 box can send e-mails to any external location, just not the Ex2k server. But, e-mails sent from an external account to the test account on the Ex2k3 machine bounce.

Below is the verbose report from smtpdiag. I am particularly concerned about MX records returning 2 IP addresses for navy.x.edu. Furthermore, computer x.x.x.35 is a Windows 2000 DC that I want to demote once the Ex2k server is gone. For some unknown reason, x.x.x.35 must be running for Ex2k to work. Clearly, I have some configuration errors. All computers use x.x.x.25 as the primary DNS server and x.x.x.26 as the alternate.

Please help. Thanks.

x.x.x.25 Windows 2003 DC (DHCP, Primary DNS, IIS, WINS)

x.x.x.26 Windows 2003 Member Server with Exchange 2003 (Secondary DNS, IIS)

x.x.x.35 Windows 2000 DC (AD-Integrated DNS) (ultimately want to demote and turn off)

x.x.x.134 Windows 2000 Member Server with Exchange 2000 (DNS - stopped, IIS - stopped except to support Exchange, Routing and Remote Access) (ultimately want to uninstall Exchange 2000 and turn off)

Also note that pinging navy.x.edu from outside the domain returns x.x.x.134 (the Ex2k box) whereas the same ping from inside returns x.x.x.35 (the DC that used to host all of the roles prior to me adding x.x.x.25) if done from one of the servers or x.x.x.25 if done from a client workstation.

- Navy LT

--- SmtpDiag ---

Searching for Exchange external DNS settings.
Computer name is HALSEY (x.x.x.26).
VSI 1 has the following external DNS servers:
There are no external DNS servers configured.

Checking SOA for navy.tamu.edu.
Checking external DNS servers.
Checking internal DNS servers.

Checking TCP/UDP SOA serial number using DNS server [x.x.x.25].
TCP test succeeded.
UDP test succeeded.
Serial number: 332

Checking TCP/UDP SOA serial number using DNS server [x.x.x.26].
TCP test succeeded.
UDP test succeeded.
Serial number: 331
SOA serial number match: Passed.

Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will try to validate that DNS is set up correctly for inbound mail. This test can fail for 3 reasons.
1) Local domain is not set up in DNS. Inbound mail cannot be routed to local mailboxes.
2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail, but will affect outbound mail.
3) Internal DNS is unaware of external DNS settings. This is a valid configuration for certain topologies.
Checking MX records using TCP: navy.tamu.edu.
A: navy.x.edu [x.x.x.35]
A: navy.x.edu [x.x.x.25]
Checking MX records using UDP: navy.tamu.edu.
A: navy.x.edu [x.x.x.35]
A: navy.x.edu [x.x.x.25]
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will try to validate that DNS is set up correctly for outbound mail. This test can fail for 3 reasons.
1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows 2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP queries first, then fall back to TCP queries.
2) Internal DNS does not know how to query external domains. You must either use an external DNS server or configure DNS server to query external domains.
3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: navy.tamu.edu.
A: navy.x.edu [x.x.x.35]
A: navy.x.edu [x.x.x.25]
Checking MX records using UDP: navy.x.edu.
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for rko9h@navy.x.edu.
Connecting to navy.x.edu [x.x.x.25] on port 25.
Connecting to the server failed. Error: 10061
Failed to submit mail to navy.tamu.edu.
Connecting to navy.x.edu [x.x.x.35] on port 25.
Connecting to the server failed. Error: 10061
Failed to submit mail to navy.x.edu.

 

[wblake76]

It looks to me like there are two MX records for your domain. That's why you have two addresses returned the first is the highest priority and and so on. This is a normal configuration. From the error message on connecting to the mail server all I can tell you is that it doesn't look like it was able to connect to port 25. Have you verifed port 25 is available by using telnet to port 25?

bh

 

[rko9h]

Port 25 is open for both exchange servers. I can connect to both on port 25 using telnet from inside the domain. Since we are part of a university network, the campus firewall blocks telnet requests to port 25 on both servers from outside the network. I can probably get the campus to open port 25 if needed but this doesn't seem to be the problem as the Echange 2000 server can receive e-mails from external accounts (i.e. Yahoo, Hotmail, etc.).

- Navy LT