none
Edge Transport & Exchange 2013

    Question

  • Hello everyone,

    I have installed Exchange 2013 successfully (Mailbox & Client Access Roles). The 2013 server is called "exchange".

    I also have a 2010 edge transport server called "exch-shield".

    I was able to successfully create the Edge transport XML file and import it to the 2013 server. 

    What I need assistance with, is creating the edge subscription in PowerShell (so mail goes out & comes in via the Edge transport server).

    The result of a Start-EdgeSynchronization is posted below as well:

    [PS] C:\Windows\system32>Start-EdgeSynchronization -Server exchange -ForceFullSync


    RunspaceId     : 8b685e08-7fae-43a6-89e1-aeffae682f8e
    Result         : Success
    Type           : Recipients
    Name           : exch-shield
    FailureDetails :
    StartUTC       : 29/12/2012 3:22:27 PM
    EndUTC         : 29/12/2012 3:22:27 PM
    Added          : 0
    Deleted        : 0
    Updated        : 1
    Scanned        : 10
    TargetScanned  : 0

    RunspaceId     : 8b685e08-7fae-43a6-89e1-aeffae682f8e
    Result         : Success
    Type           : Configuration
    Name           : exch-shield
    FailureDetails :
    StartUTC       : 29/12/2012 3:22:27 PM
    EndUTC         : 29/12/2012 3:22:28 PM
    Added          : 0
    Deleted        : 0
    Updated        : 1
    Scanned        : 12
    TargetScanned  : 0

    Saturday, December 29, 2012 3:43 PM

All replies

  • How did you do what you say you did?  Creating an edge subscription creates the necessary connectors unless you tell it not to, in which case you must create them manually.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Sunday, December 30, 2012 6:58 AM
    Moderator
  • How did you do what you say you did? 

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    I installed Exchange 2013 onto a Win Server 2012 domain member server. It has mailbox & Client access roles installed.

    The server name is "exchange".

    I installed AD Lightweight & populated the DNS suffix of a non-domain joined server.

    I installed Exchange 2010 onto it, and installed Edge Transport role.

    The server name is "exch-shield". Both servers can resolve each other by host name or IP address.

    I created a New-Edgesubscription XML file and imported it into the 2013 server with the following line of code: 

    New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeServerSubscription.xml" -Encoding Byte -ReadCount 0)) -Site "Default-First-Site-Name"

    The mail queue on the edge transport server fails in delivering mail with the following error:

    451 4.4.0 Error DNS query failed. This is unusual as both servers have the primary DNS server set as the Windows Server 2012 Domain controller.

    Tuesday, January 1, 2013 5:37 AM
  • Hi,

    You cannot send mails to the external domains? How about inbound mails?

    Please try to use Telnet to test the communication:

    Telnet to Port 25 to Test SMTP Communication

    http://support.microsoft.com/kb/153119?wa=wsignin1.0

    Hope the following similar post will be helpful:

    451 4.4.0 DNS Query Failed

    http://social.technet.microsoft.com/Forums/zh/exchange2010/thread/0d73a7ec-dbc2-4e21-bf6f-72637a2587d1


    Frank Wang
    TechNet Community Support

    Tuesday, January 1, 2013 1:12 PM
  • Hi,

    You cannot send mails to the external domains? How about inbound mails?

    I can send outbound mail if I disable the edge subscription and enable the SMTP send connector on the 2013 Exchange server (bypassing the edge transport server altogether).

    Inbound mail either:

    arrives at the edge transport server (and the 451 4.4.0 error prevents delivery to the 2013 mailbox & client access server)

    ~or~

    If I disable the inbound edge subscription & enable the 2013 receive connector (and forward the ports to the 2013 server instead of the edge transport server, mail successfully arrives at the 2013 server.

    Hope this makes sense :-S 

    Edit: Edge transport = Exchange 2010

     CAS & MBX = Exchange 2013

    Wednesday, January 2, 2013 3:02 AM
  • I know this was a while ago, but you can try installing CU1 on the Exchange 2013 and SP3 on the 2010 Edge server to see if that helps.

    For details, see the following topics:

    Cumulative Updates for Exchange 2013

    Upgrade from Exchange 2010 to Exchange 2013

    You configuration is supported: Exchange 2010 Edge on a non-domain joined server subscribed to an AD site that contains an Exchange 2013 CAS/Mailbox server.

    2007/2010 Edge is not 2013 CAS aware, so your inbound/outbound message delivery will completely ignore 2013 CAS. Mail flow would go Internet --> Edge --> Transport service on Mailbox role and vice-versa.

    Wednesday, April 10, 2013 10:35 PM