


The next thing to check is the Virtual Directories and fix them accordingly too. Then check your external DNS records and make sure and point to your external IP Address of your mail server. Then create another DNS Zone for and create a blank A record and point it to the internal IP Address of your mail server. The easiest way to do this is to create a DNS Zone for (assuming that is your OWA URL) and then create a blank A Record and point it to your internal IP Address for your mail server. Powershell Get-OutlookProvider | fl Get-OutlookAnywhere | flĪlso, make sure your OWA URL resolves externally to your external IP and resolves internally to your internal IP. In any case, I've had their tech's monitor several stations and they can't find a problem.Īnything that I should be trying and haven't, or if you have an idea please let me know. This is a pretty resource heavy system and removing the outlook add-in seemed to help the problem but was inconsistent across multiple users. I should note that I've only been here a few months and they added a Document Management System (Aderant Total Office) right when I came on. Users are on different switches so it doesn't seem like faulty hardware. Moved 5 of the worst users to a new mail store. I'm using outlook 2010 and exchange 2007 on a Server 2008 R2 box.

Event view logs the application event ID as 25 which isn't very helpful. It's very intermittent whereas it might not happen everyday but it does seem to generally happen to the same users and not others. It's usually only for a few moments and then it will work for a while. On several users I'm experiencing outlook losing connection to exchange several times throughout the day or being very sluggish.
