Yes, your analysis makes sense. Exchange should only use DCs in its local AD site. Do you have sites set up and configured in AD? I'm guessing not, without any further information...
Exchange should log about once every 20-30 minutes a 2080 event log entry that tells you the in-site and out-site DCs it sees. Post us the contents of a recent one of those. It would help answer your question. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Steve Hart [mailto:sh...@wrightbg.com] Sent: Thursday, June 09, 2011 2:36 PM To: MS-Exchange Admin Issues Subject: Exchange changing DC Exchange 2007 Just had a brief outage that Exchange recovered from on its own. >From Event Viewer: 1022 from MSExchange Mailbox Sore with a failed logon. We got three of these 9662 from MEExchangeIS "There was an error obtaining the Unsolicited Commercial Email default filter level from the directory. The error code was 0x80040401. The value remains at 8." 9002 from MSExchange Assistants "Service MSExchangeMailboxAssistants. Stopped processing database Storage Group 1/Mail Database 1 (12ffb86a-4842-420c-8c15-b43b86acdbbc)." We got one of these for each Storage Group. 1022 MSExchange ActiveSync "The connection between the Client Access server and Mailbox server "CORP-EXCHANGE.wrightbg.com" failed." By now email is piling up in queues. Users are telephoning that Outlook can't reach the Exchange server. 2095 ExchangeADAccess "Process STORE.EXE (PID=3652). The Configuration Domain Controller has been changed from cal-dc03.wrightbg.com to CORP-DC03A.wrightbg.com." Now good things happen: 9661 MSExchangeIS "The Unsolicited Commercial Email default filter level has been updated. The new value is 8." 9001 from MSExchange Assistants "Service MSExchangeMailSubmission. Started to process mailbox database Storage Group 1/Mail Database 1 (12ffb86a-4842-420c-8c15-b43b86acdbbc). (One for each storage group" Email is working normally again. The total timeline was about 5 minutes. The original DC involved was in another physical location connected by a T1. The domain controller it's now pulling from is local. We've got bandwidth issues here in general and I suspect that the Exchange server couldn't contact the remote DC, so it after a delay, it switched to the local DC. Questions: Does this analysis make sense? We have two local DCs. How can I force Exchange to only use these, to avoid this problem in the future? Thanks in advance, Steve --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
