Outlook 2010, Exchange 2010, Windows 2008R2 Recently our Exchange stopped updating users' inbox folders. They will only receive email in bunches every 5 or 6 hours or after they click Update Folder in Outlook. The only thing I am aware of that changed was I demoted a domain controller that Exhcange had been aware of. Any idea why Exchange has stopped updating inboxes when mail is received?

Changing the domain controller shouldn't have caused the problem. Did you restart the Exchange services afterwards? The primary reason for this is something blocking the traffic. The way that Outlook/Exchange communicate is that Exchange sends a packet to Outlook to say that something has changed, and then Outlook goes and checks the mailbox. If that packet has been blocked for some reason, then Outlook just sits there. Changing the folder forces Outlook to query the mailbox. Usual reason for this is a firewall or antivirus product with a firewall built in. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

I haven't made any changes to our antivirus and I wasn't having these problems up until a couple weeks ago. I did install a new firewall but as our exchange is local and the users are local I'm not sure how the firewall would block internal communications. I've been getting these warnings. Are they anything to be worried about: Process Microsoft.Exchange.RpcClientAccess.Service.exe (PID=3964). Configuration object CN=SMTP (LLC3-{88120695-204E-4ABE-A753-BF5C7A3EC5A4}),CN=Connections,CN=LLC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LLC,DC=LOCAL read from Server1.LLC.LOCAL failed validation and will be excluded from the result set. Set event logging level for Validation category to Expert to get additional events about each failure. Reconcilation of catalog for database Mailbox Database 1166977053 revealed that 1 mailboxes had to be reconciled. An attempt was made to re-index items missing in the catalog. The next line shows order of fields appearing in the following reconcile results. Inbound authentication failed with error LogonDenied for Receive connector Default SERVER3. The authentication mechanism is Login. The source IP address of the client who tried to authenticate to Microsoft Exchange is

None of those errors have anything to do with clients connecting to the Exchange, those look like SMTP errors. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi, You need to check whether there is 9646 error in the event logs: If users opened multiple shared mailboxes, the outlook client may open more than the default value of the server objects in outlook cache mode, server prevents MAPI client to access server from exhausting resources on the Exchange server, so we may see similar issue and items may be delayed or cannot update to OST. If we cache many cached mailboxes, OST will be increase fast as well. ThanksSophia Xu

Exchange has to notify the client about new email then only client can fetch the new e-mail. But in your case that notification is not happening. Check to see the devices involved between the client and the server. Do you have outlook installed on Exchange server ? Is it possible to have it ? (As it is now supported by microsoft). The reson is, it will narrow down the problem to either the network bond or the component on the exchange responsible for notifying the client.Jasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP:Exchange 2010 | Exchange 2007 | MCTS:OCS 2007 | Exchange 2010 | Exchange 2007 | MCSA:Messaging | Security | MCSE:Messaging | Security | MCP

The problem resolved itself when I manually entered the domain controller into system configuration.