?
Solved

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

Posted on 2008-10-29
9
Medium Priority
?
317 Views
Last Modified: 2013-11-30
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."
0
Comment
Question by:MOPSC
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 
LVL 12

Expert Comment

by:florin_s
ID: 22834502
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
 

Author Comment

by:MOPSC
ID: 22835330
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
 
LVL 12

Expert Comment

by:florin_s
ID: 22835737
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
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 

Author Comment

by:MOPSC
ID: 22837581
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
 
LVL 12

Expert Comment

by:florin_s
ID: 22838762
0
 

Author Comment

by:MOPSC
ID: 23131499
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
 

Accepted Solution

by:
MOPSC earned 0 total points
ID: 23339936
Had to make a phone to Microsoft Technical Support and they were able to resolve this issue.
0
 
LVL 12

Expert Comment

by:florin_s
ID: 23371447
what was the solution provided by them?
0
 

Author Comment

by:MOPSC
ID: 23372429
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

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Question has a verified solution.

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

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
how to add IIS SMTP to handle application/Scanner relays into office 365.

719 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