Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

Exchange 2003 Machine Account Security Event 537

We have started having random issues with our exchange server over the last coulpe of days (when creating mailboxes through AD tools they don't always get created, random outlook disconects/reconnects, etc)  I have been searching for a solution for this for several days and happened to click on the Security section of the Event Viewer and noticed about 19,000 of the below errors.  Hopefully someone can help me out with this, as google and all of the other admins I know have no explination.  Thanks!
Date: 2/19/2009 
Source: Security
Time: 11:36:00 PM
Category: Logon/Logoff
Type: Failure Audit
Event ID: 537
User: NT AUTHORITY\SYSTEM
Computer: EXCHANGE
 
 
 
Logon Failure:
 	Reason:		An error occurred during logon
 	User Name:	EXCHANGE$
 	Domain:		FUBAR (Obviously not the real value)
 	Logon Type:	3
 	Logon Process:	ÈùÆ  (I have no idea what this is about but it changes in every message)
 	Authentication Package:	NTLM
 	Workstation Name:	EXCHANGE
 	Status code:	0xC000006D
 	Substatus code:	0x0
 	Caller User Name:	-
 	Caller Domain:	-
 	Caller Logon ID:	-
 	Caller Process ID:	-
 	Transited Services:	-
 	Source Network Address:	-
 	Source Port:	-

Open in new window

0
Honer
Asked:
Honer
  • 2
1 Solution
 
MesthaCommented:
I would start by running the domain prep again.
Then run the Exchange Best practises tool on the server and see what that throws up.

-M
0
 
HonerAuthor Commented:
Mestha,

    As a quick follow up.  As this is a "working" (as far as user can tell) production exchange server, is there anything special I need to be aware of before I run domain prep?  (If there is a site that covers this a link would be fine.  Google has failed me again :-/ )
0
 
MesthaCommented:
Domain prep is non-destructive. It can be run in production hours and does not make any changes that would affect the operation of Exchange. It simply corrects permissions within the domain that Exchange requires.

-M
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now