Exchange 2k3 and AD Communication failure

pts.
Tags:
Active Directory
Exchange security
Microsoft Exchange
Spam
Dear All, I have the following setup all running on Dell PE 1950 servers AD : Win2k3 Standard ( DC, DNS, DHCP ) IP - 10.10.1.6 EMAIL : Exchange 2003 -standard IP - 10.10.1.4 the link below explains exactly the errors I get http://support.microsoft.com/kb/322837 Event Category: (3) Event ID: 2103 Date: 4/21/2007 Time: 6:24:07 AM User: N/A Computer: LOCALMAIL Description: The description for Event ID ( 2103 ) in Source ( MSExchangeDSAccess ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: MAD.EXE, 2092, jag-dc01. jag.com Event Type: Error Event Source: MSExchangeDSAccess Event Category: (3) Event ID: 2104 Date: 4/21/2007 Time: 6:24:24 AM User: N/A Computer: LOCALMAIL Description: The description for Event ID ( 2104 ) in Source ( MSExchangeDSAccess ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: INETINFO.EXE, 1416. Event Type: Error Event Source: MSExchangeAL Event Category: (5) Event ID: 8026 Date: 4/21/2007 Time: 6:24:56 AM User: N/A Computer: LOCALMAIL Description: The description for Event ID ( 8026 ) in Source ( MSExchangeAL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: jag-dc01.jag.com, , 51, Server Down, Event Type: Error Event Source: MSExchangeAL Event Category: (4) Event ID: 8250 Date: 4/21/2007 Time: 6:25:52 AM User: N/A Computer: LOCALMAIL Description: The description for Event ID ( 8250 ) in Source ( MSExchangeAL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: DsGetDCNameW, 54b, The specified domain either does not exist or could not be contacted.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Aside from the fact that you have not asked a clear question, the article points to two things that should be addressed.

1) Does YOUR instance of these match what the article says; i.e. occurring only after a reboot, and apparently not having any other effect? I’d recommend a closer examination of your event logs to see if Microsoft’s observation is accurate.

2) Since some of your error messages bear IDs different than specified by MS, you should use the comment/feedback field at the bottom of the article to point out to them that you are getting a particular error message which points to a somewhat different set of circumstances. And then specify what you’re seeing.

If users do not hold vendors accountable by pointing out inconsistencies such as these, the vendor has little incentive to fix the problem.

Bob

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • BIGFella
    Looking at the errors specfied in the MS article, I would suggest looking at the following: Using the Exchange server manager MMC check the properties of the exchange server (at the server level) on the "Directory Access" tab and ensure that the "Automatically discover servers" option is set, it may be that this option has been disabled and de-commissioned server(s) have been manually specified have been set causing the errors described.
    0 pointsBadges:
    report
  • Amehsys
    Dear all, it's resolved. There were issues with the Broadcom Network cards on the Dell servers and Dell happily ignore the fact that there's a problem. We had to change the cards.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following