Edge Transport: Incoming mails stuck in the queue with error 4.4.1
Today while configuring an Edge transport, I got the below error. I am sharing the resolution to help others.
Issue:
Incoming mails are queuing up Delivery to Mailbox queue to deliver in the database in a IPLess DAG.
Get-queue is showing the following error
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 2002:b00:5::b00:5:475};{FQDN=dagdb01};{IP=2002:b00:5::b00:5}]
Point to be noted 2002:b00:5::b00:5:475};{FQDN=dagdb01};{IP=2002:b00:5::b00:5}]
This is IP version 6 addresses which are not accepting the mails.
Resolution:
-Opened the DNS and verified the IP belongs to Exchange server W12R2E1.
-Removed IPv6 DNS entries
-Opened the Registry and disabled IPv6 by all FFFFFFFF. Restarted the exchange server.
-Now mail started delivering.
Prabhat Nigam
Microsoft MVP | Exchange Server
Team@MSExchangeGuru
January 20th, 2015 at 3:44 pm
Prabhat,
You are a legend!..Keep up the good work.
January 25th, 2015 at 9:18 pm
[…] Edge Transport: Incoming mails stuck in the queue with error 4.4.1 – […]
January 25th, 2015 at 9:30 pm
[…] Edge Transport: Incoming mails stuck in the queue with error 4.4.1 – […]
May 20th, 2016 at 4:47 pm
Excellent ….