locked
How to config receive connectors in mail flow with 2 NICs and different IP network RRS feed

  • Question

  • We have installed the Exchange Server 2016 on Windows Server 2016, and installed 2 NICs (Network Interface Card).
    This Exchange Server run for local mail only, not connected to the internet.

    NIC 1 with IP Network 10.254.1.0 and 10.254.3.0
    NIC 2 with IP Network 10.254.2.0

    the primary IP is 10.254.1.x

    How to configure receive connectors in mail flow with these different IP network (with two NICs) ?

    Does need to add these IP Network to the receive connectors (HubTransport), so all client can send and receive mail each others.


    • Edited by n70n1 Wednesday, October 18, 2017 10:10 AM
    Wednesday, October 18, 2017 10:06 AM

Answers

  • We have installed the Exchange Server 2016 on Windows Server 2016, and installed 2 NICs (Network Interface Card).
    This Exchange Server run for local mail only, not connected to the internet.

    NIC 1 with IP Network 10.254.1.0 and 10.254.3.0
    NIC 2 with IP Network 10.254.2.0

    the primary IP is 10.254.1.x

    How to configure receive connectors in mail flow with these different IP network (with two NICs) ?

    Does need to add these IP Network to the receive connectors (HubTransport), so all client can send and receive mail each others.



    WHy the need to do this? Seems like a bad idea.
    • Marked as answer by Andy DavidMVP Thursday, November 2, 2017 10:50 AM
    Wednesday, October 18, 2017 11:54 AM
  • Hi,

    Thanks for contacting our forum.

    There is no need to configure Receive Connectors for internal mail flow on one server. 

    The server has only one routing table and it is not per NIC. It’s not recommended to use two NICs.

    Hope it helps.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Jason.Chao Monday, October 23, 2017 9:36 AM
    • Marked as answer by Andy DavidMVP Thursday, November 2, 2017 10:50 AM
    Thursday, October 19, 2017 6:39 AM

All replies

  • We have installed the Exchange Server 2016 on Windows Server 2016, and installed 2 NICs (Network Interface Card).
    This Exchange Server run for local mail only, not connected to the internet.

    NIC 1 with IP Network 10.254.1.0 and 10.254.3.0
    NIC 2 with IP Network 10.254.2.0

    the primary IP is 10.254.1.x

    How to configure receive connectors in mail flow with these different IP network (with two NICs) ?

    Does need to add these IP Network to the receive connectors (HubTransport), so all client can send and receive mail each others.



    WHy the need to do this? Seems like a bad idea.
    • Marked as answer by Andy DavidMVP Thursday, November 2, 2017 10:50 AM
    Wednesday, October 18, 2017 11:54 AM
  • Hi Andy David,

    Because when the client on IP Network 10.254.2.x send email using Outlook 2013 and the the email stuck in draft and can't be send.

    but when we try using 1 NIC's, the email can be send or receive.

    Thursday, October 19, 2017 4:17 AM
  • Hi,

    Thanks for contacting our forum.

    There is no need to configure Receive Connectors for internal mail flow on one server. 

    The server has only one routing table and it is not per NIC. It’s not recommended to use two NICs.

    Hope it helps.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Jason.Chao Monday, October 23, 2017 9:36 AM
    • Marked as answer by Andy DavidMVP Thursday, November 2, 2017 10:50 AM
    Thursday, October 19, 2017 6:39 AM
  • Hi,

    I am currently standing by for further update from you and would like to know how things are going. Please check if the reply helps you, if it helps please help to mark as answer.

    Thanks for your time.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, November 1, 2017 9:34 AM