Exchange Server 2007sp1, coexisting w/ Exchange Server 2003sp2 - SMTP Send Connector problems

I had one server running Exchange Server 2003sp2 on WinServer2003sp2, sending mail successfully to the Internet. Then I installed Exchange Server 2007sp1 on WinServer2008x64.  In EMC, I created an "additional" Send Connector, along with the Exchange 2003 connector that was already there.  After, creating this additional Send Connector, mailboxes on each server cannot send mail to the Internet.   If you open ESM, the messages are held in the "Messages with an unreachable destination," queue.  Once the Exchange 2007 server is turned off the messages are sent to the Internet fine for the Exchange 2003 Server.
The below article seems to be related to my problem, however I need some detailed steps on how this can be accomplished if this is the recommended solution:
"When you introduce Exchange Server 2007 into an existing organization, in order to route mail you absolutely must have routing group connectors and an SMTP connector.
You'll need two routing group connectors, one going from the Exchange Server 2007 routing group to the Exchange Server 2003 routing group, and vice versa. You can set this up as part of the installation process, but if you missed it or you're not sure, you can check using the Exchange Management Shell and correct the problem there. If you don't, you will not be able to send mail between your servers. Messages will end up in unreachable destination queues."
MOPSCAsked:
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.

florin_sCommented:
Hi,

Here is a link from microsoft which explains what do you need to do for creating routing group connectors:

http://technet.microsoft.com/en-us/library/bb691187(EXCHG.80).aspx
0
MOPSCAuthor Commented:
Prior to creating an "additional" SMTP Connector to the Internet, I was able to send mail to the Internet from my Exchange 2003 server fine, the Exch2007 server hasn't been able to since it's been put into production.  I wanted to mention that outgoing mail flow works as follows:

Exch2007 user to Exch2003 user = works;
Exch2003user to Exch2003user = works;
Exch2003 user to Exch2007 user = DOESN'T work (I would assume the above suggestion would fix this issue);
Exch2007 user to Internet = DOESN'T work;
Exch2003 user to Internet = works only when Exchange 2007 server is shutdown
0
florin_sCommented:
Yes you need to create a routing group connector between 2003 and 2007 for all to work fine, after this you will be able to send mail to the internet.
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.

MOPSCAuthor Commented:
OK, I will try this when I can bring the server back on-line, probably won't be until this weekend.  I will post after doing so.  One last thing, is there a need to have 2 different Send Connectors,
i.e. SMTP Internet Connector for Exch2003 server and SMTP Internet Connector for Exch2007 server, while I have co-existence between the two versions of Exchange?  Currently, this is the setup that I have.
0
MOPSCAuthor Commented:
I see that I already have 2 routing group connectors created, i.e. on Exchange 2007 server there is one called Exch2007-Exch2003 and on the Exchange 2003 server there is one called Exch2003-Exch2007.  These were there by default and look like they were created when I ran the Exchange 2007 setup.  The article implies that one of the routing group connectors would be missing and need to be created through EMS.  Since, I already have the connectors there, do I need to create another one, etc.?
0
MOPSCAuthor Commented:
Had to make a phone to Microsoft Technical Support and they were able to resolve this issue.
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
florin_sCommented:
what was the solution provided by them?
0
MOPSCAuthor Commented:
The "additional" Send Connector (E2k7 to the Internet) I mentioned that I created prior to this issue starting, was causing part of the problem - we had to make some configuration changes specific to our environment that were missing or incorrect.  There were also a couple other changes made on the pre-existing E2k3 Internet Send Connector that needed modifying so it would work along side the E2k7 connector and not cause routing loops.  
0
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
Email Protocols

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.