Outlook randomly disconnects from Exchange in Terminal Server


Terminal Server = 08R2
Outlook 2010 Pro = All MS updates current
Exchange 2010 on same subnet
30 TS Users

A couple of users (one more than the other) randomly looses connectivity with Exchange in their Terminal Server session.  "Disconnected" shows in the bottom of the Outlook window.  Sometimes the user can close and open Outlook and it re-establishes, other times not.  Sometimes user can logoff/logon session and it re-establishes and other times not.

Every time it has happened, we have been able to successfully ping exchange, the DC and any additional suspect resources successfully.  Outlook Connection Status show an active connection and reconnect goes through successfully but Outlook remains disconnected and no mail will flow in or out of the mailbox.  Exchange properties for the user look fine.  Event logs on Exchange nor TS show anything relevant.

Since the issue started we have deleted and recreated the users outlook profile, reset the user account in AD, moved the user to a second 08R2 Terminal Server.  All to no avail.  


About 1 year ago the site was upgraded from SBS 2003 to 08R2 for AD and Exchange 2010.  The upgrade went fairly smooth with minor bumps, but nothing directly exchange specific.  Considering the troubleshooting we have done on the user end, I suspect this issue is Exchange specific but I cannot put my finger on what, or why it is only effecting 2 users randomly.

Any thoughts are greatly appreciated.
Who is Participating?
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.

Run an online mailbox repair request on the user, or database.

To run a repair on the entire database (replace "Mailbox Database 1234567890" with your actual Mailbox Database Name:
New-MailboxRepairRequest -Database "Mailbox Database 1234567890" -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

Open in new window

To run the repair on only the user mailbox, use this command (replace "bart@example.com" with the users mailbox name):
New-MailboxRepairRequest -Mailbox bart@example.com -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

Open in new window

Remember: These are ONLINE repairs, so there is no need to take your database offline like you did in previous versions of MS Exchange.  You can run these during production - however, you may wish to run them after-hours if you're concerned about performance impact.

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

Is there something in front of your CAS servers, like a hardware load balancer? If this is the case start there.

Here is a link that describes the general steps for troubleshooting outlook connectivity issues:

ssiremoteAuthor Commented:
Thanks for the feedback.  Testing the mailbox repairs today (been out of office).   There is nothing in front of the CAS.  Also reading through the blog notes.  Will update asap.
ssiremoteAuthor Commented:
Thank You, Problem solved. keeping fingers crossed.
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

From novice to tech pro — start learning today.