locked
Configure Send Connectors created by Edge RRS feed

  • Question

  • Hi mates,

    I tell you, I have the next platform of Exchange:

    Exchange CCR with 2Mailbox servers
    2 Servers with Client Access role and transport hub in NLB

    1 Edge in DMZ

    Once installed, the Edge, has carried out a subscription and are generated automatically send the two Connectors:

    - Edgesync - inbound to business
    - Edgesync - business to internet

    Hubtransport properly synchronized with both Edge and everything seems ok.

    Now comes my question. These two send Connectors they work? I understand that the inbound connector to send business, send connector is used to deliver both e hubtransport the edge, and then the edge connector uses the company to send internet, to get the emails out. It's so?

    If so, I raised another question, the configuration of these two send Connectors, should be left as they are created by the edge you?? I understand that, as I see that for the inbound connector to company, part of the network I have selected Route Through the Following mail hosts smart, smart host and I have - which is the configuration I created the edge . Here I have to remove him -- and put my two servers hubtransport? Or is it in the Source tab connector, which currently I have as source the server connector Edge, where I have to remove it and put the two hubtransport??
     
     
    Thank you very much in advance.

    Monday, December 19, 2011 8:42 AM

All replies

  • Hi,

    The subscription process creates two send connectors:

    • from the Exchange organization to the internet
    • from the Edge to the Exchange organization

    This should be enough to send/receive mail from and to the internet. It is advised to make no big changes to the connectors as it should work when the Edge Subscription has been made succesfull.

    Regards,

    Johan

     


    Exchange-blog: www.johanveldhuis.nl
    Monday, December 19, 2011 10:59 AM
  • Thanks for reply Johan,

    The problem is that I have mounted an Exchange 2007 organization. In the Exchange organization, Exchange reside two platforms, one for domainA.com dns suffix and another for dns suffix domainB.com.
    In domainA.com we have:
    A CCR Mailbox servers with 2
    2 servers in NLB hubtransport

    In domainB.com we have:
    A CCR Mailbox servers with 2
    2 servers in NLB hubtransport
    1 Server with Edge in DMZ

    The connectors are send to the organization and I have a connector for domainA.com send to send to the internet, and send the two connectors domainB.com generated by the Edge.

    The problem I have is that mail sent from domainB.com, reach the hubtransport of domainB.com and hence are sent to hubtransport of domainA.com and thence to the Internet.

    As I can do to make domainB.com mails are sent to the Edge and thence to the Internet, and mails out the domainA.com continue to send domainA.com connnector?

    Thank you very much.

    Monday, December 19, 2011 11:05 AM
  • The subscription process creates two send connector ..inblund and to the internet .its enough to send and receive emails ..
    Monday, December 19, 2011 11:10 AM
  • Yes jingoi,

    The problem, is in an other send connector created for send mails for domainA.com. All send emails, for domainA.com and domainB.com are sending for send connector for domainA.com.

     

    Monday, December 19, 2011 11:15 AM
  • Hi,

    OK now I understand your issue. What is defined as the source servers on the send connectors?

    Regards,

    Johan


    Exchange-blog: www.johanveldhuis.nl
    Monday, December 19, 2011 9:21 PM
  • Thanks for reply Johan,

    The source server configure in send connector for domainA are 2 hubtransport for DomainA

    The source server configure for two send connectors created by Edge is the Edge.

    I view a option in tab Address, one checkbox: Scoped Send connector.

    Microsoft say for this option:

    When Scoped Send connector is selected, the connector can only be used by Hub Transport servers in the same Active Directory site. When Scoped Send connector isn't selected, the connector can be used by all Hub Transport servers in the Exchange organization.

    If I mark this option in send connector for domainA, I guess my problem trick.

    Do you think?

    Tuesday, December 20, 2011 8:15 AM
  • Are those Exchange servers in a different AD site, if yes, then select the scopeed option as send connectors are global.
    Sukh
    Tuesday, December 20, 2011 12:19 PM