Re: ??? Ideas on why exchange fails when one DC is rebooting?

From: JDTHREE [MVP] (john_at_removeforspam.engagenet.com)
Date: 03/19/04 

Date: Fri, 19 Mar 2004 11:07:59 -0600

Thanks, I'll run through these and give them a try. DNS entry for the
"old" server was removed before putting the new one in place, but
something might not have happened properly. Thanks for the info!

john

On Fri, 19 Mar 2004 06:51:30 GMT, v-teliu@online.microsoft.com (Terry
Liu [MSFT]) wrote:

>Hi John,
>
>Based on the problem description, I understand that DNS should be root
>cause of this issue.
>
>Regarding the event ID 9074, you must update the DNS information by
>removing the host record that is pointing to the domain controller that was
>removed. To do so, follow these steps:
>
>1. Click Start, and then click Run.
>2. In the Open box, type "cmd" (without the quotation marks), and then
>click OK.
>3. At the command prompt, type "ipconfig /flushdns" (without the quotation
>marks), and then press ENTER.
>4. At the command prompt, type "ipconfig /registerdns" (without the
>quotation marks), and then press ENTER.
>
>This procedure updates the DNS information. Exchange 2000 then links with a
>domain controller that is online.
>
>In addition, you can use DSAdiag to check the issue again. Exchange 2000
>and Exchange 2003 use the DSAccess API to communicate with Active
>Directory. DSAdiag.exe is a utility that lists the domain controllers,
>global catalog servers, and the configuration domain controller that the
>DSAccess API attempts to contact on behalf of Exchange. The status of the
>connection is displayed in the output (Up, Down, Fast, Slow, In Synch). If
>DSAccess is having trouble communicating to a particular domain controller
>or global catalog server, it fails over to a different Active Directory
>server.
>
>When you use DSAdiag.exe, you can manually force server discovery.
>DSAdiag.exe must be copied into the \Program Files\Exchsrvr\Bin folder.
>Open a command prompt and change the folders to \Bin. When you type
>"dsadiag" (without the quotation marks) and press ENTER, two options are
>displayed:
>
>
>
>Regarding event ID 8231, it may occur if the Manage Auditing and Security
>Log right (SeSecurityPrivilege) was removed for the Exchange Enterprise
>Servers domain local group on some or all of the domain controllers.
>
>When the first Exchange computer is installed in a domain, or when Exchange
>Setup is run with the /domainprep switch, the Exchange Enterprise Servers
>group is given the SeSecurityPrivilege right.
>
>If the SeSecurityPrivilege right is later removed, Exchange computers that
>use domain controllers in the domain stop working, but not immediately.
>When Kerberos security refresh intervals expire or Exchange services are
>restarted on particular servers, the issues become evident.
>
>You can refer to this Knowledge Base article: 314294 XADM: Exchange 2000
>Error Messages Are Generated Because of --
>http://support.microsoft.com/?id=314294
>
>
>
>Regarding the event 8026, please refer to the two Knowledge Base article:
>
>288828 XADM: ADC Replication Is Not Successful and an Event 8026 Message Is
>-- http://support.microsoft.com/?id=288828
>
>For your reference: 272552 XADM: Event 8026 and Event 8260: Can't Access
>Address List Configuration -- http://support.microsoft.com/?id=272552
>
>Hope this information helps!
>
>Have a nice day!
>
>Best regards,
>
>Terry Liu
>MCSE 2K MCSA MCDBA CCNA
>Microsoft Online Support Engineer
>
>Get Secure! - <www.microsoft.com/security>
>=====================================================
>When responding to posts, please "Reply to Group" via your newsreader so
>that others may learn and benefit from your issue.
>=====================================================
>This posting is provided "AS IS" with no warranties, and confers no rights.

Relevant Pages

  • RE: Strange Irregular DNS/Networking Problems
    ... Never heard about this kind of problem with IPv6, but think this is because it is not used so much until now. ... What i heard is that firefox or some other not MS browsers and addons make problems with DNS resolving after changing DNS servers. ... After resetting the domain controller and booting up things are back ...
    (microsoft.public.windows.server.dns)
  • Re: Problem sending email out of Exchange 2003
    ... My problem was resolved last night when it was found that Exchange was not ... referring DNS queries to SBS but instead had been given specific DNS ... Exchange SMTP was no longer able to query these servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange cant send email to one of the domains
    ... Specifying the smarthost as the remote mail exchanger won't be considered ... Exchange will route the message to this BH server and deliver the message to ... DNS, ... Most mail servers have no problem sending messages via SMTP ...
    (microsoft.public.exchange.admin)
  • Re: Exchange cant send email to one of the domains
    ... Specifying the smarthost as the remote mail exchanger won't be considered ... Exchange will route the message to this BH server and deliver the message to ... DNS, ... Most mail servers have no problem sending messages via SMTP ...
    (microsoft.public.exchange2000.connectivity)
  • Re: Exchange cant send email to one of the domains
    ... Specifying the smarthost as the remote mail exchanger won't be considered ... Exchange will route the message to this BH server and deliver the message to ... DNS, ... Most mail servers have no problem sending messages via SMTP ...
    (microsoft.public.exchange2000.admin)