• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3019
  • Last Modified:

Exchange 2010 outgoing email errors

Hello,

I’m having the following problem :
I have a Windows 2003 as DC and a Windows 2008 STD server with Exchange 2010 installed as mail server.

We are having the problem that some messages get stuck in the Que with the following errors:
400 4.4.7 Message delayed
421 4.4.2 ns1.cnb.nl Error: timeout exceeded
421 4.4.2 Connection dropped due to SocketError
452 Internal error
451 4.4.0 Primary target IP address responded with: “421 mail.****.com Error: timeout exceeded. “ Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
451 4.4.0 Primary target IP address responded with: “421 4.4.2. Connection dropped due to SocketError “ Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
451 4.4.0 Primary target IP address responded with: “421 4.4.2. Connection dropped due to ConnectionReset “ Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
451 Timeout waiting for client input
451 Transaction failed
451 4.4.0 DNS query failed

It is not with all the messages that we send out just with random ones.
With some messages if i restart the Exchange Transport Service they will go out right away.
After usually a day the sender will get a error 550 4.4.7 QUEUE.Expired: message expired.

I am also getting some complaints about people when they are in the office and work in outlook it sometimes hangs / needs 15-45 sec to load. I don’t know if this has something to do with it.
0
tinus67
Asked:
tinus67
  • 3
1 Solution
 
tinus67Author Commented:
rajkr2020 thank you for the responce i will try to do that asap but i have to schedule it because the server will be needing a reboot. I will keep you posted.
0
 
tinus67Author Commented:
we figuerd it out the Cisco firewall was cauzing the problems in the network. Thanks for the help.
0
 
tinus67Author Commented:
we figuerd it out the Cisco firewall was cauzing the problems in the network. Thanks for the help.
0
 
raedmmhamdanCommented:
Dear tinus ,
I ave same problem and still suffering
Could u tell me what was the slution plz????
i appreciate ur fast response.
I have Juniper firewall.

Regards
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now