DC not responding

From: Steve Gould (steve.gould_at_apawood.org)
Date: 02/17/04


Date: Tue, 17 Feb 2004 13:22:37 -0800

When ever I reboot my FSMO DC (dc1) my Exchange 2003 server gives LDAP
errors. According to the messages the Exchange server reports both of my
DC's as being unreachable. Below are the error strings. I have checked
netdiag, nltest, and the Active Directory Administration Tool. It seems DNS,
Wins, LDAP, etc. are working properly. It almost seems like a kerberos
problem because of the last error message. This particular DC (dc2) has no
event errors logged. Both DC's are GC's, both run DNS and Wins. Dc2 also
runs RAS, DHCP, printer shares, and Backup Exec for all the servers.

Can anyone suggest what to test next?

Errors:

Application Log Errors:

* Source: MSExchangeDSAccess - Event ID: 2114 - Process INETINFO.EXE
(PID=1600). Topology Discovery failed, error 0x80040a02.

* Source: MSExchangeDSAccess - Event ID: 2102 - Process MAD.EXE (PID=1964).
All Domain Controller Servers in use are not responding:
dc1.apawood.org
dc2.apawood.org

* Source: MSExchangeSA - Event ID: 9154 - DSACCESS returned an error
'0x80004005' on DS notification. Microsoft Exchange System Attendant will
re-set DS notification later.

System Log Errors:

* Source: NETLOGON - Event ID: 5719 - This computer was not able to set up a
secure session with a domain controller in domain APA_NT due to the
following:
The remote procedure call was cancelled. This may lead to authentication
problems. Make sure that this computer is connected to the network. If the
problem persists, please contact your domain administrator.

* Source: LSASRV - Event ID: 40961 - The Security System could not establish
a secured connection with the server ldap/dc2.apawood.org. No
authentication protocol was available.

Thanks,

-- 
Steve Gould
Network Administrator
APA - The Engineered Wood Association
253-620-7454
steve.gould@apawood.org


Relevant Pages

  • RE: Help Replication problem
    ... The Exchange server does not need to be a Domain Controller to function. ... The mailboxes will be linked to the Active Directory users as it writes ...
    (microsoft.public.windows.server.active_directory)
  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • Re: MSADC 8355 LDAP Result failed
    ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ... If you put Exchange on one, ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ... If you put Exchange on one, then you won't need the other ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... Made the exchange ldap anonymous, ... I receive 2 when the server restarts. ... Opening LDAP session to directory xxx on port 389. ...
    (microsoft.public.exchange.setup)