Exchange sending/receiving for some people and not for others

Env:
3x Exchange 2010, all running Windows Server 2008 R2 DataCenter


Emails in exchange appear to be being delayed or not being sent, I open the queue viewer and all the emails are getting stuck there with the status of 'Ready' and it just sits there waiting to send. I am not particularly knowledgeable with exchange so any help would be appreciated...

The emails are not sending/receiving from some people but then other users are sending/receiving them fine (it all appears to be internal but i could be wrong..)

If I restart the server then the emails are then released and it clears the queue..

If I restart exchsrv1 then it clears the queue and emails are sent, then 20 minutes later emails start to grow on exchsrv2 and if i reboot that, it then goes back to exchsrv1 again..

any ideas, or if you need any further information then please let me know

Many thanks
TomAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
What do the application logs say on those Exchange servers? Does this happen for both internal and external emails?

Check your send and receive connectors to ensure that the proper permissions groups are associated.

Will.
TomAuthor Commented:
When I go into the send connectors within Organization config > hub transport > send connectors, it said "force close" on exchsrv1 and exchsrv2, but if i refresh it then shows them and appears that they're enabled... Now it's not giving me force close any longer but emails are still piling up in the queue viewer.

The receive connectors seem to be ok with status 'Enabled'

From what I can see, it appears to be only internal emails which are stopped being sent and not external


The only warning I get in app log is:
Source servers belonging to different Active Directory sites were detected for connector 'CN=## Outbound,CN=Connections,CN=Exchange Routing Group (),CN=Routing Groups,CN=Exchange Administrative Group (),CN=Administrative Groups,CN=##,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=##,DC=org' in routing tables with timestamp 06/11/2015 15:58:57. Only the closest site will be used and load-balancing will be affected.
Will SzymkowskiSenior Solution ArchitectCommented:
So this is only affecting users that are sending internally? If a user sends externally then the email is sent without any issues?

Where are they getting stuck in the queue? i.e. submission?

If this is only affecting your internal mail flow check your default receive connectors on both exchange servers and verify the configuration. Also you said that it works if you reboot the server for about 20 minutes and then it stops again?

Can you isolate it to a specific server? Stop the Transport Service on one of Exchange servers holding the Hub Transport Roles and see if mail continues to flow.

Also what is your logging level set to? Might want to turn the on as well if it is not already.

Will.
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.

TomAuthor Commented:
All the emails appear to be stuck on Hub Version 14. I was wrong, it is internal and external messages being blocked

We have three exchange servers, first one built up a back log in the queue for Hub Version 14, then restart the server and it sends them all but then messages get directed to the second exchange server where it does the same thing, and then sends it to the third server etc etc etc.

Because it seems to be all servers i won't be able to isolate it to one server, i restarted the transport service but it just generated a lot of IIS errors, not sure what that meant but after restarting the server it didn't bring up any further errors..

The logging level is set to Low but mostly set to Lowest, is there anything specific you want me to increase to high, or should i set all of it to high? - Never had to change logging before..
TomAuthor Commented:
Just a bit more of information as it appears that this might be linked, ever since this DNS problem occurred, we also started having the problem with delayed emails.. We seem to have DNS entries disappearing, one day we can ping fileserver2 and then the following day we can't, we then check DNS and the entry for that server is no longer there!

just happened to one of the exchange servers so we put it back and it appears that it may have resolved the issue..
Will SzymkowskiSenior Solution ArchitectCommented:
Very weird, might want to check your scavenging settings for DNS.

Will.
TomAuthor Commented:
Scavenge stale resource records is not ticked, should it be?
Capture.PNG
Will SzymkowskiSenior Solution ArchitectCommented:
Scavenging is not enabled by defualt to having it unchecked is correct. I thought if it was enabled might be the reason for deleting those records.

Will.
TomAuthor Commented:
Appears to have been a DNS issue, one of the DNS records were missing but i haven't found out why the record suddenly disappeared, thanks for the help Will.


Strange it was a DNS issue since it could still resolve/send some emails but not all, but appears to be working now at least.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TomAuthor Commented:
Trouble shooting led to discovering it was a DNS issue.

A and PTR record was missing from one of our DNS servers, once put back in it decides to send properly
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.