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

If the bad DC is in there adn something wierd is going on with Exchange's
DNS client, I can see htis happening...

--
Thanks,
Brian Desmond
Windows Server MVP

www.briandesmond.com


"SteveJHU" <SteveJHU@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E3D452C9-CE3C-45D4-B06B-4FB5B1CE3AE0@xxxxxxxxxxxxxxxx
>
> Hey, thanks for the reply Brian...
>
> Yes, both DC's are configured as Global Catalog Servers and show under the
> ESM DSAccess tab as Global Catalog Servers.
>
> And this just effected clients sending and receiving mail. Even through
> OWA, users could not send/receive email. They appeared to send, but would
> actually go into a queue until the DC was brought online. Very strange.
> One thought is that we utilize our organizations's 3rd party DNS servers.
> We send them the netlogon.dns files from our two DC's. But I don't see
> how
> this could cause the effects that we have been noticing.
>
> Any more thoughts? Thanks!
>
> Steve
>
>
> "Brian Desmond [MVP]" wrote:
>
>> 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: Lost Resources
    ... You wrote in your site you have a DC/DNS server and also the clients are in that site. ... Means for my point of view, they have all the same ip range in use and also the same DNS servers. ... think there is a problem with the VPN Configuration? ...
    (microsoft.public.windows.server.active_directory)
  • Re: OWA & SMTP on NLB Front End Server
    ... the configuration with ISA in front of your FE servers is a preferred ... solution and I commonly do this at many of my clients. ... You don't need two nics on each server to accomplish an NLB configuration. ...
    (microsoft.public.exchange.connectivity)
  • Re: MAPI Clients - Referral Service
    ... The clients benefit from a local GC for other reasons, ... We have centralized Exchange servers in the center of a hub ... > Basically in this configuration, do clients benefit from a local GC or not ...
    (microsoft.public.exchange.admin)
  • Re: DNS lookups from external clients
    ... >servers in the domain. ... It's more likely a DHCP or TCP/IP configuration error. ... >clients to do lookups on addresses in the domain despite ... Any DNS client can contact any DNS server - at a DNS level ...
    (microsoft.public.windows.server.dns)
  • Re: Help with setting up Sites.
    ... Site A - respresenting physical site B ... servers is increasing by the day. ... Do you have any DCs at SiteB? ... clients servers in the relevant sites to authenticate against them. ...
    (microsoft.public.windows.server.active_directory)