Solved

Microsoft Exchange 2003 Decomissioning

Posted on 2013-06-04
17
331 Views
Last Modified: 2013-06-07
A previous Networkin Admin setup Exchange Server 2010 in addition to the Exchange Server 2003 that was already in place. I want to get rid of the Exchange Server 2003 and was working on steps to removing it using msexchange.org. I followed all steps and got to the point where I was deleting the routing group connectors on the 2003 box. As soon as I deleted the Routing Group Connector from the First Administrative Group, I was unable to get mail from the outside. Also,  I was able to receive mail to the outside and have everything work internally without issue though.

Does anyone have idea what I could be missing? Thanks in advance for your help!


Elvir
0
Comment
Question by:sweeneym
  • 10
  • 6
17 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39220723
You need to ensure that SMTP traffic is pointing at Exchange 2010 (NAT on your firewall) and you have Anonymous enabled on the Default Receive Connector. That is all that is required.

Simon.
0
 

Author Comment

by:sweeneym
ID: 39220750
There is 2 receive connectors and the only difference is the FQDN he set. Looks like one is external webmail.XXXX.org and one is internal emailsvr.XXXX.org.  Both have Anonymous checked.

It's possible the Cisco ASA 5510 needs to allow SMTP to the Exchange 2010 server.

I'll take a look at that tomorrow. Thanks!
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39220755
You shouldn't have Anonymous enabled on the Second connector, which should be called "Client Receive Connector" (unless modified). One should be listening on port 25 (Default) and the other on 465 (Client).

The Cisco ASA should also have fixup SMTP disabled on it.
http://semb.ee/fixupsmtp

Simon.
0
 

Author Comment

by:sweeneym
ID: 39220761
The external connector has port 587 and the internal has port 25 set. Looks like this may be set incorrectly.

I'm assuming Fixup is already disabled on the ASA since the Exchange 2003 box is behind it also.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39221893
I would check FIXUP SMTP anyway. It doesn't have to be disabled for Exchange to work, but I have seen odd results when it isn't.

Simon.
0
 

Author Comment

by:sweeneym
ID: 39222630
**UPDATE**  6/5/13 11:24AM EST
ESMTP was enabled on the ASA and I disabled it. I then removed the RGC on the 2003 Exchange server and changed the port from 587 to 465 and so far it's eaxactly like yesterday where I can't get mail from the outside but I can send email to my gmail account without issue.

I do understand that these changes my take awhile and might not work immediately. I've seen many instances of changes working hours later.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39222776
From an external server you need to telnet in and see what server answers. Whether it is Exchange 2003 or 2010. Once you know that then you can start tracking what Exchange is doing with the message.

Simon.
0
 

Author Comment

by:sweeneym
ID: 39225545
Sembee2,
Can you elaborate on your last post? I don't 100% get what you are saying.
0
Too many email signature changes to deal with?

Are you constantly being asked to update your organization's email signatures? Do they take up too much of your time? Wouldn't you love to be able to manage all signatures from one central location, easily design them and deploy them quickly to users. Well, you can!

 

Author Comment

by:sweeneym
ID: 39225637
I tried from the outside to do a "telnet webmail.xxxx.org 25" and I did the same for port 587 and got a 220 response from both. So it looks like the ports are working properly, right?  I think that's what you were asking before.

How can I see what server is responding through telnet?

Also I noticed the MX record of the old 2003 Exchange Server is higher on the list than the Exchange 2010 server. Should I switch that around?
0
 

Author Comment

by:sweeneym
ID: 39225748
Received: from mail.xxxx.org (192.168.11.251) by emailsvr2.xxxxx.org
 (192.168.11.79) with Microsoft SMTP Server id 14.1.218.12; Thu, 6 Jun 2013
 09:58:07 -0400
Received: from mail-vb0-f45.google.com ([209.85.212.45]) by mail.xxxx.org
 with Microsoft SMTPSVC(6.0.3790.4675);       Thu, 6 Jun 2013 09:57:06 -0400

Above is what a message header looks like. It's hitting the old email server first then being handing over to the new server.
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39226971
With regards to the MX records, I would remove the record that is pointing at Exchange 2003 completely. Only have the single record pointing at Exchange 2010.

The 220 response is expected, it is HOW it answers that allows you to tell which server is answering.

Simon.
0
 

Author Comment

by:sweeneym
ID: 39227001
Yeah it's what I thought. The MX record for the old server has a higher priority and when the server is on the mail is still going to it but staying  at the old server because i'm removing the connector. Once I turn off the server physically the email is actually working correctly.  

Issue resolved. Thanks for all your help Simon!
0
 

Author Comment

by:sweeneym
ID: 39227502
I've requested that this question be closed as follows:

Accepted answer: 0 points for sweeneym's comment #a39227001

for the following reason:

Sembee2 provided the correct answer
0
 

Author Comment

by:sweeneym
ID: 39227006
All set!
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39227503
No points for my answers then?
0
 

Author Comment

by:sweeneym
ID: 39228912
I thought I did? I apologize if I didn't.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now