Re: MSExchangeDSAccess Problem

  • From: Rick Boza <rickb@xxxxxxxxxxxxxxx>
  • To: Exchange List <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 10 Mar 2005 08:28:11 -0500


Your second DC does need to be a GC for it to serve up directory lookups for
Outlook.  According to your message, it already is.

So, a couple of clarifying questions:

When you say your DC is a ?replica¹ DC versus a ?master¹ DC, what do you
mean?  Are you simply referring to the holder of the FSMO roles?

When you say your users suffer, what do you mean?  Do you mean an active
client using one of the DC¹s has a problem if that DC goes down in the
middle of a session?  Or do you mean something else entirely?

When you say ³I have serious issue² do you mean you are experiencing issues,
or you take issue with the architecture?  (Syntactic I know, but because I
suspect there¹s a slight language gap, I want to understand which of these
you intend).

Exactly what changes did you make that led to the issues you¹re now seeing?

On 3/10/05 12:28 AM, "Ara" <ara@xxxxxxxxxxxxx> wrote:

> hello
> I am a noob in exchange, but if I get it right, you want the exchange to
> automatically use the second server. there should be global catalog server on
> second one, also I think you may have to seize some rules. not sure let's see
> what experts say
> From: Rajnish Malik [mailto:rajnish@xxxxxxxxxxxx]
> Sent: Wed 3/9/2005 7:55 PM
> To: [ExchangeList]
> Subject: [exchangelist] MSExchangeDSAccess Problem
> Hi All,
> I have a Windows 2000 Cluster running Exchange 2000 Enterprise edition with SP
> 3 of exchange and SP 4 of OS.
> I have 2 domain controllers running Windows 2000 with SP 4
> 1. DC002 is a replica DC plus GC.
> 2. DC003 is a master DC plus GC. This server is operation master for every
> thing.
> I have serious issue with exchange directory access automatically pointing to
> single DC only (DC002).  As a result in case of un-availability of this server
> my users suffer.
> I want my exchange to point at both the DC¹s (DC002 & DC003)
> I have tried making manual connection by adding names of GC, Configuration and
> DC for both the servers.
> Now I started getting event warning message that domain controller does not
> exists:-
> EVENT ID: 2090
> EVENT Source: MSExchangeDSAccess
> Can anyone answer this query?
> Await your reply.
> Thanks & Regards,
> Rajnish Malik
> ------------------------------------------------------
> List Archives:
> Exchange Newsletters:
> Exchange FAQ:
> ------------------------------------------------------
> Other Internet Software Marketing Sites:
> World of Windows Networking:
> Leading Network Software Directory:
> No.1 ISA Server Resource Site:
> Windows Security Resource Site:
> Network Security Library:
> Windows 2000/NT Fax Solutions:
> ------------------------------------------------------
> You are currently subscribed to this Discussion List as:
> ara@xxxxxxxxxxxxx
> To unsubscribe visit
> Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: