Getting Error LED=441 4.4.1 | Exchange Server 2013

Syed Fazal Hassan 20 Reputation points
2023-11-10T11:26:36.8766667+00:00

Hello Experts,

I am unable to send emails outside the organization. However, I am receiving emails from all and inside communication incoming and outgoing is working fine too.

November 10, 2023 12:24:48 PM" orient-power.com DnsConnectorDelivery Connecting 1   "

 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 };{FQDN=};{IP=}]" "Friday, November 10, 2023 12:24:32 PM"

Screenshot_1.png

We are running Exchange Server 2013 Service Pack 1 (SP1 aka CU4) 15.0.847.32

DNS is running from Windows Server and in properties I only have DNS IP of the DC server, no other IPV4 or IPV6 entry is enabled. However, the forwarder tab in DNS properties is empty and there was no entry before and exchange was working fine.

I am able to ping MXs of all affected domains but emails don't go out. I have tried restarting the transport service but that didn't work.
 

Apologies, If I missed any details. Let me know what else I can provide for better assistance.

An urgent help is much appreciated.

Thank you.

Exchange | Exchange Server | Other
Windows for business | Windows Server | User experience | Other
Exchange | Other
{count} votes

Accepted answer
  1. Anonymous
    2023-11-13T08:42:00.4333333+00:00

    Hello @Syed Fazal Hassan ,

    Based on your error message, I would like to confirm with you whether you have made any changes to the server recently? It is recommended that you first test the connection to the remote SMTP server using telnet on port 25 to ensure that port 25 is not blocked or filtered by the firewall or ISP, as it may be that your ISP blocks the port. Here are some similar cases for your reference: https://techcommunity.microsoft.com/t5/exchange/444-4-4-1-error/m-p/3278252 https://thesysadminchannel.com/solved-exchange-failed-to-connect-winsock-error-code-10060-win32-error-code-10060/(Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)
    In addition, for further troubleshooting, could you provide the output of using ipconfig /all on the Exchange Server?


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.