• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Routing between Exch 2003 and Exch 2007

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2007] >> Message Routing >> Routing between Exch 2003 and Exch 2007 Page: [1]
Login
Message << Older Topic   Newer Topic >>
Routing between Exch 2003 and Exch 2007 - 9.Jan.2008 10:57:05 AM   
rhyswatson

 

Posts: 10
Joined: 29.Oct.2007
Status: offline
Hi,

I have a slight problem with message routing that's starting to drive me crazy. We started out some time back with 1 Exchange 2003 server. We have recently added a new remote office and installed Exchage 2007 in there and all was well. The default connectors were created and mail flow worked fine. We then added another Exchange 2007 server to a new remote office, created the bidirectional connectors but mail just won't get there. The 2003 server is basically our hub with the 2007 servers as spokes. I can see that when when I send e-mail from the 2003 server to a mailbox on the newest 2007 server the message goes down the wrong connector and queues at the first 2007 server we installed. There is no direct link between the two 2007 servers so eventually we end up with an NDR.

NB: all three servers are physically seperated and configured as seperate sites within AD.

The cost on both sets of connectors is the same as are the site link costs. I was under the impression that in that scenario the route of the message would be done based on hop counts but clearly this isn't happening.

Messages between the two 2007 servers fail also. Based on my Site topology a message from the first 2007 server should go to the 2003 server site and the it's next hop should be the destination 2007 server (and visa versa) but I just get an NDR.

Can anyone suggest where I may have gone wrong with my config?

Thanks for any suggestions.
Post #: 1
RE: Routing between Exch 2003 and Exch 2007 - 9.Jan.2008 11:14:48 AM   
John Weber

 

Posts: 1236
Joined: 20.Apr.2005
From: Portland, Oregon
Status: offline
My opinion is going to be that the second e2k7 server and the e2k3 server AND the first e2k7 server are not in the same coexistence routing group  - properly, that is.

Can you provide us with:

Get-routinggroupconnector

You should have used this command to create the routing group, or add to the existing one.  All e2k7 servers are considered to be members of the same routing group,...

New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Ex2007Hub1.contoso.com" -TargetTransportServers "Ex2003BH1.contoso.com" -Cost 100 -Bidirectional $true -PublicFolderReferralsEnabled $true

There is a way to put multiple server names in the "source" piece, but I will be doggonned if I can find it right at the moment.

[edit]  found it:





SourceTransportServers


Optional


Microsoft.Exchange.Data.MultiValuedProperty


Use the SourceTransportServers parameter to specify the host name or FQDN of the transport servers that will be used to send messages to the target transport servers. You can specify more than one server by separating each entry with a comma. For more information about how to add or remove values from multivalued properties, see Modifying Multivalued Properties


-jmw

< Message edited by John Weber -- 9.Jan.2008 11:18:38 AM >

(in reply to rhyswatson)
Post #: 2
RE: Routing between Exch 2003 and Exch 2007 - 9.Jan.2008 11:43:06 AM   
rhyswatson

 

Posts: 10
Joined: 29.Oct.2007
Status: offline
Thanks for the quick reply John. Result of get-routinggroupconnector is below.

NB: I've replaced the domain name with "OurDomain". Our first server has been called "EXCH2003", the first Exch 2007 server is called "EXCH2007 A" and the second  "EXCH2007 B"

When creating the new routing group connector for the second E2K7 server I used the New-Routinggroupconnector command. Prety much just copied it from the MS website.

C:\>get-routinggroupconnector | format-list

TargetRoutingGroup           : First Routing Group
Cost                         : 1
TargetTransportServers       : {EXCH2003}
ExchangeLegacyDN             : /o=OurDomain Organization/ou=Exchange Administra
                              tive Group (FYDIBOHF23SPDLT)/cn=Configuration/cn
                              =Connections/cn=EXCH2007 A-EXCH2003
PublicFolderReferralsEnabled : True
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {EXCH2007 A}
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : EXCH2007 A
MinAdminVersion              : -2147453113
AdminDisplayName             :
ExchangeVersion              : 0.1 (8.0.535.0)
Name                         : EXCH2007 A-EXCH2003
DistinguishedName            : CN=EXCH2007 A-EXCH2003,CN=Connections,CN=Exchange Ro
                              uting Group (DWBGZMFD01QNBJR),CN=Routing Groups,
                              CN=Exchange Administrative Group (FYDIBOHF23SPDL
                              T),CN=Administrative Groups,CN=OurDomain Organiz
                              ation,CN=Microsoft Exchange,CN=Services,CN=Confi
                              guration,DC=OurDomain
Identity                     : EXCH2007 A-EXCH2003
Guid                         : c7195340-4e33-4720-bccb-2af5ad8174fd
ObjectCategory               : OurDomain/Configuration/Schema/ms-Exch-Routing-G
                              roup-Connector
ObjectClass                  : {top, msExchConnector, msExchRoutingGroupConnect
                              or}
WhenChanged                  : 06/11/2007 14:56:26
WhenCreated                  : 29/09/2007 13:41:40
OriginatingServer            : EXCH2007 B.OurDomain
IsValid                      : True
TargetRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost                         : 1
TargetTransportServers       : {EXCH2007 A}
ExchangeLegacyDN             : /o=OurDomain Organization/ou=First Administrativ
                              e Group/cn=Configuration/cn=Connections/cn=EXCH2003-
                              EXCH2007 A
PublicFolderReferralsEnabled : True
SourceRoutingGroup           : First Routing Group
SourceTransportServers       : {EXCH2003}
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : EXCH2003
MinAdminVersion              : -2147453113
AdminDisplayName             :
ExchangeVersion              : 0.1 (8.0.535.0)
Name                         : EXCH2003-EXCH2007 A
DistinguishedName            : CN=EXCH2003-EXCH2007 A,CN=Connections,CN=First Routi
                              ng Group,CN=Routing Groups,CN=First Administrati
                              ve Group,CN=Administrative Groups,CN=OurDomain O
                              rganization,CN=Microsoft Exchange,CN=Services,CN
                              =Configuration,DC=OurDomain
Identity                     : EXCH2003-EXCH2007 A
Guid                         : 31b23efd-f9f2-44bf-96c3-7470ae2495e6
ObjectCategory               : OurDomain/Configuration/Schema/ms-Exch-Routing-G
                              roup-Connector
ObjectClass                  : {top, msExchConnector, msExchRoutingGroupConnect
                              or}
WhenChanged                  : 06/11/2007 14:56:26
WhenCreated                  : 29/09/2007 13:41:40
OriginatingServer            : EXCH2007 B.OurDomain
IsValid                      : True
TargetRoutingGroup           : First Routing Group
Cost                         : 1
TargetTransportServers       : {EXCH2003}
ExchangeLegacyDN             : /o=OurDomain Organization/ou=Exchange Administra
                              tive Group (FYDIBOHF23SPDLT)/cn=Configuration/cn
                              =Connections/cn=EXCH2007 B-EXCH2003
PublicFolderReferralsEnabled : True
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {EXCH2007 B}
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : EXCH2007 B
MinAdminVersion              : -2147453113
AdminDisplayName             :
ExchangeVersion              : 0.1 (8.0.535.0)
Name                         : EXCH2007 B-EXCH2003
DistinguishedName            : CN=EXCH2007 B-EXCH2003,CN=Connections,CN=Exchange Ro
                              uting Group (DWBGZMFD01QNBJR),CN=Routing Groups,
                              CN=Exchange Administrative Group (FYDIBOHF23SPDL
                              T),CN=Administrative Groups,CN=OurDomain Organiz
                              ation,CN=Microsoft Exchange,CN=Services,CN=Confi
                              guration,DC=OurDomain
Identity                     : EXCH2007 B-EXCH2003
Guid                         : 4200589d-6cc7-4ca8-ab23-2adfe621f186
ObjectCategory               : OurDomain/Configuration/Schema/ms-Exch-Routing-G
                              roup-Connector
ObjectClass                  : {top, msExchConnector, msExchRoutingGroupConnect
                              or}
WhenChanged                  : 09/01/2008 14:42:37
WhenCreated                  : 07/11/2007 16:50:41
OriginatingServer            : EXCH2007 B.OurDomain
IsValid                      : True
TargetRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost                         : 1
TargetTransportServers       : {EXCH2007 B}
ExchangeLegacyDN             : /o=OurDomain Organization/ou=First Administrativ
                              e Group/cn=Configuration/cn=Connections/cn=Hgbse
                              rver2-EXCH2003
PublicFolderReferralsEnabled : True
SourceRoutingGroup           : First Routing Group
SourceTransportServers       : {EXCH2003}
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : EXCH2003
MinAdminVersion              : -2147453113
AdminDisplayName             :
ExchangeVersion              : 0.1 (8.0.535.0)
Name                         : EXCH2007 B-EXCH2003
DistinguishedName            : CN=EXCH2007 B-EXCH2003,CN=Connections,CN=First Routi
                              ng Group,CN=Routing Groups,CN=First Administrati
                              ve Group,CN=Administrative Groups,CN=OurDomain O
                              rganization,CN=Microsoft Exchange,CN=Services,CN
                              =Configuration,DC=OurDomain
Identity                     : EXCH2007 B-EXCH2003
Guid                         : 70d9a225-d6a3-4d9e-93fc-07b4de553749
ObjectCategory               : OurDomain/Configuration/Schema/ms-Exch-Routing-G
                              roup-Connector
ObjectClass                  : {top, msExchConnector, msExchRoutingGroupConnect
                              or}
WhenChanged                  : 09/01/2008 14:41:17
WhenCreated                  : 07/11/2007 16:50:41
OriginatingServer            : EXCH2007 B.OurDomain
IsValid                      : True

(in reply to John Weber)
Post #: 3
RE: Routing between Exch 2003 and Exch 2007 - 13.Feb.2008 1:15:33 AM   
hcxeadmin

 

Posts: 144
Joined: 6.Feb.2007
Status: offline
you can add multiple servers with a comma. it'd not necessary to put the fqdn but whatever works...

-targettransportservers srv1,srvr2 -sourcetransportservers srvr2,srvr3 etc

(in reply to rhyswatson)
Post #: 4
RE: Routing between Exch 2003 and Exch 2007 - 13.Feb.2008 4:10:38 AM   
rhyswatson

 

Posts: 10
Joined: 29.Oct.2007
Status: offline
Thanks for that. Tried adding the multiple target and source transport servers based on Johns post but still had the same issue. Messages from the 2003 routing group still go to the first 2007 Exchange server and then stop there (as there is no direct link between the 2007 servers).

I've found (in some random article) that Exchange 2007 will never route into the 2003 routing group and then back into the 2007 one at all. That being the case the scenario I'm in is hopeless until I put a 2007 server in our hub site (where the 2003 server currently is and where all remote sites have comms to). I'm thinking (and hoping) that if I put a 2007 server in the hub site and then modify the routing group connector to route only between the Ex2003 and Ex2007 server in the main hub site then Active Directory will then be able to route messages based on our Sites and Services configuration.

That should then remove the main problem of mail going to the wrong server from the Ex2003 routing group and allow messgae flow from pretty much anywhere.

What do you think gents?

(in reply to hcxeadmin)
Post #: 5

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2007] >> Message Routing >> Routing between Exch 2003 and Exch 2007 Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter