MS Exchange 2013 intermittent delivery delays using primary and back Exchange servers

We just migrated to new servers in a Server 2012 and Exchange 2013 environment running the Office 2010 Outlook client as well as the 2013 Exchange OWA.   Using Queue Viewer I can see messages moving through the "Mail1" server. When I connect to the "Mail2" backup server, that queue is backlogged at the times when we know we have a problem.  We start/stop the transport service and the MAIL2 queue clears.

Sometimes when we first access the Queue Viewer we get the message "The remote pipeline has been stopped...".

Any suggestions on where we might look to see what is stopping the transport to avoid the manual stop/start?
jmalinowskiAsked:
Who is Participating?
 
jmalinowskiAuthor Commented:
Hats off to "VB ITS" as that solution pointed us in the right direction to resolve the problem.

We had configured the mail servers to use Network Adapter DNS lookups (found in Exchange Admin Center under "servers" option). We changed the DNS option from "all network adapters" to "custom settings" and added our DNS server IP addresses.

This appears to have resolved the problem of mail delivery latency and the transports not forwarding mail.

Thanks for your recommendation and for demonstrating the value of the Experts Exchange service. We consider this incident closed.
0
 
VB ITSSpecialist ConsultantCommented:
I'd look at DNS on the Mail2 server firstly. Also check that there's sufficient free disk space on the server.
0
 
jmalinowskiAuthor Commented:
Will check DNS, ample disk space available as we're fortunate these are new servers. CU6 is applied to the servers.
0
 
VB ITSSpecialist ConsultantCommented:
Glad I could help!
0
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.

All Courses

From novice to tech pro — start learning today.