none
unable to send message internally from exchange 2013

    Question

  • Hi All,

    We have Single AD site where we have Datacenter 1 and Dtacenter 2.

    In DC 1 we have 2 Mailbox/CAs server and in DC 2 we have single CAS/MBX server.

    All server are member of DAG.

    Now the issue is internal mail flow working sometime , and sometime not working .

    When i check the mail queue it is shwoing below error message.

    LED=441 4.4.1 Error encountered while communicating
    with primary target IP address: "Failed to connect. Winsock error code 10061,
    Win32 error code 10061." Attempted failover to alternate host, but that did not
    succeed. Either

    All serers are multi role servers.

    DNS is properly configured, Network binding and ip config is perfect.

    All services are working fine. ABle to telnet and send the messges but message stuck in quest wiht same error message.

    ABle to send external message wihtout any issue.

    Thanks in advance

    Wednesday, May 18, 2016 7:52 PM

Answers

  • Is AV installed on the 2013 server?  Is there any firewall piece that could be causing a problem?

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

    • Marked as answer by Am230089 Thursday, May 19, 2016 8:05 PM
    Thursday, May 19, 2016 1:58 PM
  • It sounds like a network issue to me.

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

    • Marked as answer by Am230089 Thursday, May 19, 2016 8:05 PM
    Thursday, May 19, 2016 6:53 AM
    Moderator
  • Hi,

    Have you tried to restart the Exchange Transport Service when the issue occurred?

    In general,winsock error 10061 means that the server you are attempting to connect to is actively refusing the connection.Please telnet to port 25 to test.

    Please check if you can find some related logs when the issue happens.

    Also disable temporarily anti-virus or malware scanning on the exchange server, and see if that helps.

    Regards,

    David 


    Thursday, May 19, 2016 9:19 AM
    Moderator

All replies

  • It sounds like a network issue to me.

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

    • Marked as answer by Am230089 Thursday, May 19, 2016 8:05 PM
    Thursday, May 19, 2016 6:53 AM
    Moderator
  • Hi,

    Have you tried to restart the Exchange Transport Service when the issue occurred?

    In general,winsock error 10061 means that the server you are attempting to connect to is actively refusing the connection.Please telnet to port 25 to test.

    Please check if you can find some related logs when the issue happens.

    Also disable temporarily anti-virus or malware scanning on the exchange server, and see if that helps.

    Regards,

    David 


    Thursday, May 19, 2016 9:19 AM
    Moderator
  • Is AV installed on the 2013 server?  Is there any firewall piece that could be causing a problem?

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

    • Marked as answer by Am230089 Thursday, May 19, 2016 8:05 PM
    Thursday, May 19, 2016 1:58 PM
  • Thanks all for your reply.

    Issue has been automatically fix. May be there are some issue in network or other devices.

    Regards

    AM

    Thursday, May 19, 2016 8:07 PM