Exchange 2010 to 2003 mail flow failing
Scenario: Just installed exchange 10 to coexist with an existing exchange 03 organization with two 03 servers
Problem: Mail flow fails from 10 to 03 but for just one of the 03 servers (slave). Mail flow works from 10 to 03 (master) just fine.
Variables:
Single forest, single domain
Exchange 2003 master – Ex03A (AD site A)
Exchange 2003 slave – Ex03B (AD site
Exchange 2010 – Ex10Z (AD site A)
Current mail flow:
Ex03A <-> Ex03B
Ex03A <-> Ex10Z
Ex03B -> Ex10Z
Ex10Z -fails> Ex03B
Output from get-routinggroupconnector | fl ran from Ex10Z
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : First Routing Group
Cost : 1
TargetTransportServers : {Ex03A}
ExchangeLegacyDN : /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuratio
n/cn=Connections/cn=Ex10Z-Ex03A
PublicFolderReferralsEnabled : True
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {Ex10Z}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex10Z
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex10Z-Ex03A
DistinguishedName : CN=Ex10Z-Ex03A,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routin
g Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=
First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=c
om
Identity : Ex10Z-Ex03A
Guid : ae599ccb-bdfb-4765-b846-a9066ad8dcfb
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost : 1
TargetTransportServers : {Ex10Z}
ExchangeLegacyDN : /o=First Organization/ou=First Administrative Group/cn=Configuration/cn=Connections/cn=G
JL2-Ex10Z
PublicFolderReferralsEnabled : True
SourceRoutingGroup : First Routing Group
SourceTransportServers : {Ex03A}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex03A
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex03A-Ex10Z
DistinguishedName : CN=Ex03A-Ex10Z,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Adm
inistrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,C
N=Services,CN=Configuration,DC=company,DC=com
Identity : Ex03A-Ex10Z
Guid : 382fae0f-beed-4003-adaf-237a2dddd91b
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
Output from get-message | fl on Ex10Z where the queue is filling up:
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
Subject : Test
InternetMessageId : <1D2C2D8EE4345940A8D1F69B19E060E38A8B@ex10Z.company.com>
FromAddress : ex10user@company.com
Status : Ready
Size : 5.982 KB (6,126 bytes)
MessageSourceName : FromLocal
SourceIP : 255.255.255.255
SCL : -1
DateReceived : 2/7/2015 3:57:10 PM
ExpirationTime : 2/9/2015 3:57:10 PM
LastError : There is currently no route to the mailbox database.
RetryCount : 0
Recipients :
ComponentLatency :
MessageLatency : 15:52:27.3487757
DeferReason : None
Priority : Normal
MessageIdentity : ex10Z\Unreachable\103
Queue : ex10Z\Unreachable
Identity : ex10Z\Unreachable\103
IsValid : True
Proposed solution:
In order to fix mail flow from Ex10Z -> Ex03B, run the following command in Ex10Z EMS
New-RoutingGroupConnector -Name "Ex10Z-Ex03B" -SourceTransportServers "Ex10Z.company.com" -TargetTransportServers "Ex03B.company.com" -Cost 100 -Bidirectional $true
Restart transport service on Ex10Z, restart smtp service on Ex03A and Ex03B
Will this proposed solution work or should I be looking elsewhere?
Problem: Mail flow fails from 10 to 03 but for just one of the 03 servers (slave). Mail flow works from 10 to 03 (master) just fine.
Variables:
Single forest, single domain
Exchange 2003 master – Ex03A (AD site A)
Exchange 2003 slave – Ex03B (AD site
Exchange 2010 – Ex10Z (AD site A)
Current mail flow:
Ex03A <-> Ex03B
Ex03A <-> Ex10Z
Ex03B -> Ex10Z
Ex10Z -fails> Ex03B
Output from get-routinggroupconnector | fl ran from Ex10Z
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : First Routing Group
Cost : 1
TargetTransportServers : {Ex03A}
ExchangeLegacyDN : /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuratio
n/cn=Connections/cn=Ex10Z-Ex03A
PublicFolderReferralsEnabled : True
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {Ex10Z}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex10Z
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex10Z-Ex03A
DistinguishedName : CN=Ex10Z-Ex03A,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routin
g Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=
First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=c
om
Identity : Ex10Z-Ex03A
Guid : ae599ccb-bdfb-4765-b846-a9066ad8dcfb
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost : 1
TargetTransportServers : {Ex10Z}
ExchangeLegacyDN : /o=First Organization/ou=First Administrative Group/cn=Configuration/cn=Connections/cn=G
JL2-Ex10Z
PublicFolderReferralsEnabled : True
SourceRoutingGroup : First Routing Group
SourceTransportServers : {Ex03A}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex03A
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex03A-Ex10Z
DistinguishedName : CN=Ex03A-Ex10Z,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Adm
inistrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,C
N=Services,CN=Configuration,DC=company,DC=com
Identity : Ex03A-Ex10Z
Guid : 382fae0f-beed-4003-adaf-237a2dddd91b
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
Output from get-message | fl on Ex10Z where the queue is filling up:
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
Subject : Test
InternetMessageId : <1D2C2D8EE4345940A8D1F69B19E060E38A8B@ex10Z.company.com>
FromAddress : ex10user@company.com
Status : Ready
Size : 5.982 KB (6,126 bytes)
MessageSourceName : FromLocal
SourceIP : 255.255.255.255
SCL : -1
DateReceived : 2/7/2015 3:57:10 PM
ExpirationTime : 2/9/2015 3:57:10 PM
LastError : There is currently no route to the mailbox database.
RetryCount : 0
Recipients :
ComponentLatency :
MessageLatency : 15:52:27.3487757
DeferReason : None
Priority : Normal
MessageIdentity : ex10Z\Unreachable\103
Queue : ex10Z\Unreachable
Identity : ex10Z\Unreachable\103
IsValid : True
Proposed solution:
In order to fix mail flow from Ex10Z -> Ex03B, run the following command in Ex10Z EMS
New-RoutingGroupConnector -Name "Ex10Z-Ex03B" -SourceTransportServers "Ex10Z.company.com" -TargetTransportServers "Ex03B.company.com" -Cost 100 -Bidirectional $true
Restart transport service on Ex10Z, restart smtp service on Ex03A and Ex03B
Will this proposed solution work or should I be looking elsewhere?
Comments
-
joelsfood Member Posts: 1,027 ■■■■■■□□□□Honestly, I did not read thorugh all of the current settings.
That being said, yes, that's where I would start. Any time I've had 2010 and 2003 coexistings, and there's been flow problems, it's been the routing groups.
Just make SURE you remove the routing group when you retire the 2003 servers, or you'll have issues with mailflow to the 2010 box, even when it's the only server. -
phoeneous Member Posts: 2,333 ■■■■■■■□□□Honestly, I did not read thorugh all of the current settings.
That being said, yes, that's where I would start. Any time I've had 2010 and 2003 coexistings, and there's been flow problems, it's been the routing groups.
Just make SURE you remove the routing group when you retire the 2003 servers, or you'll have issues with mailflow to the 2010 box, even when it's the only server.
Tried and didnt work. Queue on Ex10Z is still unable to send to Ex03B but Ex03B is able to send to Ex10Z. -
joelsfood Member Posts: 1,027 ■■■■■■□□□□What does EX03B show for routing? I do'nt see it mentioned in either of those routing group connectors
-
phoeneous Member Posts: 2,333 ■■■■■■■□□□What does EX03B show for routing? I do'nt see it mentioned in either of those routing group connectors
Here is the new get-routinggroupconnector | fl. Interesting that it created two Ex10Z-Ex03B identities despite me issuing the Bidirectional flag. Shouldnt there be one for Ex03B-Ex10Z?
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : First Routing Group
Cost : 1
TargetTransportServers : {Ex03A}
ExchangeLegacyDN : /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuratio
n/cn=Connections/cn=Ex10Z-Ex03A
PublicFolderReferralsEnabled : True
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {Ex10Z}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex10Z
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex10Z-Ex03A
DistinguishedName : CN=Ex10Z-Ex03A,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routin
g Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=
First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=c
om
Identity : Ex10Z-Ex03A
Guid : ae599ccb-bdfb-4765-b846-a9066ad8dcfb
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost : 1
TargetTransportServers : {Ex10Z}
ExchangeLegacyDN : /o=First Organization/ou=First Administrative Group/cn=Configuration/cn=Connections/cn=G
JL2-Ex10Z
PublicFolderReferralsEnabled : True
SourceRoutingGroup : First Routing Group
SourceTransportServers : {Ex03A}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex03A
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex03A-Ex10Z
DistinguishedName : CN=Ex03A-Ex10Z,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Adm
inistrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,C
N=Services,CN=Configuration,DC=company,DC=com
Identity : Ex03A-Ex10Z
Guid : 382fae0f-beed-4003-adaf-237a2dddd91b
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : First Routing Group
Cost : 100
TargetTransportServers : {Ex03B}
ExchangeLegacyDN : /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuratio
n/cn=Connections/cn=Ex10Z-Ex03B
PublicFolderReferralsEnabled : True
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {Ex10Z}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex10Z
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex10Z-Ex03B
DistinguishedName : CN=Ex10Z-Ex03B,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Rout
ing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,C
N=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC
=com
Identity : Ex10Z-Ex03B
Guid : 37a9f53c-2166-440c-b54b-23b165323ae3
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/8/2015 8:09:08 AM
WhenCreated : 2/8/2015 8:09:08 AM
WhenChangedUTC : 2/8/2015 4:09:08 PM
WhenCreatedUTC : 2/8/2015 4:09:08 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost : 100
TargetTransportServers : {Ex10Z}
ExchangeLegacyDN : /o=First Organization/ou=First Administrative Group/cn=Configuration/cn=Connections/cn=G
JLSRVLVMX1-Ex03B
PublicFolderReferralsEnabled : True
SourceRoutingGroup : First Routing Group
SourceTransportServers : {Ex03B}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex03B
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex10Z-Ex03B
DistinguishedName : CN=Ex10Z-Ex03B,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First A
dministrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange
,CN=Services,CN=Configuration,DC=company,DC=com
Identity : Ex10Z-Ex03B
Guid : c8cd8eea-4ad6-47b4-bef5-9fb93288bca3
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/8/2015 8:09:08 AM
WhenCreated : 2/8/2015 8:09:08 AM
WhenChangedUTC : 2/8/2015 4:09:08 PM
WhenCreatedUTC : 2/8/2015 4:09:08 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True -
joelsfood Member Posts: 1,027 ■■■■■■□□□□Those look right, one each way, from each pair of routing groups. I would try adjusting the cost to 1
-
lsud00d Member Posts: 1,571Have you looked at layer 3? What are the logs saying?
To that extent, what does a route print show?
It sounds like it might be site/schema related. This link has more info on it
http://www.cosonok.com/2013/01/a-fistful-of-exchange-2010-errors-and.html -
phoeneous Member Posts: 2,333 ■■■■■■■□□□Layer 3 is fine, Ex10Z can telnet:25 to Ex03B.
Thanks for the link, I think it's the permission inheritance issue. -
phoeneous Member Posts: 2,333 ■■■■■■■□□□Fixed.
In adsiedit, enabled inherit permissions on Ex03B here:
CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=First Administrative Group, CN=Servers, CN=Ex03B -
phoeneous Member Posts: 2,333 ■■■■■■■□□□I also ran into the problem of not being able to add email to my phone through activesync. After checking error logs, I found the culprit:
Exception type: Microsoft.Exchange.Data.Directory.ADOperationException
Exception message: Active Directory operation failed on dc.company.com. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-03151E07, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
Turns out because I'm domain/enterprise admin, inherited permissions are disabled for security reasons which makes total sense.
Followed the steps here and problem fixed:
iPhones don't sync with Exchange 2010 - connection to the server failed -
joelsfood Member Posts: 1,027 ■■■■■■□□□□Thanks for the update phoeneous, I've filed this one away in my notes. I might hope not to see exchange 2003 again, but I'm sure I will.