Solved

Mail not routing from 2003 to 2007 server

Posted on 2007-11-22
4
1,702 Views
Last Modified: 2008-02-01
We are having a problem with the Interop RGC that routes mail between the 2003 and 2007 server. Mail flows fine from the Exchange 2007 server to the Exchange 2003 server, however it gets stuck in the "Messages with an Unreachable Destination" queue on the Exchange 2003 server. I have attempted to recreate the RGC's with no luck. Mail is flowing outbound to the internet, so I know part of the RGC is working. In this situation, Exchange1 is the 2003 server, Exchange2 is the new 2007 mailbox server. EXCA1 is the CAS and HT server. When looking at the events, it's seems almost like Exchange1 dose not know to use EXCA1 to get to Exchange2, but I don't know how to convince it to do so. Routing groups are set up as follows:

TargetRoutingGroup           : First Routing Group
Cost                         : 10
TargetTransportServers       : {EXCHANGE1}
ExchangeLegacyDN             : /o=Domain/ou=Exchange Administrative Group (FY
                               DIBOHF23SPDLT)/cn=Configuration/cn=Connections/c
                               n=Interop RGC
PublicFolderReferralsEnabled : True
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {EXCA1}
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : EXCA1
MinAdminVersion              : -2147453113
AdminDisplayName             :
ExchangeVersion              : 0.1 (8.0.535.0)
Name                         : Interop RGC
DistinguishedName            : CN=Interop RGC,CN=Connections,CN=Exchange Routin
                               g Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=E
                               xchange Administrative Group (FYDIBOHF23SPDLT),C
                               N=Administrative Groups,CN=Domain,CN=Microsoft
                                Exchange,CN=Services,CN=Configuration,DC=domain
                               ,DC=com
Identity                     : Interop RGC
Guid                         : 0f8fe667-d5e3-4de3-8fc5-96527b5b0787
ObjectCategory               : domain.com/Configuration/Schema/ms-Exch-Routin
                               g-Group-Connector
ObjectClass                  : {top, msExchConnector, msExchRoutingGroupConnect
                               or}
WhenChanged                  : 11/20/2007 10:26:03 AM
WhenCreated                  : 11/12/2007 5:15:22 PM
OriginatingServer            : ad2.domain.com
IsValid                      : True

TargetRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost                         : 10
TargetTransportServers       : {EXCA1}
ExchangeLegacyDN             : /o=Domain/ou=First Administrative Group/cn=Con
                               figuration/cn=Connections/cn=Interop RGC
PublicFolderReferralsEnabled : True
SourceRoutingGroup           : First Routing Group
SourceTransportServers       : {EXCHANGE1}
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : EXCHANGE1
MinAdminVersion              : -2147453113
AdminDisplayName             :
ExchangeVersion              : 0.1 (8.0.535.0)
Name                         : Interop RGC
DistinguishedName            : CN=Interop RGC,CN=Connections,CN=First Routing G
                               roup,CN=Routing Groups,CN=First Administrative G
                               roup,CN=Administrative Groups,CN=Domain,CN=Mic
                               rosoft Exchange,CN=Services,CN=Configuration,DC=
                               domain,DC=com
Identity                     : Interop RGC
Guid                         : 40e3cef1-09a2-4134-826c-147ced478941
ObjectCategory               : domain.com/Configuration/Schema/ms-Exch-Routin
                               g-Group-Connector
ObjectClass                  : {top, msExchConnector, msExchRoutingGroupConnect
                               or}
WhenChanged                  : 11/20/2007 10:25:35 AM
WhenCreated                  : 11/12/2007 5:15:23 PM
OriginatingServer            : ad2.domain.com
IsValid                      : True

When turning up event logging on the Exchange1 server, I see the following events:

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Routing Engine/Service
Event ID: 955
Date:  11/22/2007
Time:  5:15:59 PM
User:  N/A
Computer: EXCHANGE1
Description:
SMTP GetNextHop returned hr=0x80004005 in 0ms.
 DestAddr=<exchange2.domain.com>
 DestType=<SMTP>
 MsgType=0x2
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Queuing Engine
Event ID: 4003
Date:  11/22/2007
Time:  5:15:59 PM
User:  N/A
Computer: EXCHANGE1
Description:
The domain 'exchange2.domain.com' is currently unreachable.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Routing Engine/Service
Event ID: 960
Date:  11/22/2007
Time:  5:22:54 PM
User:  N/A
Computer: EXCHANGE1
Description:
When trying to obtain routing related info about the following server, the server doesn't appear to be a member of any routing group. Legitimately, this could happen if the server is non-mail related server (for example an IM server). Otherwise, check your DS configuration for any corruption in routing group membership attribute. <CN=EXCHANGE2,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com>
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
Comment
Question by:mikemsd
  • 2
4 Comments
 
LVL 22

Expert Comment

by:ATIG
Comment Utility
most of the time I have seen problem from 03 to 07 it has been 1 of 2 things

1. AV on the 03 server
2. smart host specified on the 03 smtp virtual server

please check both and try disabling the AV
0
 
LVL 2

Author Comment

by:mikemsd
Comment Utility
I actually got this figured out. After quite a bit of digging, it turns out the Exchange2 server was not in the correct routing group. I discovered that, after in desperation I tried to add the Hub Transport role to the backend server and just move the routing group connectors. When I tried to do that it wouldn't start the hub transport role stating in the event log that the server wasn't a member of any routing group.

When I looked at the routing group in ADSI edit, the msExchRoutingGroupMembersBL attribute did not have Exchange2 listed. I resolved it by adding the correct routing group to the msExchHomeRoutingGroup attribute on the server using the following instructions from MS:

http://technet.microsoft.com/en-us/library/bb267020.aspx
0
 
LVL 22

Accepted Solution

by:
ATIG earned 500 total points
Comment Utility
good stuff
0
 

Expert Comment

by:N8tvtexan
Comment Utility
Just a quick FYI: I had this same problem. I did not want to change internal DNS at all, so I moved the SMTP Server IP to the new Exch 2007 box. However, I forgot to remove it from the the old SMTP server on the Exch 2003 box. What clued me in was the "Additional Queue Information" on the bottom when you have a Queue select in ESM 2003. There error was "Could not bind to server in DNS". Changed the SMTP server Ip to the machine IP and email started flowing, and PFs started replicating.
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Learn to move / copy / export exchange contacts to iPhone without using any software. Also see the issues in configuration of exchange with iPhone to migrate contacts.
In this video we show how to create a User Mailbox 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 Recipients >> Mailb…
In this video we show how to create a mailbox database 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 Servers >> Data…

772 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

11 Experts available now in Live!

Get 1:1 Help Now