Re: Exchange 2000 - Domain Controller Failover - could not send or rec

Tech-Archive recommends: Fix windows errors by optimizing your registry

Steve-

Are both of your DCs configured as Global Catalogs? They should be. Exchange
talks to GCs. It will failover automatically. You can double check in the
DSAccess tab of the server's properties in ESM.

--
Thanks,
Brian Desmond
Windows Server MVP

www.briandesmond.com


"SteveJHU" <SteveJHU@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A22591B-FE4A-44B5-BC0D-98B925104115@xxxxxxxxxxxxxxxx
> Hi,
>
> - Does anyone know how to configure Exchange 2000 Server to automatically
> failover to another available Domain Controller in case one fails?
> - Or, if it cannot be done automatically, does anyone know the proper
> procedure for reconfiguring Exchange 2000 to point to another DC in case
> of
> failure?
>
>
> We have one Exchange 2000 Server and two Active Directory 2000 Domain
> Controllers in native-mode (all have latest Service Packs and updates).
>
> We recently brought one of our two Domain Controllers down for
> maintenance.
> During that time, clients could not send or receive email. Their emails
> would not appear in their Outbox, but would actually seem like they were
> sent. However, they were not. It looks like they were just put into a
> queue
> on the Exchange server. Same with incoming email. Both DC's are Global
> Catalog servers and clients could look up addresses in the Global Address
> List and access their mailboxes fine. Just sending and receiving were out
> to
> lunch. The remaining online DC also had all FSMO roles except for PDC
> Emulator. DNS is configured on both DC's.
>
> We suspected that the problem was from both of the default Recipient
> Update
> Services pointing to the disconnected DC. We added a second RUS
> configuration for the second DC and no luck. We then changed the RUS
> Enterprise Configuration to the second DC and still no luck.
>
> We finally changed back the RUS Enterprise Configuration to the original
> setting and brought the DC back online. All emails in the queue were then
> sent and received. We left the new RUS we created though which points to
> the
> other DC (don't know if this will hurt anything).
>
> So if anyone has some words of wisdom as to how we should configure
> Exchange
> differently or what we should have done to allow the remaining DC to take
> over, we'd appreciate it! Thanks!
>
> Steve
>
>
>


.

Relevant Pages

  • Re: Problem w. RUS in one subdomain
    ... Do you mean that after you rebuild RUS, there is a delay before email ... Or the RUS does not stamp ... I would like to let you know that it is necessary to run Exchange setup ... whether there is an Exchange 2000/2003 server in the domain as Exchange ...
    (microsoft.public.exchange.admin)
  • Re: Exchange in a Child domain
    ... Service (RUS) problem. ... Do your recipients have valid e-mail addresses, ... MVP - Exchange ... in the child domain on the parent domain Exchange Server. ...
    (microsoft.public.exchange.setup)
  • Re: Problem w. RUS in one subdomain
    ... Coming back to office this morning and checking Exchange server logs and user properties, it looks like everything is in top order now:). ... Do you mean that after you rebuild RUS, there is a delay before email addresses are stamped into newly-created objects? ... Generally, when we create a new mailbox-enabled user in Exchange 2003 Server, the Recipient Update Service in Exchange will try to stamp the e-mail addresses to it, and this procedure may take several minutes. ...
    (microsoft.public.exchange.admin)
  • Re: Configuring LDAP on Entourage 2004 OS X
    ... Exchange server on the SBS server box. ... Mobile Access) option in the "Web Services Configuration" page, ...
    (microsoft.public.windows.server.sbs)
  • Re: No one will answer
    ... Having an MX record pointing to an IP address isn't a legal configuration, ... what is your DomainA server trying ... Microsoft Exchange Support ... How about External DNS configuration? ...
    (microsoft.public.exchange2000.active.directory.integration)