Slow propagation between front-end & back-end Exchange
Posted on 2007-10-10
We have the following set up:
Front End Exchange server (2003) that is on our DMZ, being NAT'ed from the public IP. We then have our back-end Exchange server. They are both fairly beefy boxes on a gigabit network.
The problem I am having is not that OWA is slow or even RPC over HTTP...the problem is with changes propagating between the two. Examples
1) Someone changes their network password - the change takes effect immediately for inside usage...however, for OWA & anything else on the front-end Exchange server (ie - Exchange ActiveSync), it takes several hours (sometimes up to 8)
2) We create a new user & within 2 minutes, their email-addresses are created depending on which Recipient Policy applies to them. If I send the mail from the inside, it works fine...however, if I send them an email from an outside source, it gets to the front-end server (which is our gateway) & gets rejected since it is an un-routeable address (not found in the recipient policy?). If I wait a day or so, it works.
3) Same general scenario, but if I add another email alias for someone (ie....first.last@domain in addition to email@example.com), it takes several hours before thos emails are accepted by the gateway.
Please, this cannot be normal. Let me know what I can do to diagnose the issues.
These are just some examples of slowness going through. Does anyone have any ideas?