Re: Exchange Slowness due to remote Domain Controllers?



this might help...?

http://support.microsoft.com/kb/319206/en-us

--
Susan Conkey [MVP]



"Aaron" <Aaron.Smith@xxxxxxxx> wrote in message
news:1173885419.362674.60420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We have an Exchange 2003 SP2 server that sits at a remote hosting
facility. We have 6 domain controllers, 5 of which are here at the
local network and one of which is at the remote facility. Each DC has
a global catalog. The Exchange server is set to auto-discover domain
controllers for directory access (except for the config server, which
is set to the local DC that shares the rack with the Exchange
server). The two sites are connected via VPN tunnels (cisco PIX).

Here's my issues I'm seeing. We get seemingly random reports of
Exchange being "slow". Not REAL slow, just...kinda slow. I don't
really notice it myself unless I'm opening a folder that has a TON of
messages. But I'd expect that with the server not being local. It's
not unbearably slow, but that's relative for some users. Our
monitoring software sometimes reports momentary outages to various
services like the HTTPS port (for OWA) or the IMAP port. It'll
timeout once and then be fine. Lately, OUtlook calendar users have
reported that thier calendars are slow, especially if they open
someone else's shared calendar. The final item we notice is that
Macintosh users using Entourage (which interfaces with the OWA web
site via WebDAV) will often get what they've started calling the
"Pinwheel of Death" where it will sit and sit waiting for a response
from the Exchange server.

Here's my question. Could all of these somewhat random performance
issues be because the Exchange server is having to contact Domain
controllers that are not on it's local network for information? I.e.,
if I restricted it to only use the one local domain controller (with
perhaps ONE other remote one for some redundancy) would that perhaps
clear up some of these problems?



.



Relevant Pages

  • Re: Exchange Slowness due to remote Domain Controllers?
    ... We have 6 domain controllers, 5 of which are here at the ... local network and one of which is at the remote facility. ... The Exchange server is set to auto-discover domain ...
    (microsoft.public.exchange.admin)
  • Re: Global Catalog and Exchange Server Placement Question
    ... In a single domain environment, you really have no use for GCs. ... All domain controllers have all objects in the forest. ... The Exchange server is at the HQ site. ... The rest use RDP to access terminal server in HQ so that they have access to their main legacy application in the HQ, and they use Outlook in terminal server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Outlook is retrieving data from exchange
    ... remaining Domain Controllers, correct? ... The two Domain Controllers should show port 389 while the ... at Service Pack level are the Outlook clients? ... outlook (retrieving data from the Microsoft exchange server error ...
    (microsoft.public.windows.server.active_directory)
  • Re: Exchange 2007 distribution group creation
    ... All our domain controllers are running server 2003 with the latest ... The exchange server has the latest SP installed. ... > universal distribution group in exchange management console. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange/Outlook password problem
    ... Event Category: Account Logon ... saved password for the Exchange server, ... Caller User Name: - ... against all three of our domain controllers with no problems. ...
    (microsoft.public.exchange.admin)

Loading