|
dougsymes -> remote DC down preventing Exch2K from working (7.Nov.2006 1:50:10 PM)
|
We have one W2K AD Domain and two sites. Our remote site has a DC running DNS, GC, DHCP and WINS for computers there. Our main site has the Exchange 2K server and three DC's with two of them being GC's and DHCP servers. We also use DFS to do replication between the sites in order to supply faster data to the remote site. All our servers are updated using WSUS so they have the latest SP's. Last night at our remote site it appears that we lost power and that the UPS didn't keep the DC running and it appears to have restarted about three times in attempts to get going again but it was estentually off from 10:22pm to about 6:35am. During this time our Exchange server quit allowing people to connect with Outlook and when I found out at about 10:45pm I noticed that the IS service had stopped as well as the MS Exchange System Attendant. The events in the Exchange Application event viewer are the following:
Time Source Category Event
10:22pm MSExchangeDSAccess Topology 2102
(Process MAD.exe, all DC servers in use are not responding [listed all three DCs at main site and the one remote DC])
10:24pm MSExchangeDSAccess Topology 2103
(Process MAD.exe, all DC servers in use are not responding [listed all three DCs at main site and the one remote DC])
10:25pm MSExchangeSA NSPI Proxy 9176
NSPI Proxy can contact Global Catalog <remote DC> but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients. Reboot <remote DC> as soon as possible.
NSPI Proxy can contact Global Catalog IDC2.interconnect-wiring.com but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients. Reboot IDC2.interconnect-wiring.com as soon as possible.
10:25pm MSExchangeSA NSPI Proxy 9057
NSPI Proxy cannot contact any Global Catalog that supports the NSPI Service. New clients will be refused until a Global Catalog is available. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients.
10:25pm MSExchangeSA RFR Interface 9143
Referral Interface cannot contact any Global Catalog that supports the NSPI Service. Clients making RFR requests will fail to connect until a Global Catalog becomes available again. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients.
10:25pm MSExchangeSA RFR Interface 9074
The Directory Service Referral interface failed to service a client request. RFRI is returning the error code:[0x3f0].
10:33pm MSExchangeDSAccess Topology 2102
(Process MAD.exe, all DC servers in use are not responding [listed all three DCs at main site and the one remote DC])
{Above events repeat}
10:36pm MSExchangeSA General 9154
DSACCESS returned an error '0x80004005' on DS notification. Microsoft Exchange System Attendant will re-set DS notification later.
10:40pm MSExchangeDSAccess Topology 2102
(Process MAD.exe, all DC servers in use are not responding [listed all three DCs at main site and the one remote DC])
..
..
During this time I tried rebooting Exchange but to no avail. Many events later, about 6:30am - someone rebooted the remote DC and then we could reboot the Exchange Server and the Information Store mounted fine.
My main question is how could a DC running as a GC on a remote site cause our Exchange server to not work when we have three local DC's in our main site and two of them are GC's.
Any thoughts?
|
|
|
|