Installed new Exchange 2016 mailbox server into 2010 environment w/2010 Edge. Test account from 2016 will not send/receive externally.

Ponleu Sisowath 196 Reputation points
2020-10-23T16:01:24.467+00:00

I recently completed an installation of Exchange 2016 mailbox server into an Exchange 2010 environment, which includes one 2010 mailbox server and one 2010 Edge Transport server.

I created a test account on the 2016 database and tested the send/receive connectivity. I was able to send internally, but for external mail, it's hangs in the queue. Error below.

------------------------------------------------------------------------------

Diagnostic information for administrators:
Generating server: Exchange2016.domain.local
Receiving server: edgesync - default-first-site-name to internet (2xx.xx.xx.xx)
example@Stuff .com
Server at edgesync - default-first-site-name to internet (2xx.xx.xx.xx) returned '400 4.4.7 Message delayed'
10/21/2020 10:43:36 AM - Server at edgesync - default-first-site-name to internet (2xx.xx.xx.xx) returned '451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect -> SocketTimedout: Socket error code 10060'
Original message headers:
Received: from Exchange2016.domain.local (192.168.xx.xxx) by
Exchange2016.domain.local (192.168.xx.xxx) with Microsoft SMTP Server
(version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id
15.1.2106.2; Wed, 21 Oct 2020 02:46:10 -0400
Received: from Exchange2016.domain.local ([::1]) by
Exchange2016.domain.local ([::1]) with mapi id 15.01.2106.002; Wed, 21
Oct 2020 02:46:10 -0400

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,284 questions
Excel Management
Excel Management
Excel: A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.Management: The act or process of organizing, handling, directing or controlling something.
1,627 questions
0 comments No comments
{count} votes

Accepted answer
  1. Ponleu Sisowath 196 Reputation points
    2020-11-10T22:02:50.33+00:00

    The Resolution:

    So I followed everyone's advice to resubscribe the Edge Subscription and so I did, using the Edge 2010 and Exchange 2010 mailbox. Tested it and got the same error. This is not to say that this wasn't required, it very well may have, it's just that I also needed to create a Firewall rule to allow the Exchange 2016 mailbox server to see the Edge 2010 and vice versa. Once the bidirectional FW rule was enabled, I was able to send/receive to external recipients using a test mailbox from the Exchange 2016 mailbox server. Thank you all for your assistance and expertise.

    Paul S.

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Andy David - MVP 139.8K Reputation points MVP
    2020-10-23T16:13:17.16+00:00

    You have to re-subscribe an Edge Subscription whenever you add or remove Mailbox servers in the AD site.
    https://learn.microsoft.com/en-us/exchange/architecture/edge-transport-servers/edge-subscriptions?view=exchserver-2019

    Also, I would suggest following the docs and bring up an Exchange 2016 Edge and subscribe that

    https://practical365.com/exchange-server/exchange-server-2016-migration-mail-flow-cutover/

    1 person found this answer helpful.

  2. Lydia Zhou - MSFT 2,371 Reputation points Microsoft Employee
    2020-10-26T02:21:50.657+00:00

    @Ponleu Sisowath

    Agree with AndyDavid. When we add a Mailbox server, the new Mailbox server doesn't automatically participate in EdgeSync synchronization. So we have to resubscribe the Edge Transport server to AD. For your reference: Add or Remove a Mailbox server.

    If you have any questions or need further help on this issue, please feel free to post back.


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

  3. Wiegmann, Niklas 11 Reputation points
    2020-10-27T14:14:55.75+00:00

    Hi,

    just found your articel becuase I came to the same problem.

    I re subscribed and mail flow is working from the new mailboxserver 2016 aswell.

    however wenn I run test-edgesubscription on the old 2010 mailboxserver it states failed.
    when I run test-edgsubscription on the new 2016server it states successfully.

    Is this normal behavior in 2010/2016 mix?

    1 person found this answer helpful.