none
No mail flow between Exchange 2010 and Exchange 2003 RRS feed

  • Question

  • Hi Everyone,

    I have an issue with email that does not flow from Exchange 2010 to Exchange 2003. We have an existing Exchange 2003 NLB FE (2 servers) and an Exchange 2003 clustered BE (2 nodes). I have installed a 2 node Exchange 2010 HUB/CAS array and 2 Exchange 2010 MBX servers in a DAG. Mail DOES flow from Exchange 2003 to Exchange 2010 although Delivery Receipts are not received. The Exchange 2010 environment is not in production yet. The Legacy configuration has not been enabled as yet.

    I have been through copious blogs and notes without success. I have disabled Anti Virus, disabled NIC TOE offload and numerous other Exchange related configuration - without success. The error that is displayed within the Queue viewer on CASHUB server states "451 4.4.0 Primary IP address responded with "421 4.4.2 Connection dropped due to socket error." Attempted to failover to alternate host but that did not succeed...."

    I'm beginning to think that there may be an issue with the NIC NLB configuration... Any assistance would be appreciated

     

    Tuesday, April 27, 2010 9:53 AM

Answers

  • Apologies for the tardy update. Scheduled downtime occurred and the configuration changes were successfully implemented. Creating an additional virtual SMTP server on each of the two FE Exchange servers, listening on a dedicated IP resulted in an inconsistent state with mail not flowing as expected. The solution that best resolved the issue was to remove the Windows NLB from the FE Exchange servers and have our firewall handle the NLB. Each FE Exchange server is now only managing ONE virtual SMTP server and listening on its Primary IP. Mail now flows from Exchange 2010 to Exchange 2003 and externally with no further issues experienced.

    Thanks for the support and input. Appreciated.

    • Marked as answer by Desertonian Sunday, May 30, 2010 7:07 AM
    Sunday, May 30, 2010 6:58 AM

All replies

  • Hi there,

    Do you have any routing group connector?

    I suggest you do a connectivity test with Exchange Best Practice Analyser (EXBPA)!


    ftornell
    • Edited by [zid] Tuesday, April 27, 2010 12:53 PM
    Tuesday, April 27, 2010 12:21 PM
  • Kindly Run the cmdlet to check the Routing Group Connectors from Exchnage 2003 to Exchange 2010 Default Routing Group.

    http://technet.microsoft.com/en-us/library/aa996924.aspx

    If The InterORG Routing Group Connector is not present than use

    http://technet.microsoft.com/en-us/library/aa997292.aspx

    Regards


    Fazal Muhammad Khan | MCT, MCSE, MCSA, MCTS | Infrastructure Consultant, Technology Services | CDC Pakistan Ltd. | https://fazalmkhan.spaces.live.com | OFFICE: +92 21 111 111 500 Ext: 1402 | +5 GMT
    Tuesday, April 27, 2010 12:51 PM
  • I had previously removed the single RGC and created a bi-directional connector for both feex servers and both hub servers. In an effort to determine why mail was flowing from Exchange 2003 to Exchange 2010 without a problem I removed the newly created bi-directional connectors and created two separate connectors in a one way direction. See below. Mail still does NOT flow from Exchange 2010 to Exchange 2003...

    [PS] C:\Windows\system32>Get-RoutingGroupConnector |fl
    [PS] C:\Windows\system32>New-RoutingGroupConnector

    cmdlet New-RoutingGroupConnector at command pipeline position 1
    Supply values for the following parameters:
    Name: CASHUB2FEEX
    SourceTransportServers[0]: nzk-cashub-cl1
    SourceTransportServers[1]: nzk-cashub-cl2
    SourceTransportServers[2]:
    TargetTransportServers[0]: nzk-feex-3
    TargetTransportServers[1]: nzk-feex-4
    TargetTransportServers[2]:

    Name                      SourceRoutingGroup                             TargetRoutingGroup
    ----                      ------------------                             ------------------
    CASHUB2FEEX               Exchange Routing Group (DWBGZMFD01QNBJR)       First Routing Group


    [PS] C:\Windows\system32>New-RoutingGroupConnector

    cmdlet New-RoutingGroupConnector at command pipeline position 1
    Supply values for the following parameters:
    Name: FEEX2CASHUB
    SourceTransportServers[0]: nzk-feex-3
    SourceTransportServers[1]: nzk-feex-4
    SourceTransportServers[2]:
    TargetTransportServers[0]: nzk-cashub-cl1
    TargetTransportServers[1]: nzk-cashub-cl2
    TargetTransportServers[2]:

    Name                      SourceRoutingGroup                             TargetRoutingGroup
    ----                      ------------------                             ------------------
    FEEX2CASHUB               First Routing Group                            Exchange Routing Group (DWBGZMFD01QNBJR)


    [PS] C:\Windows\system32>Get-RoutingGroupConnector |fl


    RunspaceId                   : 9a3c1309-5932-4fb5-bb34-08a471bfee64
    TargetRoutingGroup           : First Routing Group
    Cost                         : 1
    TargetTransportServers       : {NZK-FEEX-4, NZK-FEEX-3}
    ExchangeLegacyDN             : /o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Conn
                                   ections/cn=CASHUB2FEEX
    PublicFolderReferralsEnabled : True
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {NZK-CASHUB-CL2, NZK-CASHUB-CL1}
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : NZK-CASHUB-CL1
    MaxMessageSize               : unlimited
    AdminDisplayName             :
    ExchangeVersion              : 0.1 (8.0.535.0)
    Name                         : CASHUB2FEEX
    DistinguishedName            : CN=CASHUB2FEEX,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Gro
                                   ups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Domain
                                   ,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com
    Identity                     : CASHUB2FEEX
    Guid                         : 09b4255f-1e6e-4492-bc40-9ffe8788997b
    ObjectCategory               : Domain.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
    ObjectClass                  : {top, msExchConnector, msExchRoutingGroupConnector}
    WhenChanged                  : 4/27/2010 3:12:46 PM
    WhenCreated                  : 4/27/2010 3:12:46 PM
    WhenChangedUTC               : 4/27/2010 12:12:46 PM
    WhenCreatedUTC               : 4/27/2010 12:12:46 PM
    OrganizationId               :
    OriginatingServer            : nzk-ad-2.Domain.com
    IsValid                      : True

    RunspaceId                   : 9a3c1309-5932-4fb5-bb34-08a471bfee64
    TargetRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    Cost                         : 1
    TargetTransportServers       : {NZK-CASHUB-CL2, NZK-CASHUB-CL1}
    ExchangeLegacyDN             : /o=Domain/ou=First Administrative Group/cn=Configuration/cn=Connections/cn=FEEX2CASHU
                                   B
    PublicFolderReferralsEnabled : True
    SourceRoutingGroup           : First Routing Group
    SourceTransportServers       : {NZK-FEEX-4, NZK-FEEX-3}
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : NZK-FEEX-3
    MaxMessageSize               : unlimited
    AdminDisplayName             :
    ExchangeVersion              : 0.1 (8.0.535.0)
    Name                         : FEEX2CASHUB
    DistinguishedName            : CN=FEEX2CASHUB,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administ
                                   rative Group,CN=Administrative Groups,CN=Domain,CN=Microsoft Exchange,CN=Services,CN=
                                   Configuration,DC=Domain,DC=com
    Identity                     : FEEX2CASHUB
    Guid                         : 48af435a-0e0d-4744-a327-8bef6c061ec6
    ObjectCategory               : Domain.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
    ObjectClass                  : {top, msExchConnector, msExchRoutingGroupConnector}
    WhenChanged                  : 4/27/2010 3:13:50 PM
    WhenCreated                  : 4/27/2010 3:13:50 PM
    WhenChangedUTC               : 4/27/2010 12:13:50 PM
    WhenCreatedUTC               : 4/27/2010 12:13:50 PM
    OrganizationId               :
    OriginatingServer            : nzk-ad-2.Domain.com
    IsValid                      : True

    Tuesday, April 27, 2010 1:33 PM
  • The underlying issue has been identified. Our FE Exchange 2003 consists of 2 nodes, each with 2 Virtual SMTP servers. These servers are listening on their VIP addresses as opposed to their Primary IP addresses. So, we willl create an additional Virtual SMTP server for each FE node pointing to the node's Primary IP. Feedback to follow after scheduled downtime

    Wednesday, April 28, 2010 7:19 AM
  • Nice to hear that the issue has been understood.

    Kindly Update us on the Feedback of the Issue being working so that it can be helpful for others as well

    Regards


    Fazal Muhammad Khan | MCT, MCSE, MCSA, MCTS | Infrastructure Consultant, Technology Services | CDC Pakistan Ltd. | https://fazalmkhan.spaces.live.com | OFFICE: +92 21 111 111 500 Ext: 1402 | +5 GMT
    Wednesday, April 28, 2010 10:50 AM
  • Kindly mark teh post as Answered so that it can be helpful for others as well

    regards


    Fazal Muhammad Khan | MCT, MCSE, MCSA, MCTS | Infrastructure Consultant, Technology Services | CDC Pakistan Ltd. | https://fazalmkhan.spaces.live.com | OFFICE: +92 21 111 111 500 Ext: 1402 | +5 GMT
    Friday, May 14, 2010 5:44 AM
  • Apologies for the tardy update. Scheduled downtime occurred and the configuration changes were successfully implemented. Creating an additional virtual SMTP server on each of the two FE Exchange servers, listening on a dedicated IP resulted in an inconsistent state with mail not flowing as expected. The solution that best resolved the issue was to remove the Windows NLB from the FE Exchange servers and have our firewall handle the NLB. Each FE Exchange server is now only managing ONE virtual SMTP server and listening on its Primary IP. Mail now flows from Exchange 2010 to Exchange 2003 and externally with no further issues experienced.

    Thanks for the support and input. Appreciated.

    • Marked as answer by Desertonian Sunday, May 30, 2010 7:07 AM
    Sunday, May 30, 2010 6:58 AM