Exchange Server

Chris L · Guest

I've my exchange 2003 server running fine for months with no recent changes
to the network. Once or twice a day at random the exchange server will
fail with the following errors (see below). I recently turned on the
diagnostic logging on for MSExchangeDSAccess and MSExchangeAL. Info from
the web seems to point to the fact that the exchange server can't
communicate to the domain controller. When this happened the last time,
the domain controller seemed fine (but I didn't check the ldap port, will
do next time). Also, I have a second domain controller off-site, but
exchange doesn't seem to use it in the event that the GC from the local
site is "down".

Ideas, suggestions of other things to look at? :(

Thanks,
Chris L.

Policytest looks good...
===============================================
Local domain is "xxxx.net" (xxxx)
Account is "xxxx\Exchange Enterprise Servers"
========================
DC = "DCSERVER"
In site = "SantaMonica"
Right found: "SeSecurityPrivilege"
========================
DC = "SECONDDC"
In site = "Biloxi"
Right found: "SeSecurityPrivilege"

Autodiscovery looks ok too...
===============================================
Description:
Process MAD.EXE (PID=4004). DSAccess has discovered the following servers
with the following characteristics:
(Server name | Roles | Reachability | Synchronized | GC capable | PDC |
SACL right | Critical Data | Netlogon | OS Version)
In-site:
DCSERVER.xxxx.net CDG 7 7 1 0 1 1 7 1
Out-of-site:
SECONDDC.xxxx.net CDG 7 7 1 0 1 1 7 1

=================================================
Occasional errors that shut exchange down
================================================
Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 1/10/2005
Time: 11:47:05 PM
User: N/A
Computer: EXCHANGE
Description:
LDAP Bind was unsuccessful on directory dcserver.xxxx.net for distinguished
name ''. Directory returned error:[0x51] Server Down. DC=xxxx,DC=net

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2114
Date: 1/11/2005
Time: 12:12:49 AM
User: N/A
Computer: EXCHANGE
Description:
Process MAD.EXE (PID=4004). Topology Discovery failed, error 0xffffffff.

Jamelia · Guest

One thing you could check is to make sure that the Exchange server is using your internal DNS Server and not an external one. If it
cant connect to the internal DNS Server..there is no way it can discover the GC:s

Jamelia

"Chris L" <chrisjloverme@yahoo.com> wrote in message news:Xns95DB6255A276Csocalcl2003yahoocom@140.99.99.130...
I've my exchange 2003 server running fine for months with no recent changes
to the network. Once or twice a day at random the exchange server will
fail with the following errors (see below). I recently turned on the
diagnostic logging on for MSExchangeDSAccess and MSExchangeAL. Info from
the web seems to point to the fact that the exchange server can't
communicate to the domain controller. When this happened the last time,
the domain controller seemed fine (but I didn't check the ldap port, will
do next time). Also, I have a second domain controller off-site, but
exchange doesn't seem to use it in the event that the GC from the local
site is "down".

Ideas, suggestions of other things to look at? :(

Thanks,
Chris L.

Policytest looks good...
===============================================
Local domain is "xxxx.net" (xxxx)
Account is "xxxx\Exchange Enterprise Servers"
========================
DC = "DCSERVER"
In site = "SantaMonica"
Right found: "SeSecurityPrivilege"
========================
DC = "SECONDDC"
In site = "Biloxi"
Right found: "SeSecurityPrivilege"

Autodiscovery looks ok too...
===============================================
Description:
Process MAD.EXE (PID=4004). DSAccess has discovered the following servers
with the following characteristics:
(Server name | Roles | Reachability | Synchronized | GC capable | PDC |
SACL right | Critical Data | Netlogon | OS Version)
In-site:
DCSERVER.xxxx.net CDG 7 7 1 0 1 1 7 1
Out-of-site:
SECONDDC.xxxx.net CDG 7 7 1 0 1 1 7 1

=================================================
Occasional errors that shut exchange down
================================================
Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 1/10/2005
Time: 11:47:05 PM
User: N/A
Computer: EXCHANGE
Description:
LDAP Bind was unsuccessful on directory dcserver.xxxx.net for distinguished
name ''. Directory returned error:[0x51] Server Down. DC=xxxx,DC=net

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2114
Date: 1/11/2005
Time: 12:12:49 AM
User: N/A
Computer: EXCHANGE
Description:
Process MAD.EXE (PID=4004). Topology Discovery failed, error 0xffffffff.

	Exchange Server Forum Index -> Connectivity	All times are GMT
Page 1 of 1