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

Exchange 2010 all messages getting stuck in queue with error 400 4.4.7

We had some power issues yesterday and while that normally wouldn't be an issue we are in the middle of changing our UPS equipment out. Needless to say servers we not powered down in a clean way. The exchange server came back up with the error that it had lost its trust relationship with the domain. I removed it from the domain and rejoined and that seems to bring email back up online.

Now this morning I am seeing that all of the outgoing messages to external domains are getting caught with the error above. Nothing has changed but i have a feeling it has to do with out send connector but I am not seeing any issues with it. Any help would be much appreciated.
Chris Christensen
Chris Christensen
  • 4
1 Solution
Can you check the event viewer for error events. Is you outbound email going through smarthost or DNS.
Please check internal emails.
Can you check your gateway/firewall is operational.
Run telnet mx1.hotmail.com 25 and check if you are able connect.
Also check if 25 port is open at firewall and ISP end.
Chris ChristensenNetwork AdministratorAuthor Commented:
Unable to telnet out, and email going through smarthost. I checked the outbound firewall rules and there is a rule allowing outbound 25 from internal to Any.

As far as event viewer goes, which logs should i be checking?
Chris ChristensenNetwork AdministratorAuthor Commented:
I am also getting this error every once in a while.

the remote pipeline has been stopped. it was running the command....
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Chris ChristensenNetwork AdministratorAuthor Commented:
Running mail flow analyzer got me a piece of info.

Invalid InternalDNSAdapterGuid setting found.
Simon Butler (Sembee)ConsultantCommented:
Have you set DNS servers on the Send Connector? If so, remove it and restart Transport.

Chris ChristensenNetwork AdministratorAuthor Commented:
Send connector some how was as singed to a nic that did not exist.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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