Hi everybody, I am facing one problem in exchange server. we have 3 site offices each with more than 1000 users and one corporate office. There are 2 Domain controllers in each office including corporate office. All theoffices are connected through WAN links with corporate office. And each office has one exchange server. We have set sending limit on user base. Depending on the level of the user, his limit is set to 1 MB to 6 MB. But sometimes some junior officers have to send some mails more than 1 MB. So we temporarily set his/her sending limit to 4-6 MB as required. Butthe problem is that if we have set new limit as 5 MB and then also user can't send any attachment more than 1 MB for 30 to 60 minutes. Sometimes user has to wait for 2 hours ..!!! When we were running exchange 5.5 server that time the new limit was in effect on the same moment. But now when we migrated to exchange server 2003, it takes this much time, we just can't understand. Can anybody please tell me what the problem could be...?? Thanking you all in advance... ;)

The sending limit is configured in Active Directory as an attribute to the user's account. If the changes are made ona DC in a differant site than their Exchange server you'll have to first wait for replication before the change will take effect. The fastest (and easiest) way to avoid this problem would probably be to point your MMC at a DC in the same site as their Exchange server, it will be slower for you making the change (since your management traffic would than be over the WAN) but will apply to their mailbox much faster. Give this a try, test how quick the change is applied and let us know. Regards,Erik

Thanks Erik, I have tried it first. And my local exchange server is always pointing to local DC only. I have tried connecting all DCs by ADUC snapin. But each timeit takes almost same time. kanti

How are you certain you're making the change on the same DC? Have you verified using ESM that this Exchange server is accessing this DC? Assuming this is correct you may have an Exchange directory access issue. Do you notice any other problems with AD changes taking a long time to "replicate" over to Exchange? Might be good to work through MSFT's understanding/troubleshooting guide on Exchange directory access:http://www.microsoft.com/technet/prodtechnol/exchange/2000/library/utda.mspx The article was written for 2000, but most of it is still applicable to 2003. Good luck, Erik

HI, I Have checked it in ESM under the receipient update services. My Exchange server is bound with my local DC only, I mean for my server it is showing Domain: my domain name, Exchange server: my exchange server name, Windows Domain Controller: my local DC and in Update interval : Always run. I run Dcdiag tools also and it is running successfully. Now what shoul I look into..?? Kanti

Hi, I too had experienced this issue, Alternately you can try replicating DC manually through AD Sites and Services, the default intra site replication interval is 30 Min. Hope this will work for u. Regards Paramesh