none
400 4.4.7 Message delayed and 441 4.4.1 Error encountered while communicating with primary target IP address

    Question

  • Hi,

    After shutting down the old Exchange server 2010 (Internal IP 115.135.55.10) in my data center, now I cannot send email to one of the important recipients in my group of companies:

    Generating server: PRDEX24-VM.domain.com
    Receiving server: [115.135.55.229] (115.135.55.229)
    Banking@ParentCo.com
    Remote Server at [115.135.55.229] (115.135.55.229) returned '400 4.4.7 Message delayed'
    20/06/2018 8:45:40 PM - Remote Server at [115.135.55.229] (115.135.55.229) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060, Win32 error code: 10060." 
    Attempted failover to alternate host, but that did not succeed. 
    Either there are no alternate hosts, or delivery failed to all alternate hosts. 
    The last endpoint attempted was 115.135.55.229:25'


    The above is the NDR that I got when my customer and also myself from free webmail sending email to Banking@ParentCo.com.

    PRDEX02-VM.domain.com is the existing Exchange Server 2013 where both domain.com and ParentCo.com are listed as the Authoritative Accepted email domain.

    Usually, the email that is delivered to Banking@ParentCo.com is delivered to another Application server (Mainframe with the IP 115.135.55.229) through the Exchange server 2013.

    How to fix the issue with the NDR above from external sender?


    /* Server Support Specialist */

    Wednesday, June 20, 2018 10:47 AM

All replies

  • I'm sure I've told you this before, /* Server Support Specialist */ Senior System Engineer.

    Never just "turn off" an Exchange server unless you want things to break.  Exchange expects all servers in the organization to be up and won't check if they're down before trying to use them.  If you don't want the server to be up, uninstall it.


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

    Wednesday, June 20, 2018 5:59 PM
    Moderator
  • I'm sure I've told you this before, /* Server Support Specialist */ Senior System Engineer.

    Never just "turn off" an Exchange server unless you want things to break.  Exchange expects all servers in the organization to be up and won't check if they're down before trying to use them.  If you don't want the server to be up, uninstall it.


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

    Hi Ed,

    yes, but this is the only way to test what could be breaking when decommissioning the old Exchange Server.

    How to interpret that error message?


    /* Server Support Specialist */

    Wednesday, June 20, 2018 11:39 PM
  • Hi,

    Things I want to confirm with you:

    Your existing server is "PRDEX02-VM". What is the "PRDEX24-VM", the server that you shut down?

    What do you mean about "send email to one of the important recipients in my group of companies"?  Do you mean use a Exchange 2013 mailbox send mail to  Banking@ParentCo.com(a mailbox in other domain).

    If you send mails internally, where this issue occur?

     Regards, 

    Kyle Xu


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

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, June 21, 2018 8:35 AM
    Moderator
  • That error message says that you turned off an Exchange server, which is what you did and what I've repeatedly told you not to do.

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

    Friday, June 22, 2018 2:14 PM
    Moderator
  • That error message says that you turned off an Exchange server, which is what you did and what I've repeatedly told you not to do.

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


    Hm, so in this case, I’ll try to uninstall the Exchange 2010 from Add/Remove programs. Hopefully the error goes away.

    /* Server Support Specialist */

    Friday, June 22, 2018 2:20 PM
  • I would use the command line.  For Exchange 2010:

    C:
    CD "\Program Files\Microsoft\Exchange Server\V14\bin"
    setup.com /mode:uninstall


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

    Friday, June 22, 2018 2:28 PM
    Moderator