Exchange 2010/2003 Coexistence - Mail Problem

Hi,

I installed two new Exchange 2010 servers in a domain that already had an one Exchange 2003 server in it.  Both 2010 servers are configured with identical roles but the DB is only one one.


As a test, I moved one user over from 2003 to 2010 and the move went fine. My only problem is that, although he can send mail out to the internet, he is not able to receive any mail at all.

The installation seems to pulled all appropriate connector settings so I'm a bit miffed why it isn't working.  I do know, however, that the SMTP connector on the 2003 server seems to be essential to getting any mail in or out of the network.  If it's turned off, no mail flow at all.  Shouldn't this be running on 2010?

TIA

- dan -

LVL 7
dansotoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hypercat (Deb)Commented:
You need to create a routing group connector between the 2003 and 2010 server:
http://technet.microsoft.com/en-us/library/aa998574.aspx
I assume that you are still receiving your incoming email on the 2003 server. A routing group connector is essential to route the email between the 2003 server and the 2010 server so that mailboxes on the 2010 server can receive mail. You actually need two routing group connectors - one to route mail from the 2010 server to the 2003 server, and one to route the mail from the 2003 server to the 2010 server (i.e., you need to go both ways to ensure that all mail flow is happening properly).
0
dansotoAuthor Commented:
Actually the RCG's were created already with the appropriate information in it... I have since deleted them and recreated them to see if that works... to no avail :(
0
Hypercat (Deb)Commented:
Correction - in rereading that article, I see that there is an option for a bi-directional routing group connector. I was speaking from my experience with Exchange 2007 when I said you need two routing group connectors. If the connector is two-way, then you would only need one, I presume.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Hypercat (Deb)Commented:
How did you delete them? Did you use the management shell?
0
dansotoAuthor Commented:
yes...used the shell... only way to do it...and only way to create it.  When you use the shel to create it you can use =bidirectional $true and it creates both connectors for you...

New info though....
I just telneted from that 2010 server to itself and tried to generate a mail that way... if I tried to send to an external domain I get "relay denied" so I need to see where that's being restricted...
0
dansotoAuthor Commented:
Correction:  message is "unable to relay"   don't see in the send connector where this is being restricted though
0
Hypercat (Deb)Commented:
Do you have a send connector set up on your 2010 server to route the mail out to the Internet directly? I assume that you are controlling the receive end through a router/firewall that is redirecting the incoming SMTP mail to your 2003 or 2010 server. Which one is actually receiving the incoming mail at this point?
0
Hypercat (Deb)Commented:
Whoo - I'm getting my servers mixed up here. The send (SMTP) connector would be on the 2003 server.  On the 2010 end, you need to configure a receive connector for Internet email to come in directly to the 2010 Edge Transport server, as well as a receive connector for the client end. Again, these should have been created automatically during the install. Where/what they are depends on whether you have one server doing all roles, or if you have a separate Edge Transport server:
http://technet.microsoft.com/en-us/library/aa996395.aspx 
0
Hypercat (Deb)Commented:
Looking back at your OP, you said both servers are created with identical roles. Could you please elaborate? Are they in different sites? Are they both running all of the Exchange 2010 roles? (I don't think that will work, as far as I know, if they are in the same site, but I'm still a beginner when it comes to the more elaborate Exchange 2007/2010 configurations.)
0
dansotoAuthor Commented:
While there is an SMTP connector on the 2003 server, my goal is to make this server go away after I move all the mailboxes over.  If that server goes away..doesn't the receiver connector on 2003 handle that in place?

Also, my understanding is that I don't need an Edge Transport server ... I though I could just use the Hub Transport to relay mail
0
Hypercat (Deb)Commented:
Yes, there is no "SMTP connector" on the Exchange 2010 server - this function is handled by the receive connector(s). Normally you have two receive connectors, one for internal email that requires authentication and one for external email that allows anonymous connections. These are normally created during the installation process.
You need either one server handling all roles or multiple servers handling multiple roles.  If you have one server handling all roles (Client Access, Mailbox, and Hub Transport) you don't need a separate Edge Transport server. But if you separate out the roles in any way, then you must have a separate Edge Transport server -  at least that is my understanding at this point... My question is why do you have two separate 2010 servers set up? If you are not going to use separate servers for separate roles, then all roles must be on one server. I'm going to do some additional research on this to see if Exchange 2010 is different in this area than Exchange 2007.
0
dansotoAuthor Commented:
Hey...Thanks for your help.  I actually resolved it and it wasn't anything relate to the connectors.
In short, client had a firewall rule that basically was routing smtp traffic to the wrong host ....

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.