none
Exchange 2010 & 2016 queues

    Question

  • Hoping you can help, we are migrating from Exchange 2010 to 2016 and setup a new Exchange 2016.

    Everything seems to be fine until I noticed that emails from external are being delivered to the new Exchange 2016 server but then getting stuck and will not deliver them to the mailboxes that are currently on the Exchange 2010 server.

    What am I missing?

    Friday, July 1, 2016 8:53 PM

Answers

  • What do you see in the SMTP queues?

    Did you ever make changes to the Default receive connector on the Exchange 2010 server?  The usual reason for what you're observing is that the Exchange servers can't send SMTP to each other and that's usually caused by misconfiguring the Default receive connector instead of creating a new connector for special purposes.

    Another problem could be the creation of a new receive connector that the Exchange server's traffic is routed through.  For example, the new receive connector might have a RemoteIPRanges range that includes the new server so that its SMTP traffic isn't handled by the Default receive connector.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Saturday, July 2, 2016 12:37 AM
    Moderator

All replies

  • What do you see in the SMTP queues?

    Did you ever make changes to the Default receive connector on the Exchange 2010 server?  The usual reason for what you're observing is that the Exchange servers can't send SMTP to each other and that's usually caused by misconfiguring the Default receive connector instead of creating a new connector for special purposes.

    Another problem could be the creation of a new receive connector that the Exchange server's traffic is routed through.  For example, the new receive connector might have a RemoteIPRanges range that includes the new server so that its SMTP traffic isn't handled by the Default receive connector.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Saturday, July 2, 2016 12:37 AM
    Moderator
  • Thanks for the tip, spent hours going through the configuration of the new server and it turned out to be an issue on the old one. The IP address of the new Exchange 2016 server must have been used in the past for a server or device as its address was a member of a custom Receive Connector used for anonymous connections.

    Once I removed the IP address for the Receive Connector the emails were delivered immediately. 

    Saturday, July 2, 2016 5:51 PM
  • You're welcome, happy to have helped.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Saturday, July 2, 2016 8:39 PM
    Moderator