Re: Exchange can't see DC

Unless you have Pre-Windows 2000 or SQL 2000 or Exchange 2000 systems, dump
WINS. It isn't needed anymore.

Mike Ober.

"Vern Rabe" <VernRabe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B248F3A6-657D-4678-8CF0-D72DF678C098@xxxxxxxxxxxxxxxx
Thanks, Mark. I had already put a CG on the remaining DC. I didn't
override
the DSAccess tab, and I had checked for the DCs in AD, and also in DNS
(but I
never checked WINS - is that really used?). I did finally find and fix the
problem, though. Apparently, the GPO was not always being applied to the
remaining DC, and the Enterprise Exchange Servers did not have the right
to
Manage auditing and security logs. As a result, DSAccess wouldn't accept
them. I fixed that (permanently, I hope), and I'm back up.

Thanks for the quick response
Vern Rabe

"Mark Arnold [MVP]" wrote:

On Wed, 6 Dec 2006 21:50:01 -0800, Vern Rabe
<VernRabe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Exchange 2003 on Windows 2003. One of my DCs recently died, and I had to
take
it offline. Exchange hasn't worked since.

Err, yes, and Exchange won't work until you make one of the other DCs
a GC and make sure that you hadn't overriden the DSAccess tab on the
properties of the server in ESM.

There are two symptoms that tell me
that the Exchange server doesn't recognize the remaining DC. First, in
Exchange System Manager, Servers, the properties of the Exchange server,
Directory Access tab, no domain controllers are listed when
Automatically
discover servers is selected, regardless of what is selected in the Show
drop
down. Second, in the Application Event log, this is what 2081 looks like
since the DC died:

Process MAD.EXE (PID=740). DSAccess will use the servers from the
following
list:
Domain Controllers:

Global Catalogs:

The Configuration Domain Controller is set to <None>.

The same is displayed for INETINFO.EXE. Prior to the DC dying, this is
what
it reported:

Process MAD.EXE (PID=932). DSAccess will use the servers from the
following
list:
Domain Controllers:
dell220.RABE.NET

Global Catalogs:
dell220.RABE.NET

The Configuration Domain Controller is set to dell220.RABE.NET.

Where dell220 is the now dead and gone DC. If I go way back (several
months)
I can find some entries like this:

Process MAD.EXE (PID=1952). DSAccess will use the servers from the
following
list:
Domain Controllers:
STILTS.RABE.NET
dell220.RABE.NET

Global Catalogs:
dell220.RABE.NET

The Configuration Domain Controller is set to dell220.RABE.NET.

Where STILTS is the remaining DC. Since dell220 died, I have seized all
five
FSMOs onto STILTS, and have created a global catalog. I have also
promoted
another server to DC, and yet the Exchange server can't see any.

What's missing?

Thanks
Vern Rabe

Check AD Sites and Services. Check WINS and DNS settings on the DC and
the Exchange server. Make sure STILTS is a GC and reboot it to make
sure it knows it's a GC.



.

Relevant Pages

  • Re: Exchange cant see DC
    ... the DSAccess tab, and I had checked for the DCs in AD, and also in DNS (but I ... Exchange System Manager, Servers, the properties of the Exchange server, ...
    (microsoft.public.exchange.admin)
  • Re: Upgrading Exchange 2003 Hardware
    ... now working on the parrallel exchange server for migration. ... Intent was to build the new baseline servers offline, ... We need to replicate all AD/Exchange data into fresh ...
    (microsoft.public.exchange.admin)
  • Re: Directory access topology
    ... The following list outlines the discovery process, ... DSAccess determines server suitability and assigns ... sorts the siteLink objects for each site from lowest cost to highest cost. ... global catalog servers that are located in the secondary topology sites. ...
    (microsoft.public.exchange2000.admin)
  • RE: Ldap Mad.exe error event id 2061
    ... DSAccess needs to close a connection to the ... Navigate to your Exchange server. ... Click Ok and reboot your Exchange server. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Controlling/Limiting impact of LDAP Referrals / remote sites d
    ... from what I know DSACCESS uses DNS to retrieve a DC to read the directory from. ... After that DSACCESS creates an in-site list and an out-site list based upon the information of the directory itself. ... BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx ... 'DSAccess' in Exchange server queries resource ...
    (microsoft.public.windows.server.active_directory)
Loading